Support for FUSE extension about seafile-containerized HOT 6 CLOSED

@ggogel The main use-case would be to have automatic backups that are independant of Seafile's way of storing files and be able to later on restore the backup to a fully new Seafile install if anything goes terribly wrong.

from seafile-containerized.

Hi,

What exactly would be a use case for this?

The documentation states that the file mount can only be accessed read only.

Further, to mount a volume inside a container, the container needs system administrator capabilities, as demonstrated in the docs. This is quite a security risk.

I'm sorry but this looks like something I'm not going to support. You can always modify the Dockerfile or CMD statement yourself to implement this feature.

from seafile-containerized.

Rclone has a seafile backend, which uses the seafdav (webdav) interface of seafile: https://rclone.org/seafile/

Or you can use any other webdav client.

from seafile-containerized.

@ggogel Thanks! Are you using rclone for backups currently? Any other suggestion how you'd handle it? Thanks again and also thanks for this project! :)

from seafile-containerized.

Thank you :)

I'm not doing any backups on file level at the moment. Since I sync my libraries across several devices, I don't think that this is necessary.

I'm taking snapshots and backups at volume level with Longhorn. I'm using Longhorn as storage solution for Kubernetes. To be precise, I'm using Harvester as hypervisor, which has Longhorn integrated.

Before migrating to Kubernetes, I used Veeam to take backups of my virtual machines running Docker.

from seafile-containerized.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from seafile-containerized.