Deploying Seafile under Linux

Here we describe how to deploy Seafile from prebuild binary packages.

Deploy Seafile in Home/Personal Environment

• Deploying Seafile with SQLite

Deploy Seafile in Production/Enterprise Environment

In production environment we recommend using MySQL as the database and config Seafile web behing Nginx or Apache. For those who are not familiar with Nginx and Apache. We recommend Nginx, since it is easier to config than Apache.

Basic:

• Deploying Seafile with MySQL
• Config Seahub with Nginx
• Enabling Https with Nginx
• Config Seahub with Apache
• Enabling Https with Apache

Advanced:

• Configure Seafile to use LDAP
• Start Seafile at System Bootup
• Firewall settings
• Logrotate
• Add Memcached

Other Deployment Issues

• Deploy Seafile behind NAT
• Deploy Seahub at Non-root domain
• Migrate From SQLite to MySQL

Check configuration options for server config options like enabling user registration.

Read here if you have troubles setting up Seafile server

1. Read Seafile Server Components Overview to understand how Seafile server works. This will save you a lot of time.
2. Common Problems for Setting up Server
3. Use our google group forum or IRC to get help.

Upgrade Seafile Server

• Upgrade Seafile server

For those that want to package Seafile server

If you want to package seafile yourself, (e.g. for your favorite Linux distribution), you should always use the correspondent tags:

• When we release a new version of seafile client, say 3.0.1, we will add tags v3.0.1 to ccnet, seafile and seafile-client.
• Likewise, when we release a new version of seafile server, say 3.0.1, we will add tags v3.0.1-server to ccnet, seafile and seahub.
• For libsearpc, we always use tag v3.0-latest.

Note: The version numbers of each project has nothing to do with the tag name.