Excellent work! Thanks for the update instructions!
Search Criteria
Package Details: seafile 9.0.12-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/seafile.git (read-only, click to copy) |
|---|---|
| Package Base: | seafile |
| Description: | An online file storage and collaboration tool |
| Upstream URL: | https://github.com/haiwen/seafile |
| Licenses: | GPL2 |
| Conflicts: | seafile-server |
| Provides: | seafile-client-cli |
| Submitter: | eolianoe |
| Maintainer: | Joffrey |
| Last Packager: | Joffrey |
| Votes: | 110 |
| Popularity: | 0.000000 |
| First Submitted: | 2016-08-11 16:38 (UTC) |
| Last Updated: | 2025-02-18 17:52 (UTC) |
Dependencies (8)
- argon2 (argon2-gitAUR)
- fuse (fuse2)
- libevent (libevent-gitAUR)
- libsearpcAUR
- libwebsockets
- sqlite (sqlite-fossilAUR)
- intltool (make)
- vala (vala-gitAUR) (make)
Required by (2)
Sources (2)
maribu commented on 2014-04-30 18:37 (UTC)
<deleted-account> commented on 2014-04-30 11:53 (UTC)
This package now comes with a bash script 'seahub-preupgrade', that is NOT used automatically anywhere. It exists solely to unify most steps of the procedure to upgrade seahub after a seafile upgrade. With this, the steps to upgrade seafile are now like this:
1. Stop seafile, e.g. # systemctl stop seafile-server@example.org
2. Upgrade the seafile-server package
3. Repeat for all for your seafile-server's on the target system (e.g. example.org, foo.bar, etc.):
a. Change directory to the server's 'seafile-server' subdirectory, e.g. '$ cd /srv/seafile/example.org/seafile-server'
b. Become the user the seafile server runs at (who should own all the directores and files below e.g. /srv/seafile), e.g. '$ sudo -u seafile -s'
c. Run the preupgrade script (Or do the steps by hand, see seafile's wiki for that): '$ seahub-preupgrade'
d. Run the appropriate seafile/seahub upgrade scripts from the upgrade subdirectory, i.e. '$ ./upgrade/minor-upgrade.sh' for an x.y.a to x.y.b (a < b) upgrade (minor) and '$ ./upgrade/upgrade_x.y_z.w.sh' for an x.y.a to z.w.b (x < z || y < w) upgrade (major).
4. Start seafile, e.g. # systemctl start seafile-server@example.org
Important note: I have tested this on my own server only so far, feedback would thus be welcome. Also, note that the seahub-preupgrade script has no error detection other than exiting if it's not run in a directory named 'seafile-server', so use it at your own risk.
<deleted-account> commented on 2014-04-30 11:53 (UTC)
This package now comes with a bash script 'seahub-preupgrade', that is NOT used automatically anywhere. It exists solely to unify most steps of the procedure to upgrade seahub after a seafile upgrade. With this, the steps to upgrade seafile are now like this:
1. Stop seafile, e.g. # systemctl stop seafile-server@example.org
2. Upgrade the seafile-server package
3. Repeat for all for your seafile-server's on the target system (e.g. example.org, foo.bar, etc.):
a. Change directory to the server's 'seafile-server' subdirectory, e.g. '$ cd /srv/seafile/example.org/seafile-server'
b. Become the user the seafile server runs at (who should own all the directores and files below e.g. /srv/seafile), e.g. '$ sudo -u seafile -s'
c. Run the preupgrade script (Or do the steps by hand, see seafile's wiki for that): '$ seahub-preupgrade'
d. Run the appropriate seafile/seahub upgrade scripts from the upgrade subdirectory, i.e. '$ ./upgrade/minor-upgrade.sh' for an x.y.a to x.y.b (a < b) upgrade (minor) and '$ ./upgrade/upgrade_x.y_z.w.sh' for an x.y.a to z.w.b (x <z || y < w) upgrade (major).
4. Start seafile, e.g. # systemctl start seafile-server@example.org
Important note: I have tested this on my own server only so far, feedback would thus be welcome. Also, note that the seahub-preupgrade script has no error detection other than exiting if it's not run in a directory named 'seafile-server', so use it at your own risk.
<deleted-account> commented on 2014-04-30 11:52 (UTC)
This package now comes with a bash script 'seahub-preupgrade', that is NOT used automatically anywhere. It exists solely to unify most steps of the procedure to upgrade seahub after a seafile upgrade. With this, the steps to upgrade seafile are now like this:
1. Stop seafile, e.g. # systemctl stop seafile-server@example.org
2. Upgrade the seafile-server package
3. Repeat for all for your seafile-server's on the target system (e.g. example.org, foo.bar, etc.):
a. Change directory to the server's 'seafile-server' subdirectory, e.g. '$ cd /srv/seafile/example.org/seafile-server'
b. Become the user the seafile server runs at (who should own all the directores and files below e.g. /srv/seafile), e.g. '$ sudo -u seafile -s'
c. Run the preupgrade script (Or do the steps by hand, see seafile's wiki for that): '$ seahub-preupgrade'
d. Run the appropriate seafile/seahub upgrade scripts from the upgrade subdirectory, i.e. '$ ./upgrade/minor-upgrade.sh' for an x.y.a to x.y.b (a != b) upgrade (minor) and '$ ./upgrade/upgrade_x.y_z.w.sh' for an x.y.a to z.w.b (x != z || y != w) upgrade (major).
4. Start seafile, e.g. # systemctl start seafile-server@example.org
Important note: I have tested this on my own server only so far, feedback would thus be welcome. Also, note that the seahub-preupgrade script has no error detection other than exiting if it's not run in a directory named 'seafile-server', so use it at your own risk.
<deleted-account> commented on 2014-04-30 11:51 (UTC)
This package now comes with a bash script 'seahub-preupgrade', that is NOT used automatically anywhere. It exists solely to unify most steps of the procedure to upgrade seahub after a seafile upgrade. With this, the steps to upgrade seafile are now like this:
1. Stop seafile, e.g. # systemctl stop seafile-server@example.org
2. Upgrade the seafile-server package
3. Repeat for all for your seafile-server's on the target system (e.g. example.org, foo.bar, etc.):
a. Change directory to the server's 'seafile-server' subdirectory, e.g. '$ cd /srv/seafile/example.org/seafile-server'
b. Become that the user the seafile server runs at (who should own all the directores and files below e.g. /srv/seafile), e.g. '$ sudo -u seafile -s'
c. Run the preupgrade script (Or do the steps by hand, see seafile's wiki for that): '$ seahub-preupgrade'
d. Run the appropriate seafile/seahub upgrade scripts from the upgrade subdirectory, i.e. '$ ./upgrade/minor-upgrade.sh' for an x.y.a to x.y.b (a != b) upgrade (minor) and '$ ./upgrade/upgrade_x.y_z.w.sh' for an x.y.a to z.w.b (x != z || y != w) upgrade (major).
4. Start seafile, e.g. # systemctl start seafile-server@example.org
Important note: I have tested this on my own server only so far, feedback would thus be welcome. Also, note that the seahub-preupgrade script has no error detection other than exiting if it's not run in a directory named 'seafile-server', so use it at your own risk.
maribu commented on 2014-04-27 16:41 (UTC)
As acieroid said, your package needs gunicorn-python2 and not gunicorn. Also the "seafile-admin.patch" patch file needs to be updated: The bin path for the gunicorn-python2 package used in seafile-admin is "/usr/bin/gunicorn_django-python2", not "/usr/bin/gunicorn_django".
acieroid commented on 2014-04-27 08:31 (UTC)
I think you should depend on gunicorn-python2 instead of gunicorn (at least I needed to install gunicorn-python2 to get seafile-server to work).
<deleted-account> commented on 2014-04-27 08:19 (UTC)
If you use the --user option to systemd it is supposed to work. The workaround you describe has already been discussed here, though (and it is what I personally use, since I don't want to setup --user).
ElNick commented on 2014-04-27 08:10 (UTC)
systemd's %h resolution to seafile user's homedir in seafile-server@.service no longer works. Hardcoding the homedir into the file fixes problem with launching seafile's fcgi for me.
<deleted-account> commented on 2014-04-24 12:49 (UTC)
Forget my earlier reply (removed it). I get the same 'Page unavailable' problem. I didn't notice it before, since I don't actually use the webinterface anymore since you can do most of the stuff in the client nowadays. I'll look into it.
Pinned Comments