- Return to book
- Review this book
- About the author
- Introduction
- 1. Overview
-
2.
Deploying Seafile under Linux
- 2.1. Deploying Seafile with SQLite
- 2.2. Deploying Seafile with MySQL
- 2.3. Config Seahub with Nginx
- 2.4. Enabling Https with Nginx
- 2.5. Config Seahub with Apache
- 2.6. Enabling Https with Apache
- 2.7. Enable syncing via HTTP/HTTPS
- 2.8. Configure Seafile to use LDAP
- 2.9. Start Seafile at System Bootup
- 2.10. Firewall settings
- 2.11. Logrotate
- 2.12. Other Deployment Issues
- 2.13. Common Problems for Setting up Server
- 2.14. Upgrade Seafile server
-
3.
Deploy Seafile under Windows
- 3.1. Download and Setup Seafile Windows Server
- 3.2. Deploy Seafile with MySQL
- 3.3. Deploy Seafile with Apache
- 3.4. Deploy Seafile with Nginx
- 3.5. Install Seafile Server as a Windows Service
- 3.6. Ports used by Seafile Windows Server
- 3.7. Upgrading Seafile Windows Server
- 3.8. Migrate Seafile From Windows To Linux
- 3.9. Garbage Collecting Unused Blocks on Seafile Server
-
4.
Deploy Seafile Pro Edition under Linux
- 4.1. Download and Setup Seafile Professional Server
- 4.2. Migrate from Seafile Community Server
- 4.3. Upgrading Seafile Professional Server
- 4.4. Setup With Amazon S3
- 4.5. Setup With OpenStackSwift
- 4.6. Setup With Ceph
- 4.7. Setup with MariaDB and Ceph
- 4.8. Configurable Options
- 4.9. FAQ
- 4.10. Other Deployment Issues
- 4.11. License
- 5. Server Configuration and Customization
- 6. Administration
- 7. WebDAV and FUSE extensions
- 8. Security and Auditing
- 9. Developing
Components Overview
Seafile server and client consists of several components. Understanding how they work together will save you a lot time in deploying and maintaining Seafile.
Server 4.0
In version 4.0, Seafile supports syncing using HTTP/HTTPS protocol. The architecture has been simplified a lot.
- Seahub (django)：the website. Seafile server package contains a light-weight Python HTTP server gunicorn that serves the website. Seahub runs as an application within gunicorn.
- Seafile server (
seaf-server)：data service daemon, handles raw file upload/download/syncing - Ccnet server (
ccnet-server)： RPC service daemon to enable communication among multiple components.
The picture below shows how Seafile clients access files when you configure Seafile behind Nginx/Apache. The desktop client should turn the option "sync over HTTP/HTTPS" on.
Server 3.x
- Seahub (django)：the website. Seafile server package contains a light-weight Python HTTP server gunicorn that serves the website. Seahub runs as an application within gunicorn.
- FileServer (
fileserver) (It is called HttpServer before version 3.1): handles raw file upload/download functions for Seahub. Due to Gunicorn being poor at handling large files, so we wrote this "FileServer" in the C programming language to serve raw file upload/download. - Seafile server (
seaf-server)：data service daemon - Ccnet server (
ccnet-server)：networking service daemon. In our initial design, Ccnet worked like a traffic bus. All the network traffic between client, server and internal traffic between different components would go through Ccnet. After further development we found that file transfer is improved by utilizing the Seafile daemon component directly.
The picture below shows how Seafile desktop client syncs files with Seafile server:
The picture below shows how Seafile mobile client interacts with Seafile server:
The picture below shows how Seafile mobile client interacts with Seafile server if the server is configured behind Nginx/Apache:
Client
- Applet (
seafile-applet): The GUI front-end - Seafile daemon (
seafile): data service daemon for client - Ccnet daemon (
ccnet): networking service daemon for client