So far there's only one viable option for #SelfHosting file storage; #seafile. However, I need to resolve the backup issue before I can start using it.
I tried seafile-mirror but I couldn't get it to work. I tried fuse, but that didn't work in a docker container, even after tweaking the #docker compose file.
The only option seems to be somehow physically cloning the configuration, file chunks and database files.
Have you tried rclone? That's the way I've settled on backing it up. Rclone natively supports Seafile as one of the many remotes. Set that up with your Seafile server URL, username, and password. Then rclone mount --daemon seafile /path/to/mount/directory. That will "fuse" the chunks back together and you can use rclone copy, cp, or rsync to back it up wherever you want. Seems to be working quite well so far.
Though I'm currently testing using the backend function and pointing Seafile at iDrive e2 as it's storage target instead of the local file system.
Add comment