Seafile blocks on HDD and indexes on SSD

[tomservo]

I hate the block box nature of docker too, and the running even more stuff as root, and several other aspects of docker. You might be interrested in this post I made about how I switched to the docker version, but running in podman instead of docker.

Alternative steps for switching to the docker version of Seafile

Continuing from above Set file permissions. Now we will need the container to have access to the files in the “persistent-data” directory. The admin guide says to run “chmod -R a+rwx /seafile-data/persistent-data” to give everyone access to these files and directories. This means that ever user on this server has full access to read, add and remove Seafile files. I don’t really like that idea, but if you’re running most of the code on this server as root, then file permissions aren’t going t…

And for splitting your data up to put some on the HDD and some on the NVME, I think this can work. Docker can be weird with links, so rather than using a link, I would suggest defining a different path as a mount point. I think it would look something like this:

    volumes:
      - /path/to/hdd/seafile-data:/shared
      - /path/to/nvme/commits:/shared/seafile/seafile-data/storage/commits
      - /path/to/nvme/fs:/shared/seafile/seafile-data/storage/fs