Don’t forget to stop Seafile Server before the upgrade (i.e: sudo systemctl stop seafile-server or sudo systemctl stop seahub && sudo systemctl stop seafile)
Don’t forget to change the directory rights of Seafile after unpacking it (i.e: chown -R seafile:nogroup seafile-server-9.0.2 or sudo chown -R seafile:seafile seafile-server-9.0.2 )
Don’t forget to apply the upgrade script/s according your start release && with the properly user which in normal case should be seafile (i.e change to seafile user: su seafile -s /bin/bash or sudo su seafile), then run upgrade, i.e: cd seafile-server-9.0.2 && sh upgrade/upgrade_8.0_9.0.sh
Recommendations and clarifications
Download the properly rpi version for your OS. There are: Debian Buster, Bullseye or Ubuntu Bionic, Focal, Hirsute. These were compiled against his own native libraries inside linux containers.
If Seahub is not starting properly you can debug by disabling daemon in conf/gunicorn.conf.py with daemon = False and start Seahub manually: ./seafile-server-latest/seahub.sh start
We are still searching for ARM Arch volunteers. Let us a message in Seafile Forum
You can check Seafile release table to find the lifetime of each release and current supported OS.
The first ist clear and has no impact since the seahub.sh script is intended for both architectures, but the seafile/lib/python3 should exist and instead an empty python3.6 directory. Can you pls check?
Interesting, thanks. It seems for Bionic something doesn’t work as expected. The python3 directory should be there with its contents (site-packages…) and another directory python3.6 (native python used by bionic).
Hello!
This release (9.0.2) is the last one for raspberry pi. The generic linux release is 5 maintenance versions ahead (9.0.7).
Is the pi version abandoned?
Is it possible to run generic release on pi?