Package Details: seafile 9.0.13-1

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-04-04 12:14 (UTC)

Pinned Comments

Latest Comments

« First ‹ Previous 1 .. 40 41 42 43 44 45 46 47 Next › Last »

wabi commented on 2013-12-19 14:53 (UTC)

Tried to setup a new seafile server with this package. I'm runing "seafile-admin setup" within /srv/seafile as user seafile (who's home is /src/seafile). I can create the config files sucessfully but initializing the database fails: Now initializing seahub database, please wait... /usr/lib/seafile/seafileenv/bin/python2: can't open file 'manage.py': [Errno 2] No such file or directory Error: Seahub syncdb failed Is there any way to create the database config manually and a sql-dump to preload the DB?

kevincox commented on 2013-11-20 22:31 (UTC)

I wouldn't call that unusual, I see it all the time. useradd --home /srv/seafile/ seafile # or if the user already exists. usermod --home /srv/seafile seafile Note that neither of those create the directory. Although personally, I like to give every service their own place in `/home/`. I think it keeps things tidier IMHO.

<deleted-account> commented on 2013-11-20 22:09 (UTC)

Well, you could make /srv/seafile be the home directory for the seafile user. It's unusual, but iirc not impossible.

peacememories commented on 2013-11-20 20:46 (UTC)

gotta ask though. what would be the correct way to run the server in /srv/seafile with your systemd script?

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

« First ‹ Previous 1 .. 40 41 42 43 44 45 46 47 Next › Last »