coderofsalvation/xrforge
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

📃 master: update documentation

Browse source
This commit is contained in:
Leon van Kammen 2025-08-05 19:05:49 +02:00
parent d44007cc00
commit ed8756cc90
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
manyfold/README.md
View file

@ -48,14 +48,14 @@ When found, it uses the files in there instead (`/manyfold/usr/src/app/public/40
![](https://i.imgur.com/4VMF3CQ.png)
To enable rclone to mount network drives, the container must be run with FUSE-device support.
To enable rclone to mount **readonly** network drives, the container must be run with FUSE-device support.
The quickest way is:
* add `-v ./manyfold/root/.config:/root/.config --cap-add SYS_ADMIN --security-opt apparmor:unconfined --device /dev/fuse` to the docker cmd
* add network drives by running `docker exec -it rclone config` in a running container
* add network drives by running `docker exec -it rclone config` in a running container (see example below)
* profit!
Your drives will get automagically mounted and added to the database automagically (by [manyfold.sh](cli/manyfold.sh) `rclone_automount`-cmd) during container boot.
Your drives will/should get automagically mounted **readonly** and added to the database automagically (by [manyfold.sh](cli/manyfold.sh) `rclone_automount`-cmd) during container boot.
> NOTE: by default all rclone remotes automagically show up as separate manyfold libraries, however use `RCLONE_REMOTE` this to specify a [combined](https://rclone.org/combine/) or [union](https://rclone.org/union/) rclone remote.