Added a comment: using fuse and nextcloud

diff --git a/doc/forum/Repository_on_large_disk_server__44___browse_on_client/comment_1_6563a45d5303d5e65e88aa6df162f9fc._comment b/doc/forum/Repository_on_large_disk_server__44___browse_on_client/comment_1_6563a45d5303d5e65e88aa6df162f9fc._comment
new file mode 100644 (file)
index 0000000..624764e
--- /dev/null
+++ b/doc/forum/Repository_on_large_disk_server__44___browse_on_client/comment_1_6563a45d5303d5e65e88aa6df162f9fc._comment
@@ -0,0 +1,12 @@
+[[!comment format=mdwn
+ username="psxvoid"
+ avatar="http://cdn.libravatar.org/avatar/fde068fbdeabeea31e3be7aa9c55d84b"
+ subject="using fuse and nextcloud"
+ date="2024-11-03T13:44:44Z"
+ content="""
+Hi,
+
+One option is to use `bindfs --resolve-symlinks` FUSE to resolve simlinks, and then share the \"un-symlinked\" directory to whatever service you want, including NFS.
+
+Personally, I'm using  `bindfs --resolve-symlinks` with `nextcloud` instance - works great.
+"""]]