Jump to content
From ArchWiki

This article or section is out of date.

Reason: please use the first argument of the template to provide a brief explanation. (Discuss in Talk:Seafile)

Seafile is an open source cloud storage system, with advanced support for file syncing, privacy protection and teamwork.

Collections of files are called libraries, and each library can be synced separately. A library can be encrypted with a user chosen password. This password is not stored on the server, so even the server admin cannot view your file contents.

Seafile lets you create groups with file syncing, wiki, and discussion -- enabling easy collaboration around documents within a team.

This article covers the installation of the Seafile server. If you only require a client to access a Seafile server, install seafile-clientAUR or seafileAUR.

## Installation

Install the seafile-serverAUR package. It is part of the split package seafileAUR which produces more than one package, but not all of them are necessarily needed in your case. Consider also installing the seahubAUR package, which provides the web frontend.

## Configuration

Change to the seafile user (automatically created by the seafile-server package). The following commands are to be executed as that user unless otherwise stated.

    $ sudo -u seafile -s /bin/sh

As that user, create the directory layout for the new seafile server instance and change directory to it:

    $ mkdir -p ~/example.org/seafile-server
    $ cd ~/example.org

To create the configuration for the seafile server instance choose and follow the 'setup' section of one of the following options shown in the seafile manual:

- SQLite
- MySQL

Those initial setup steps can be done with the `seafile-admin` command as the seafile user. Be sure to execute them in the correct directory:

Note: seafile-admin only works if you also installed the seahubAUR package beforehand.

    $ cd $HOME/example.org
    $ seafile-admin setup

If you wish to have non-english consistent language support you need to compile your language by executing the following command:

    $ cd $HOME/example.org/seafile-server/seahub/locale/<yourlanguage>/LC_MESSAGES/
    $ msgfmt -o django.mo django.po

Next we need to add this default language to the settings now:

    $ echo "LANGUAGE='<yourlanguage>'" >> ~/example.org/conf/seahub_settings.py

Edit `seafile-server@.service` and replace the two occurences of `%i` in it with the actual `$HOME` for the user set up in #Installation.

If you did not yet setup nginx and if you want to test out Seafile's own web-frontend-implementation seahub purely, you have to edit `seafile-server@.service` and delete the `--fastcgi` parameter from the start script, as fastcgi is not supported with seahub-only.

To manually start your new seafile server, start `seafile-server@example.org.service`.

If it starts up fine, you may also enable the service.

After starting the seafile server daemon, you can create an admin user for your seafile instance:

    $ cd $HOME/example.org
    $ seafile-admin create-admin

### Deploy an instance with Nginx

In order to deploy Seafile's webinterface "seahub" with Nginx, you can use an Nginx configuration similar to this:

    server {
        listen 80;
        server_name www.example.org example.org;
        return 301 https://$server_name$request_uri;
    }

    server {
        listen 443;
        ssl on;
        ssl_certificate /etc/ssl/certs/example.org.crt;
        ssl_certificate_key /etc/ssl/private/server.key;
        server_name www.example.org example.org;

        location / {
            fastcgi_pass    127.0.0.1:8000;
            fastcgi_param   SCRIPT_FILENAME     $document_root$fastcgi_script_name;
            fastcgi_param   PATH_INFO           $fastcgi_script_name;

            fastcgi_param   SERVER_PROTOCOL     $server_protocol;
            fastcgi_param   QUERY_STRING        $query_string;
            fastcgi_param   REQUEST_METHOD      $request_method;
            fastcgi_param   CONTENT_TYPE        $content_type;
            fastcgi_param   CONTENT_LENGTH      $content_length;
            fastcgi_param   SERVER_ADDR         $server_addr;
            fastcgi_param   SERVER_PORT         $server_port;
            fastcgi_param   SERVER_NAME         $server_name;

            fastcgi_param   HTTPS on;
            fastcgi_param   HTTP_SCHEME https;
        }

        location /seafhttp {
            rewrite ^/seafhttp(.*)$ $1 break;
            proxy_pass http://127.0.0.1:8082;
            client_max_body_size 0;
        }

        location /media {
            root {ABSOLUTE_PATH_TO_SEAFILE_USER'S_HOME}/example.org/seafile-server/seahub;
        }
    }

You also have to add the following values to your ccnet.conf and seahub_settings.py if you are using HTTPS with nginx, as uploads fail otherwise [1], [2]. Remember to edit these files as user seafile

    $HOME/example.org/config/ccnet.conf

    SERVICE_URL = https://example.org:8000

    $HOME/example.org/config/seahub_settings.py

    FILE_SERVER_ROOT = 'https://example.org/seafhttp'

## Maintenance

### Upgrading

First, stop each of your seafile server instances (e.g. `seafile-server@example.org.service`, repeat for example.org, foo.bar, etc.).

Upgrade seafile-serverAUR from the Arch User Repository.

Become the user the seafile server instances run as (following commands are to be executed as that user unless otherwise stated):

    $ sudo -u seafile -s

Repeat the following for each seafile server instance:

- Change directory to the server instance's 'seafile-server' subdirectory:

      $ cd /srv/seafile/example.org/seafile-server

- Run the preupgrade script (Or do the steps by hand, see the Seafile wiki):

      $ seahub-preupgrade

- Run the appropriate seafile/seahub upgrade script from the upgrade subdirectory:
  - For a minor upgrade (x.y.a to x.y.b with a < b):

        $ ./upgrade/minor-upgrade.sh

  - For a major upgrade (x.y.a to z.w.b with x < z || y < w):

        $ ./upgrade/upgrade_x.y_z.w.sh

- Repeat the steps for language mentioned in the installation guide

Lastly, start each of your seafile server instances again (e.g. `seafile-server@example.org.service`, repeat for example.org, foo.bar, etc.).

### Running Seafile GC

To release storage space held by unused blocks, you will want to run Seafile's garbage collector.

Specifically, the GC program will remove:

- blocks belonging to nonexistent libraries
- out-dated blocks based on that library's history length limits

First, make sure to shutdown the Seafile program on your server. For Professional Edition v.3.1.11 on, online GC operation is supported.

Now, to see how much garbage will be collected before making changes:

    $ seafserv-gc -c /srv/seafile/example.org/ccnet -d /srv/seafile/example.org/seafile-data --dry-run

If the output looks okay, proceed to run the same command without the --dry-run argument.

## See also

- https://manual.seafile.com/deploy/
- https://manual.seafile.com/deploy/deploy_with_nginx/
- https://manual.seafile.com/deploy/https_with_nginx/
- https://manual.seafile.com/maintain/seafile_gc/

Categories:

- File sharing
- Web applications

Hidden category:

- Pages or sections flagged with Template:Out of date