Package Details: seafile 9.0.11-2

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: 2025-01-02 20:02 (UTC)

Pinned Comments

Latest Comments

« First ‹ Previous 1 .. 9 10 11 12 13 14 15 16 17 18 19 .. 47 Next › Last »

pvagner commented on 2016-09-01 05:56 (UTC)

@thealchemist sorry for the late reply. No I haven't changed the systemd service file. I am starting like systemctl start seafile-server@thatfoldername I've described in my previous comment. Anyway I'm getting some seahub tracebacks in the django_requests.log so I am just going try tupdating to freshly released 6.0.2 now.

thealchemist commented on 2016-08-23 14:24 (UTC)

@pvagner: This would mean, your setup is the same despite you use a subdirectory as mentioned in the Wiki. This may be the problem. Did you also change the systemd-service accordingly, i.e. replaced both occurrences of %i (wiki: %h) with your directory name?

pvagner commented on 2016-08-22 08:59 (UTC)

@thealchemist The arch wiki instructions worked for me i.e. I've created a user, created a directory for the whole site inside its home folder, created seafile-server directory in that, unpacked corresponding seahub.

thealchemist commented on 2016-08-16 18:50 (UTC)

Hello, firstly thanks for maintaining these packages. As far as I can tell compiles fine using makepkg or yaourt (Tested on a Cubieboard 2 and Raspberry Pi 2, hence ARMv7). The server also starts when using the systemd service, BUT the seahub web interface is messed, i.e. no images are loaded, instead there is a language list and a login mask when scrolled down. I poke on my nginx configuration for some time now and loosly followed both the seafile documentation (http://manual.seafile.com/build_seafile/server.html --> deployment section) and our own outdated wiki article. My setup only differs in not using a separate <server-url.org> directory. Any idea what I did wrong?

eolianoe commented on 2016-08-12 13:25 (UTC)

Updated to 6.0.0, according to [1] this is a beta version so be careful when updating. [1] https://seacloud.cc/group/3/wiki/server-changelog

TesterMcTest commented on 2016-08-11 05:57 (UTC)

@pvagner @lulingar The Arch installation deploys seafile with sqlite3. However you can migrate it afterwards. The people from seafile offer a migration part in their manual: http://manual.seafile.com/deploy/migrate_from_sqlite_to_mysql.html I did this quite some time back (approx. at 4.0.6). I needed to dump the migration scripts from above into the home directory of the domain I wanted to run seafile on (according to the wiki: $HOME/example.org). Furthermore, if you are having python3 installed you need to change the first line in the python script to: #!/usr/bin/env python2 (note the '2' at the end!). As a recommendation I would run seafile once and set it up properly, so that the migration scripts aren't throwing errors due to missing databases. (I did not do that and I had to comment out the lines and cross my fingers that it still would work :-) )

pvagner commented on 2016-08-10 10:34 (UTC)

I appear to be unable to figure out how to deploy it with mysql as well. According to the docs it's using mysql-python for mysql connection, installing this one does not help though. Running seafile-admin setup will install with sqlite3.

lulingar commented on 2016-08-10 02:02 (UTC)

Using version 5.1.4, I haven't been able to deploy a MySQL-based instance (as per the instructions at https://wiki.archlinux.org/index.php/seafile), even by modifying the seafile-admin script or otherwise. The PKGBUILD was built and installed successfully. Does anyone have any pointers?

Armael commented on 2016-08-09 19:41 (UTC)

Even with openjpeg2 installed (which was not a dependency), the Pillow python library installed by seafile-server.install was not compiled with jpeg support. Thus, after adding a (.jpg) avatar to an account, seahub would crash with the following traceback: http://paste.isomorphis.me/Gqy . A workaround I found (not sure if it's a proper one though) is to install python2-pillow, and replace "Pillow>=2.6.1,<3.0.0" by "Pillow>=2.6.1" in seafile-server.install.

eolianoe commented on 2016-08-01 21:02 (UTC)

Updated to 5.1.4, as previously said the server part is not fully tested. I'm in process to separate the seafile-server and seahub (the front-end https://github.com/haiwen/seahub) in order to get clearer packaging. I you wish to test or help, feel free to send e-mails.