The upgrade process is a joke

Feature Request
1

There should be a simple way to upgrade Seafile. File storage is one of the most sensitive things you could possibly upload to the internet. One tiny exploit and you’re out terabytes of data and being doxed with data of yours.

After 2+ hours of messing around with the instructions as-per the complete joke of an upgrade guide that drowns the user in barely comprehensible config variables. I’d love to post the link but apparently I can’t post those here.

I am left with a broken Seafile config. I am an extremely skilled sysadmin and have been using Linux for 20+ years and Docker for at least 10, if I can’t figure it out, believe me, nobody can. I had to restore Seafile 11 and manually manipulate the database with bullshit terminal commands to get my files back by assigning the file blocks to the current user. This is a joke and I would’ve fired the person who wrote this guide and their bad design choices are playing with people’s data. There is absolutely no technical reason this can be done.

There needs to be a simple button that says “upgrade seafile” that just do it. If that doesn’t exist it’s a design flaw. That’s why I’m putting this in Feature Request instead. It is bar none the most important thing Seafile needs, whatever trivial issue the team is working on now is unimportant compared to this.

2

I’m not part of the Seafile dev team, just a sys admin who has been running and upgrading seafile for a long time, and part of the community who is here to help. I think it might help to clarify what you are requesting.

So is it specifically the upgrade from not-docker to a docker version that is the problem, or all upgrades? There’s lots of problems with docker, but it does bring the possibility to simplify upgrading. All I have had to do for the last several minor version upgrades is change the version number in a config file and restart docker (or podman in my case because I hate it just a little less than docker).

If it is the conversion to docker, you might want to look around the forums here. There is a lot of helpful threads, including one where I wrote my own guide on doing that upgrade, but with podman in place of docker.

We are here to help if you want to explain more about the problem you are seeing.

3

In my opinion, it doesn’t have to be just a button—but a migration script that performs a preflight check, then carries out the migration, and finally performs a health check would certainly be useful.