gotta ask though. what would be the correct way to run the server in /srv/seafile with your systemd script?
Search Criteria
Package Details: seafile 9.0.11-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: | 111 |
Popularity: | 0.000000 |
First Submitted: | 2016-08-11 16:38 (UTC) |
Last Updated: | 2024-11-14 17:06 (UTC) |
Dependencies (8)
- fuse (fuse2)
- libevent (libevent-gitAUR)
- libsearpcAUR
- libwebsockets
- python-future
- sqlite (sqlite-fossilAUR)
- intltool (make)
- vala (vala-gitAUR) (make)
Required by (2)
Sources (2)
Latest Comments
« First ‹ Previous 1 .. 40 41 42 43 44 45 46 47 Next › Last »
peacememories commented on 2013-11-20 20:46 (UTC)
peacememories commented on 2013-11-20 20:35 (UTC)
Seems like an elegant solution.
Thanks for the quick response.
<deleted-account> commented on 2013-11-20 18:27 (UTC)
I've added the systemd service I've been using:
The username is fixed to "seafile" (so if you want to use a different one, you have to change it in the service file), but the directory is set by the instance name. This means, that e.g.
systemctl start seafile-server@example.org
will try to start a seafile server located in the directory "/home/seafile/example.org/" as the user "seafile".
I have decided against creating a user in the install script (seafile-server.install), as there is no reason to add it for people who want to run it under their normal user, or have any other - more complex - setup of users and different seafile-servers on a single machine.
Sadly I could not find a way to use the instance name to carry both the username AND a directory under that username, because systemd failed to start any services where the .service file contained stuff like USER=$(sed ...) that would be necessary to split the instance name.
peacememories commented on 2013-11-20 17:34 (UTC)
First of all, thanks for taking over the package, it works great.
I'd like to suggest including a service file into the package though.
I'm using this at the moment: http://pastebin.com/rrn70Rtx
Of course the user would have to be added as well.
<deleted-account> commented on 2013-11-09 00:34 (UTC)
@ddanier: Thanks for your work, I'll try to take good care of it!
ddanier commented on 2013-11-08 12:40 (UTC)
@calrama: Feel free to adopt this package. Thanks!
<deleted-account> commented on 2013-11-08 12:28 (UTC)
Updated PKGBUILD which I've verified to work a least on my own server: http://pastebin.com/raw.php?i=wJX1Pd2L
I'd be willing to adopt this package if you want (it's been out-of-date for a while).
Changes include:
- Switch to using the tagges git tarballs
- Include upgrade scripts in the package (under /usr/share/seafile-server/scripts/upgrade
- Make the package depend on seafile-shared, so seafile-client + seafile-client-cli / seafile-server don't conflict
<deleted-account> commented on 2013-11-08 12:26 (UTC)
Updates PKGBUILD which I've verified to work a least on my own server: http://pastebin.com/raw.php?i=wJX1Pd2L
I'd be willing to adopt this package if you want (it's been out-of-date for a while).
ddanier commented on 2013-10-29 12:54 (UTC)
@mbroemme: I'll still wait for the official release. There are currently multiple 2.0.x binary versions available, even multiple server versions. I don't want to put up an PKGBUILD for an old, probably unstable version. Besides ccnet probably needs to be updated first, so we have to wait for this package anyways. Again: seafile has a really bad release policy. I'm sorry to keep you waiting, but I'm not convinced rushing things will bring this package forward. Please see the discussion om the seafile-client package for further details on this issue. The same questions were asked there.
mbroemme commented on 2013-10-29 02:16 (UTC)
@ddanier: You can safely use https://github.com/haiwen/seafile/archive/server-2.0.tar.gz as it is freezed after tagging and no more commits will go into it.
Pinned Comments