Deploying Seafile under Linux
Here we describe how to deploy Seafile from prebuild binary packages.
Deploy Seafile in Home/Personal Environment
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.
Note: We have prepared an installation script Deploy Seafile with an installation script. The installer offer a quick and easy way to set up a production ready Seafile Server using MariaDB, Memcached and NGINX as a reverse proxy in under 5 minutes.
You can also install Seafile manually without the installation script as following:
- Deploying Seafile with MySQL
- Config Seahub with Nginx
- Enabling Https with Nginx
- Config Seahub with Apache
- Enabling Https with Apache
- Add Memcached, adding memcached is very important if you have more than 50 users.
- Start Seafile at System Bootup
- Firewall settings
Seafile supports a few external user authentication methods.
Other Deployment Issues
Check configuration options for server config options like enabling user registration.
Read here if you have troubles setting up Seafile server
- Read Seafile Server Components Overview to understand how Seafile server works. This will save you a lot of time.
- Common Problems for Setting up Server
- Go to our forum for help.
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.1to 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-serverto ccnet, seafile and seahub.
- For libsearpc, we always use tag
Note: The version numbers of each project has nothing to do with the tag name.