mirror of
https://github.com/haiwen/seafile-admin-docs.git
synced 2025-12-25 18:22:48 +00:00
opt:leave first-level-dirs
This commit is contained in:
Junxiang Huang
parent
6b15d29fa0
commit
cf246ba306
|
|
@ -0,0 +1,19 @@
|
|||
# Introduction
|
||||
|
||||
Seafile is an open source cloud storage system for file sync, share and document collaboration. SeaDoc is an extension of Seafile that providing a lightweight online collaborative document feature.
|
||||
|
||||
|
||||
## LICENSE
|
||||
|
||||
The different components of Seafile project are released under different licenses:
|
||||
|
||||
* Seafile iOS client: Apache License v2
|
||||
* Seafile Android client: GPLv3
|
||||
* Desktop syncing client: GPLv2
|
||||
* Seafile Server core: AGPLv3
|
||||
* Seahub (Seafile server Web UI): Apache License v2
|
||||
|
||||
## Contact information
|
||||
|
||||
* Twitter: @seafile <https://twitter.com/seafile>
|
||||
* Forum: <https://forum.seafile.com>
|
||||
|
|
@ -16,7 +16,7 @@ For version below 11.0, if you really want to change a user's ID, you should cre
|
|||
|
||||
Administrator can reset password for a user in "System Admin" page.
|
||||
|
||||
In a private server, the default settings doesn't support users to reset their password by email. If you want to enable this, you have first to [set up notification email](../config/seafile_config/sending_email.md).
|
||||
In a private server, the default settings doesn't support users to reset their password by email. If you want to enable this, you have first to [set up notification email](../config/sending_email.md).
|
||||
|
||||
#### Forgot Admin Account or Password?
|
||||
|
||||
|
|
@ -25,4 +25,4 @@ Your data will not be deleted from the admin account, this only unlocks and chan
|
|||
|
||||
#### User Quota Notice
|
||||
|
||||
Under the seafile-server-latest directory, run `./seahub.sh python-env python seahub/manage.py check_user_quota` , when the user quota exceeds 90%, an email will be sent. If you want to enable this, you have first to [set up notification email](../config/seafile_config/sending_email.md).
|
||||
Under the seafile-server-latest directory, run `./seahub.sh python-env python seahub/manage.py check_user_quota` , when the user quota exceeds 90%, an email will be sent. If you want to enable this, you have first to [set up notification email](../config/sending_email.md).
|
||||
|
|
|
|||
|
|
@ -1536,7 +1536,7 @@ Other
|
|||
### 6.0.6 (2017.01.11)
|
||||
|
||||
* Guest invitation: Prevent the same address can be invited multiple times by the same inviter and by multiple inviters
|
||||
* Guest invitation: Add an regex to prevent certain email addresses be invited (see [roles permissions](../config/authentication/roles_permissions.md#more-about-guest-invitation-feature))
|
||||
* Guest invitation: Add an regex to prevent certain email addresses be invited (see [roles permissions](../config/roles_permissions.md#more-about-guest-invitation-feature))
|
||||
* Office online: support co-authoring
|
||||
* Admin can set users' department and name when creating users
|
||||
* Show total number of files and storage in admin info page
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ There are three config files in the community edition:
|
|||
|
||||
You can also modify most of the config items via web interface.The config items are saved in database table (seahub-db/constance_config). They have a higher priority over the items in config files.
|
||||
|
||||
|
||||
|
||||
|
||||
## Common Customization Tasks
|
||||
|
||||
|
|
@ -14,7 +14,7 @@ Since 11.0 version, switching between the types is possible, but any switch requ
|
|||
|
||||
Before manually manipulating your database, make a database backup, so you can restore your system if anything goes wrong!
|
||||
|
||||
See more about [make a database backup](../../../administration/backup_recovery.md).
|
||||
See more about [make a database backup](../administration/backup_recovery.md).
|
||||
|
||||
## Migrating from local user database to external authentication
|
||||
|
||||
|
|
@ -34,7 +34,7 @@ Open "Internet Options", select "Security" tab, select "Local Intranet" zone.
|
|||
|
||||
Note: Above configuration requires a reboot to take effect.
|
||||
|
||||
|
||||
|
||||
|
||||
Next, we shall test the auto login function on Internet Explorer: visit the website and click "Single Sign-On" link. It should be able to log in directly, otherwise the auto login is malfunctioned.
|
||||
|
||||
|
|
@ -140,7 +140,7 @@ Restart the seafile service to make the above changes take effect:
|
|||
|
||||
If you use a cluster to deploy Seafile, you can use distributed indexing to realize real-time indexing and improve indexing efficiency. The indexing process is as follows:
|
||||
|
||||
|
||||
|
||||
|
||||
### Install redis and modify configuration files
|
||||
|
||||
|
|
@ -55,7 +55,7 @@ SEADOC_SERVER_URL=http://example.seafile.com/sdoc-server
|
|||
- `SEAFILE_MEMCACHED_IMAGE`: Cached server image, default is `memcached:1.6.29`
|
||||
- `SEAFILE_ELASTICSEARCH_IMAGE`: Only valid in pro edition. The elasticsearch image, default is `elasticsearch:8.15.0`.
|
||||
- `SEAFILE_CADDY_IMAGE`: Caddy server image, default is `lucaslorentz/caddy-docker-proxy:2.9`.
|
||||
- `SEADOC_IMAGE`: Only valid after integrating [SeaDoc](../../extension/extra_components/setup_seadoc.md). SeaDoc server image, default is `seafileltd/sdoc-server:1.0-latest`.
|
||||
- `SEADOC_IMAGE`: Only valid after integrating [SeaDoc](../extension/setup_seadoc.md). SeaDoc server image, default is `seafileltd/sdoc-server:1.0-latest`.
|
||||
|
||||
### Persistent Volume Configurations
|
||||
|
||||
|
|
@ -63,7 +63,7 @@ SEADOC_SERVER_URL=http://example.seafile.com/sdoc-server
|
|||
- `SEAFILE_MYSQL_VOLUME`: The volume directory of MySQL data, default is `/opt/seafile-mysql/db`.
|
||||
- `SEAFILE_CADDY_VOLUME`: The volume directory of Caddy data used to store certificates obtained from Let's Encrypt's, default is `/opt/seafile-caddy`.
|
||||
- `SEAFILE_ELASTICSEARCH_VOLUME`: Only valid in pro edition. The volume directory of Elasticsearch data, default is `/opt/seafile-elasticsearch/data`.
|
||||
- `SEADOC_VOLUME`: Only valid after integrating [SeaDoc](../../extension/extra_components/setup_seadoc.md). The volume directory of [SeaDoc server data](../../extension/extra_components/setup_seadoc.md#seadoc-directory-structure), default is `/opt/seadoc-data`.
|
||||
- `SEADOC_VOLUME`: Only valid after integrating [SeaDoc](../extension/setup_seadoc.md). The volume directory of [SeaDoc server data](../extension/setup_seadoc.md#seadoc-directory-structure), default is `/opt/seadoc-data`.
|
||||
|
||||
## MySQL configurations
|
||||
|
||||
|
|
@ -51,12 +51,12 @@ OCM_REMOTE_SERVERS = [
|
|||
### Share library to other server
|
||||
|
||||
In the library sharing dialog jump to "Share to other server", you can share this library to users of another server with "Read-Only" or "Read-Write" permission. You can also view shared records and cancel sharing.
|
||||
|
||||
|
||||
|
||||
### View be shared libraries
|
||||
|
||||
You can jump to "Shared from other servers" page to view the libraries shared by other servers and cancel the sharing.
|
||||
|
||||
|
||||
|
||||
And enter the library to view, download or upload files.
|
||||
|
||||
|
||||
|
|
@ -6,7 +6,7 @@ You can add/edit roles and permission for users. A role is just a group of users
|
|||
|
||||
`can_add_public_repo` is to set whether a role can create a public library, default is "False". **Note:**The `can_add_public_repo` option will not take effect if you configure global `CLOUD_MODE = True`.
|
||||
|
||||
The `storage_ids` permission is used for assigning storage backends to users with specific role. More details can be found in [multiple storage backends](../../../setup/advanced_topics/multiple_storage_backends.md).
|
||||
The `storage_ids` permission is used for assigning storage backends to users with specific role. More details can be found in [multiple storage backends](../setup/setup_with_multiple_storage_backends.md).
|
||||
|
||||
Since version 10.0, `upload_rate_limit` and `download_rate_limit` are added to limit upload and download speed for users with different roles. **After configured the rate limit, run the following command in the `seafile-server-latest` directory to make the configuration take effect**:
|
||||
|
||||
|
|
@ -39,21 +39,21 @@ If you use Microsoft Azure SAML app to achieve single sign-on, please follow the
|
|||
|
||||
**Second**, setup the _Identifier_, _Reply URL_, and _Sign on URL_ of the SAML app based on your service URL, refer to: [enable single sign-on for saml app](https://learn.microsoft.com/en-us/azure/active-directory/manage-apps/add-application-portal-setup-sso). The format of the _Identifier_, _Reply URL_, and _Sign on URL_ are: https://example.com/saml2/metadata/, https://example.com/saml2/acs/, https://example.com/, e.g.:
|
||||
|
||||
|
||||
|
||||
|
||||
**Next**, [edit saml attributes & claims](https://learn.microsoft.com/en-us/azure/active-directory/develop/saml-claims-customization). Keep the default attributes & claims of SAML app unchanged, the _uid_ attribute must be added, the _mail_ and _name_ attributes are optional, e.g.:
|
||||
|
||||
|
||||
|
||||
|
||||
**Next**, download the base64 format SAML app's certificate and rename to idp.crt:
|
||||
|
||||
|
||||
|
||||
|
||||
and put it under the certs directory(`/opt/seafile/seahub-data/certs`).
|
||||
|
||||
**Next**, copy the metadata URL of the SAML app:
|
||||
|
||||
|
||||
|
||||
|
||||
and paste it into the `SAML_REMOTE_METADATA_URL` option in seahub_settings.py, e.g.:
|
||||
|
||||
|
|
@ -114,7 +114,7 @@ If you use Microsoft ADFS to achieve single sign-on, please follow the steps bel
|
|||
|
||||
* Locate the _Token-signing_ certificate. Right-click the certificate and select **View Certificate**.
|
||||
|
||||
|
||||
|
||||
|
||||
* In the dialog box, select the **Details** tab.
|
||||
|
||||
|
|
@ -155,7 +155,7 @@ SAML_REMOTE_METADATA_URL = 'https://temp.adfs.com/federationmetadata/2007-06/fed
|
|||
|
||||
* Select **Import data about the relying party published online or on a local network**, type your metadate url in **Federation metadata address (host name or URL)**, and then click **Next**. Your metadate url format is: `https://example.com/saml2/metadata/`, e.g.:
|
||||
|
||||
|
||||
|
||||
|
||||
* On the **Specify Display Name** page type a name in **Display name**, e.g. `Seafile`, under **Notes** type a description for this relying party trust, and then click **Next**.
|
||||
|
||||
|
|
@ -106,4 +106,4 @@ interval = 86400 # The unit is second(s), the default frequency is one day, th
|
|||
|
||||
```
|
||||
|
||||
**NOTE**: [Access the AWS elasticsearch service using HTTPS](../authentication/details_about_file_search.md#access-the-aws-elasticsearch-service-using-https)
|
||||
**NOTE**: [Access the AWS elasticsearch service using HTTPS](./details_about_file_search.md#access-the-aws-elasticsearch-service-using-https)
|
||||
|
|
@ -213,7 +213,7 @@ upload_limit = 100
|
|||
download_limit = 100
|
||||
```
|
||||
|
||||
Since Seafile 11.0.7 Pro, you can ask file server to check virus for every file uploaded with web APIs. Find more options about virus scanning at [virus scan](../../extension/virus_scan/virus_scan.md).
|
||||
Since Seafile 11.0.7 Pro, you can ask file server to check virus for every file uploaded with web APIs. Find more options about virus scanning at [virus scan](../extension/virus_scan.md).
|
||||
|
||||
```
|
||||
[fileserver]
|
||||
|
|
@ -280,12 +280,12 @@ memcached_options = --SERVER=<the IP of Memcached Server> --POOL-MIN=10 --POOL-M
|
|||
|
||||
You may configure Seafile to use various kinds of object storage backends.
|
||||
|
||||
- [S3 or S3-compatible object storage](../../setup/advanced_topics/setup_with_amazon_s3.md)
|
||||
- [Ceph RADOS](../../setup/advanced_topics/setup_with_ceph.md)
|
||||
- [Alibaba Cloud OSS](../../setup/advanced_topics/setup_with_oss.md)
|
||||
- [OpenStack Swift](../../setup/advanced_topics/setup_with_swift.md)
|
||||
- [S3 or S3-compatible object storage](../setup/setup_with_amazon_s3.md)
|
||||
- [Ceph RADOS](../setup/setup_with_ceph.md)
|
||||
- [Alibaba Cloud OSS](../setup/setup_with_oss.md)
|
||||
- [OpenStack Swift](../setup/setup_with_swift.md)
|
||||
|
||||
You may also configure Seafile to use [multiple storage backends](../../setup/advanced_topics/multiple_storage_backends.md) at the same time.
|
||||
You may also configure Seafile to use [multiple storage backends](../setup/setup_with_multiple_storage_backends.md) at the same time.
|
||||
|
||||
## Cluster
|
||||
|
||||
|
|
@ -312,7 +312,7 @@ rpc_slow_threshold = 5000
|
|||
|
||||
```
|
||||
|
||||
You can find `seafile_slow_rpc.log` in `logs/slow_logs`. You can also use [log-rotate](../../setup_binary/other_deployment_notes/using_logrotate.md) to rotate the log files. You just need to send `SIGUSR2` to `seaf-server` process. The slow log file will be closed and reopened.
|
||||
You can find `seafile_slow_rpc.log` in `logs/slow_logs`. You can also use [log-rotate](../setup_binary/using_logrotate.md) to rotate the log files. You just need to send `SIGUSR2` to `seaf-server` process. The slow log file will be closed and reopened.
|
||||
|
||||
Since 9.0.2 Pro, the signal to trigger log rotation has been changed to `SIGUSR1`. This signal will trigger rotation for all log files opened by seaf-server. You should change your log rotate settings accordingly.
|
||||
|
||||
|
|
@ -77,7 +77,7 @@ ADDITIONAL_SHARE_DIALOG_NOTE = {
|
|||
|
||||
Result:
|
||||
|
||||
|
||||
|
||||
|
||||
## Add custom navigation items
|
||||
|
||||
|
|
@ -117,7 +117,7 @@ ADDITIONAL_APP_BOTTOM_LINKS = {
|
|||
|
||||
Result:
|
||||
|
||||
|
||||
|
||||
|
||||
## Add more links to about dialog
|
||||
|
||||
|
|
@ -130,4 +130,4 @@ ADDITIONAL_ABOUT_DIALOG_LINKS = {
|
|||
|
||||
Result:
|
||||
|
||||
|
||||
|
||||
|
|
@ -2,8 +2,8 @@
|
|||
|
||||
Build Seafile
|
||||
|
||||
* [How to Build Seafile](./build_seafile/README.md)
|
||||
* [How to Setup Development Environment](../config/seafile_config/env.md)
|
||||
* [How to Build Seafile](./build_seafile.md)
|
||||
* [How to Setup Development Environment](../config/env.md)
|
||||
|
||||
Seafile Open API
|
||||
|
||||
|
|
|
|||
|
|
@ -256,12 +256,12 @@ The test should cover these steps at least:
|
|||
* The setup process is ok
|
||||
* After `seafile.sh start` and `seahub.sh start`, you can login from a browser.
|
||||
* Uploading/Downloading files through a web browser works correctly.
|
||||
* Seafile [WebDAV](../../extension/extra_components/webdav.md) server works correctly
|
||||
* Seafile [WebDAV](../extension/webdav.md) server works correctly
|
||||
|
||||
### <a id="wiki-test-upgrading"></a> Test upgrading from a previous version
|
||||
|
||||
* Download the package of the previous version seafile server, and setup it.
|
||||
* Upgrading according to [the manual](../../upgrade/upgrade.md)
|
||||
* Upgrading according to [the manual](../upgrade/upgrade.md)
|
||||
* After the upgrade, check the functionality is ok:
|
||||
* Uploading/Downloading files through a web browser works correctly.
|
||||
* Seafile [WebDAV](../../extension/extra_components/webdav.md) server works correctly
|
||||
* Seafile [WebDAV](../extension/webdav.md) server works correctly
|
||||
|
|
@ -232,7 +232,7 @@ Then, you can visit <http://127.0.0.1:8000/> to use Seafile.
|
|||
|
||||
## The Final Directory Structure
|
||||
|
||||
|
||||
|
||||
|
||||
## More
|
||||
|
||||
|
|
@ -76,7 +76,7 @@ For more information about Collabora Online and how to deploy it, please refer t
|
|||
|
||||
## Config Seafile
|
||||
|
||||
**NOTE:** You must [enable https](../../setup_binary/ce/https_with_nginx.md) with valid TLS/SSL certificates with Seafile to use Collabora Online.
|
||||
**NOTE:** You must [enable https](../setup_binary/https_with_nginx.md) with valid TLS/SSL certificates with Seafile to use Collabora Online.
|
||||
|
||||
Add following config option to seahub_settings.py:
|
||||
|
||||
|
|
@ -116,7 +116,7 @@ Then restart Seafile.
|
|||
|
||||
Click an office file in Seafile web interface, you will see the online preview rendered by LibreOffice online. Here is an example:
|
||||
|
||||
|
||||
|
||||
|
||||
## Trouble shooting
|
||||
|
||||
|
|
@ -139,7 +139,7 @@ Notification server is enabled on the remote server xxxx
|
|||
|
||||
There is no additional features for notification server in the Pro Edition. It works the same as in community edition.
|
||||
|
||||
If you enable [clustering](../../setup_binary/pro/deploy_in_a_cluster.md), You need to deploy notification server on one of the servers, or a separate server. The load balancer should forward websockets requests to this node.
|
||||
If you enable [clustering](../setup_binary/deploy_in_a_cluster.md), You need to deploy notification server on one of the servers, or a separate server. The load balancer should forward websockets requests to this node.
|
||||
|
||||
On each Seafile frontend node, the notification server configuration should be the same as in community edition:
|
||||
|
||||
|
|
@ -64,7 +64,7 @@ Then restart
|
|||
|
||||
After you click the document you specified in seahub_settings.py, you will see the new preview page.
|
||||
|
||||
|
||||
|
||||
|
||||
## Trouble shooting
|
||||
|
||||
|
|
@ -20,7 +20,7 @@ SeaDoc excels at:
|
|||
|
||||
The SeaDoc archticture is demonstrated as below:
|
||||
|
||||
|
||||
|
||||
|
||||
Here is the workflow when a user open sdoc file in browser
|
||||
|
||||
|
|
@ -44,7 +44,7 @@ SeaDoc has the following deployment methods:
|
|||
|
||||
#### Download and modify seadoc.yml
|
||||
|
||||
Download [seadoc.yml](../../docker/seadoc/1.0/seadoc.yml) sample file to your host. Then modify the file according to your environment. The following fields are needed to be modified:
|
||||
Download [seadoc.yml](../docker/seadoc/1.0/seadoc.yml) sample file to your host. Then modify the file according to your environment. The following fields are needed to be modified:
|
||||
|
||||
- `DB_HOST`: MySQL host
|
||||
- `DB_PORT`: MySQL port
|
||||
|
|
@ -127,7 +127,7 @@ Placeholder spot for shared volumes. You may elect to store certain persistent i
|
|||
|
||||
### About SSL
|
||||
|
||||
From Seafile 12.0, the SSL is handled by [***Caddy***](https://caddyserver.com/docs/). Caddy is a modern open source web server that mainly binds external traffic and internal services in [seafile docker](./seafile_docker_structures.md). The default caddy image is [`lucaslorentz/caddy-docker-proxy:2.9`](https://github.com/lucaslorentz/caddy-docker-proxy), which user only needs to correctly configure the following fields in `.env` to automatically complete the acquisition and update of the certificate:
|
||||
From Seafile 12.0, the SSL is handled by [***Caddy***](https://caddyserver.com/docs/). Caddy is a modern open source web server that mainly binds external traffic and internal services in [seafile docker](../setup/overview.md). The default caddy image is [`lucaslorentz/caddy-docker-proxy:2.9`](https://github.com/lucaslorentz/caddy-docker-proxy), which user only needs to correctly configure the following fields in `.env` to automatically complete the acquisition and update of the certificate:
|
||||
|
||||
```shell
|
||||
SEAFILE_SERVER_PROTOCOL=https
|
||||
|
|
@ -33,9 +33,9 @@ cd seafile-server-latest
|
|||
```
|
||||
|
||||
If a virus was detected, you can see scan records and delete infected files on the Virus Scan page in the admin area.
|
||||
|
||||
|
||||
|
||||
**INFO**: If you directly use clamav command line tool to scan files, scanning files will takes a lot of time. If you want to speed it up, we recommend to run Clamav as a daemon. Please refer to [Run ClamAV as a Daemon](delpoy_clamav_with_seafile.md)
|
||||
**INFO**: If you directly use clamav command line tool to scan files, scanning files will takes a lot of time. If you want to speed it up, we recommend to run Clamav as a daemon. Please refer to [Run ClamAV as a Daemon](./deploy_clamav_with_seafile.md)
|
||||
|
||||
When run Clamav as a daemon, the `scan_command` should be `clamdscan` in `seafile.conf`. An example for Clamav-daemon is provided below:
|
||||
```
|
||||
|
|
@ -1,6 +1,6 @@
|
|||
## Kerberos
|
||||
|
||||
NOTE: Since version 7.0, this documenation is deprecated. Users should use Apache as a proxy server for Kerberos authentication. Then configure Seahub by the instructions in [Remote User Authentication](../config/authentication/remote_user.md).
|
||||
NOTE: Since version 7.0, this documenation is deprecated. Users should use Apache as a proxy server for Kerberos authentication. Then configure Seahub by the instructions in [Remote User Authentication](../config/remote_user.md).
|
||||
|
||||
[Kerberos](https://web.mit.edu/kerberos/) is a widely used single sign on (SSO) protocol. Seafile server supports authentication via Kerberos. It allows users to log in to Seafile without entering credentials again if they have a kerberos ticket.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# Seafile Docker Cluster Deployment
|
||||
|
||||
Seafile Docker cluster deployment requires "sticky session" settings in the load balancer. Otherwise sometimes folder download on the web UI can't work properly. Read the [Load Balancer Setting](../../setup_binary/pro/deploy_in_a_cluster.md#load-balancer-setting) for details.
|
||||
Seafile Docker cluster deployment requires "sticky session" settings in the load balancer. Otherwise sometimes folder download on the web UI can't work properly. Read the [Load Balancer Setting](../setup_binary/deploy_in_a_cluster.md#load-balancer-setting) for details.
|
||||
|
||||
## Environment
|
||||
|
||||
|
|
@ -18,7 +18,7 @@ kubectl create secret docker-registry regcred --docker-server=docker.seadrive.or
|
|||
|
||||
## YAML
|
||||
|
||||
Seafile mainly involves three different services, namely database service, cache service and seafile service. Since these three services do not have a direct dependency relationship, we need to separate them from the entire docker-compose.yml (in this manual, we use [Seafile 12 PRO](../../docker/pro/seafile-server.yml)) and divide them into three pods. For each pod, we need to define a series of YAML files for k8s to read, and we will store these YAMLs in `/opt/seafile-k8s-yaml`. This series of YAML mainly includes **Deployment** for pod management and creation, **Service** for exposing services to the external network, **PersistentVolume** for defining the location of a volume used for persistent storage on the host and **Persistentvolumeclaim** for declaring the use of persistent storage in the container. For futher configuration details, you can refer [the official documents](https://kubernetes.io/docs/tasks/configure-pod-container/).
|
||||
Seafile mainly involves three different services, namely database service, cache service and seafile service. Since these three services do not have a direct dependency relationship, we need to separate them from the entire docker-compose.yml (in this manual, we use [Seafile 12 PRO](../docker/pro/seafile-server.yml)) and divide them into three pods. For each pod, we need to define a series of YAML files for k8s to read, and we will store these YAMLs in `/opt/seafile-k8s-yaml`. This series of YAML mainly includes **Deployment** for pod management and creation, **Service** for exposing services to the external network, **PersistentVolume** for defining the location of a volume used for persistent storage on the host and **Persistentvolumeclaim** for declaring the use of persistent storage in the container. For futher configuration details, you can refer [the official documents](https://kubernetes.io/docs/tasks/configure-pod-container/).
|
||||
|
||||
### mariadb
|
||||
|
||||
|
|
@ -3,7 +3,7 @@
|
|||
Seafile docker based installation consist of the following components (docker images):
|
||||
|
||||
- Seafile server: Seafile core services, see [Seafile Components](../introduction/components.md) for the details.
|
||||
- Sdoc server: SeaDoc server, provide a lightweight online collaborative document editor, see [SeaDoc](../extension/extra_components/setup_seadoc.md#architecture) for the details.
|
||||
- Sdoc server: SeaDoc server, provide a lightweight online collaborative document editor, see [SeaDoc](../extension/setup_seadoc.md#architecture) for the details.
|
||||
- Database: Stores data related to Seafile and SeaDoc.
|
||||
- Memcached: Cache server.
|
||||
- Caddy: Caddy server enables user to access the Seafile service (i.e., Seafile server and Sdoc server) externally and handles `SSL` configuration
|
||||
|
|
|
|||
|
|
@ -122,11 +122,11 @@ Enter the username and password according to the prompts. You now have a new adm
|
|||
|
||||
## Backup and recovery
|
||||
|
||||
Follow the instructions in [Backup and restore for Seafile Docker](../../administration/backup_recovery.md)
|
||||
Follow the instructions in [Backup and restore for Seafile Docker](../administration/backup_recovery.md)
|
||||
|
||||
## Garbage collection
|
||||
|
||||
When files are deleted, the blocks comprising those files are not immediately removed as there may be other files that reference those blocks (due to the magic of deduplication). To remove them, Seafile requires a ['garbage collection'](../../administration/seafile_gc.md) process to be run, which detects which blocks no longer used and purges them. (**NOTE:** for technical reasons, the GC process does not guarantee that _every single_ orphan block will be deleted.)
|
||||
When files are deleted, the blocks comprising those files are not immediately removed as there may be other files that reference those blocks (due to the magic of deduplication). To remove them, Seafile requires a ['garbage collection'](../administration/seafile_gc.md) process to be run, which detects which blocks no longer used and purges them. (**NOTE:** for technical reasons, the GC process does not guarantee that _every single_ orphan block will be deleted.)
|
||||
|
||||
The required scripts can be found in the `/scripts` folder of the docker container. To perform garbage collection, simply run `docker exec seafile /scripts/gc.sh`. For the community edition, this process will stop the seafile server, but it is a relatively quick process and the seafile server will start automatically once the process has finished. The Professional supports an online garbage collection.
|
||||
|
||||
|
|
@ -140,7 +140,7 @@ docker exec -it seafile /bin/bash
|
|||
|
||||
### About SSL and Caddy
|
||||
|
||||
From Seafile 12.0, the SSL is handled by [***Caddy***](https://caddyserver.com/docs/). Caddy is a modern open source web server that mainly binds external traffic and internal services in [seafile docker](./seafile_docker_structures.md). The default caddy image is [`lucaslorentz/caddy-docker-proxy:2.9`](https://github.com/lucaslorentz/caddy-docker-proxy), which user only needs to correctly configure the following fields in `.env` to automatically complete the acquisition and update of the certificate:
|
||||
From Seafile 12.0, the SSL is handled by [***Caddy***](https://caddyserver.com/docs/). Caddy is a modern open source web server that mainly binds external traffic and internal services in [seafile docker](./overview.md). The default caddy image is [`lucaslorentz/caddy-docker-proxy:2.9`](https://github.com/lucaslorentz/caddy-docker-proxy), which user only needs to correctly configure the following fields in `.env` to automatically complete the acquisition and update of the certificate:
|
||||
|
||||
```shell
|
||||
SEAFILE_SERVER_PROTOCOL=https
|
||||
|
|
@ -80,7 +80,7 @@ The following fields merit particular attention:
|
|||
- `SEAFILE_ADMIN_EMAIL`: Admin username
|
||||
- `SEAFILE_ADMIN_PASSWORD`: Admin password
|
||||
|
||||
NOTE: SSL is now handled by the [caddy server](./setup_community_edition.md#about-ssl-and-caddy) from 12.0.
|
||||
NOTE: SSL is now handled by the [caddy server](./setup_ce_by_docker.md#about-ssl-and-caddy) from 12.0.
|
||||
|
||||
To conclude, set the directory permissions of the Elasticsearch volumne:
|
||||
|
||||
|
|
@ -170,11 +170,11 @@ All Seafile log files are stored in `/opt/seafile-data/seafile/logs` whereas all
|
|||
|
||||
## Backup and Recovery
|
||||
|
||||
Follow the instructions in [Backup and restore for Seafile Docker](../../administration/backup_recovery.md)
|
||||
Follow the instructions in [Backup and restore for Seafile Docker](../administration/backup_recovery.md)
|
||||
|
||||
## Garbage Collection
|
||||
|
||||
When files are deleted, the blocks comprising those files are not immediately removed as there may be other files that reference those blocks (due to the magic of deduplication). To remove them, Seafile requires a ['garbage collection'](../../administration/seafile_gc.md) process to be run, which detects which blocks no longer used and purges them. (NOTE: for technical reasons, the GC process does not guarantee that _every single_ orphan block will be deleted.)
|
||||
When files are deleted, the blocks comprising those files are not immediately removed as there may be other files that reference those blocks (due to the magic of deduplication). To remove them, Seafile requires a ['garbage collection'](../administration/seafile_gc.md) process to be run, which detects which blocks no longer used and purges them. (NOTE: for technical reasons, the GC process does not guarantee that _every single_ orphan block will be deleted.)
|
||||
|
||||
The required scripts can be found in the `/scripts` folder of the docker container. To perform garbage collection, simply run `docker exec seafile /scripts/gc.sh`. For the community edition, this process will stop the seafile server, but it is a relatively quick process and the seafile server will start automatically once the process has finished. The Professional supports an online garbage collection.
|
||||
|
||||
|
|
@ -4,7 +4,7 @@
|
|||
|
||||
To setup Seafile Professional Server with Amazon S3:
|
||||
|
||||
- Setup the basic Seafile Professional Server following the guide on [Download and setup Seafile Professional Server](../../../setup_binary/pro/installation.md)
|
||||
- Setup the basic Seafile Professional Server following the guide on [Download and setup Seafile Professional Server](../setup_binary/installation_pro.md)
|
||||
- Install the python `boto` library. It's needed to access S3 service.
|
||||
```
|
||||
# Version 10.0 or earlier
|
||||
|
|
@ -49,7 +49,7 @@ use_v4_signature = true
|
|||
aws_region = eu-central-1
|
||||
```
|
||||
|
||||
You also need to add [memory cache configurations](../../../config/seafile_config/seafile-conf.md#cache-pro-edition-only).
|
||||
You also need to add [memory cache configurations](../config/seafile-conf.md#cache-pro-edition-only).
|
||||
|
||||
We'll explain the configurations below:
|
||||
|
||||
|
|
@ -131,7 +131,7 @@ use_v4_signature = true
|
|||
aws_region = <region name for storage provider>
|
||||
```
|
||||
|
||||
You also need to add [memory cache configurations](../../../config/seafile_config/seafile-conf.md#cache-pro-edition-only).
|
||||
You also need to add [memory cache configurations](../config/seafile-conf.md#cache-pro-edition-only).
|
||||
|
||||
We'll explain the configurations below:
|
||||
|
||||
|
|
@ -178,7 +178,7 @@ host = 192.168.1.123:8080
|
|||
path_style_request = true
|
||||
```
|
||||
|
||||
You also need to add [memory cache configurations](../../../config/seafile_config/seafile-conf.md#cache-pro-edition-only).
|
||||
You also need to add [memory cache configurations](../config/seafile-conf.md#cache-pro-edition-only).
|
||||
|
||||
We'll explain the configurations below:
|
||||
|
||||
|
|
@ -63,7 +63,7 @@ ceph_config = /etc/ceph/ceph.conf
|
|||
pool = seafile-fs
|
||||
```
|
||||
|
||||
You also need to add [memory cache configurations](../../../config/seafile_config/seafile-conf.md#cache-pro-edition-only).
|
||||
You also need to add [memory cache configurations](../config/seafile-conf.md#cache-pro-edition-only).
|
||||
|
||||
It's required to create separate pools for commit, fs, and block objects.
|
||||
|
||||
|
|
@ -43,7 +43,7 @@ storage_classes_file = /opt/seafile_storage_classes.json
|
|||
* enable_storage_classes ：If this is set to true, the storage class feature is enabled. You must define the storage classes in a JSON file provided in the next configuration option.
|
||||
* storage_classes_file：Specifies the path for the JSON file that contains the storage class definition.
|
||||
|
||||
You also need to add [memory cache configurations](../../../config/seafile_config/seafile-conf.md#cache-pro-edition-only) to `seafile.conf`.
|
||||
You also need to add [memory cache configurations](../config/seafile-conf.md#cache-pro-edition-only) to `seafile.conf`.
|
||||
|
||||
### Notes for Docker Installs
|
||||
|
||||
|
|
@ -67,7 +67,7 @@ enable_storage_classes = true
|
|||
storage_classes_file = /shared/conf/seafile_storage_classes.json
|
||||
```
|
||||
|
||||
You also need to add [memory cache configurations](../../../config/seafile_config/seafile-conf.md#cache-pro-edition-only) to `seafile.conf`.
|
||||
You also need to add [memory cache configurations](../config/seafile-conf.md#cache-pro-edition-only) to `seafile.conf`.
|
||||
|
||||
## Defining Storage Backends
|
||||
|
||||
|
|
@ -4,7 +4,7 @@
|
|||
|
||||
To setup Seafile Professional Server with Alibaba OSS:
|
||||
|
||||
* Setup the basic Seafile Professional Server following the guide on [Download and setup Seafile Professional Server](../../../setup_binary/pro/installation.md)
|
||||
* Setup the basic Seafile Professional Server following the guide on [Download and setup Seafile Professional Server](../setup_binary/installation_pro.md)
|
||||
* Install the python `oss2` library: `sudo pip install oss2==2.3.0`.For more installation help, please refer to [this document](https://www.alibabacloud.com/help/en/object-storage-service/latest/python-preface).
|
||||
* Install and configure memcached or Redis. For best performance, Seafile requires enable memory cache for objects. We recommend to allocate at least 128MB memory for Memcached or Redis.
|
||||
|
||||
|
|
@ -34,7 +34,7 @@ key = <your-key>
|
|||
region = beijing
|
||||
```
|
||||
|
||||
You also need to add [memory cache configurations](../../../config/seafile_config/seafile-conf.md#cache-pro-edition-only).
|
||||
You also need to add [memory cache configurations](../config/seafile-conf.md#cache-pro-edition-only).
|
||||
|
||||
It's required to create separate buckets for commit, fs, and block objects. For performance and to save network traffic costs, you should create buckets within the region where the seafile server is running.
|
||||
|
||||
|
|
@ -76,7 +76,7 @@ Compared with the configuration under the classic network, the above configurati
|
|||
|
||||
`endpoint` is a general option, you can also set it to the OSS access address under the classic network, and it will work as well.
|
||||
|
||||
You also need to add [memory cache configurations](../../../config/seafile_config/seafile-conf.md#cache-pro-edition-only).
|
||||
You also need to add [memory cache configurations](../config/seafile-conf.md#cache-pro-edition-only).
|
||||
|
||||
### Use HTTPS connections to OSS
|
||||
|
||||
|
|
@ -1,6 +1,6 @@
|
|||
# Setup With OpenStack Swift
|
||||
|
||||
This backend uses the native Swift API. Previously users can only use the S3-compatibility layer of Swift. That way is obsolete now. The old documentation is still available [here](setup_with_openstackswift.md).
|
||||
This backend uses the native Swift API. Previously users can only use the S3-compatibility layer of Swift. That way is obsolete now. <!--The old documentation is still available [here](setup_with_openstackswift.md).-->
|
||||
|
||||
Since version 6.3, OpenStack Swift v3.0 API is supported.
|
||||
|
||||
|
|
@ -8,7 +8,7 @@ Since version 6.3, OpenStack Swift v3.0 API is supported.
|
|||
|
||||
To setup Seafile Professional Server with Swift:
|
||||
|
||||
* Setup the basic Seafile Professional Server following the guide on [Download and setup Seafile Professional Server](../../../setup_binary/pro/installation.md)
|
||||
* Setup the basic Seafile Professional Server following the guide on [Download and setup Seafile Professional Server](../setup_binary/installation_pro.md)
|
||||
* Install and configure memcached or Redis. For best performance, Seafile requires enable memory cache for objects. We recommend to at least allocate 128MB memory for memcached.
|
||||
|
||||
## Modify Seafile.conf
|
||||
|
|
@ -48,7 +48,7 @@ region = yourRegion
|
|||
|
||||
```
|
||||
|
||||
You also need to add [memory cache configurations](../../../config/seafile_config/seafile-conf.md#cache-pro-edition-only).
|
||||
You also need to add [memory cache configurations](../config/seafile-conf.md#cache-pro-edition-only).
|
||||
|
||||
The above config is just an example. You should replace the options according to your own environment.
|
||||
|
||||
|
|
@ -12,7 +12,7 @@ The Seafile cluster solution employs a 3-tier architecture:
|
|||
|
||||
This architecture scales horizontally. That means, you can handle more traffic by adding more machines. The architecture is visualized in the following picture.
|
||||
|
||||
|
||||
|
||||
|
||||
There are two main components on the Seafile server node: web server (Nginx/Apache) and Seafile app server. The web server passes requests from the clients to Seafile app server. The Seafile app servers work independently. They don't know about each other's state. That means each app server can fail independently without affecting other app server instances. The load balancer is responsible for detecting failure and re-routing requests.
|
||||
|
||||
|
|
@ -88,7 +88,7 @@ haiwen
|
|||
|
||||
### Setup Seafile
|
||||
|
||||
Please follow [Download and Setup Seafile Professional Server With MySQL](../installation.md) to setup a single Seafile server node.
|
||||
Please follow [Download and Setup Seafile Professional Server With MySQL](./installation_pro.md) to setup a single Seafile server node.
|
||||
|
||||
Note: **Use the load balancer's address or domain name for the server address. Don't use the local IP address of each Seafile server machine. This assures the user will always access your service via the load balancers.**
|
||||
|
||||
|
|
@ -147,7 +147,7 @@ health_check_port = 12345
|
|||
|
||||
#### seahub_settings.py
|
||||
|
||||
You must setup and use memory cache when deploying Seafile cluster. Refer to ["memory cache"](../../../config/seafile_config/seahub_settings_py.md#cache) to configure memory cache in Seahub.
|
||||
You must setup and use memory cache when deploying Seafile cluster. Refer to ["memory cache"](../config/seahub_settings_py.md#cache) to configure memory cache in Seahub.
|
||||
|
||||
Also add following options to seahub_setting.py. These settings tell Seahub to store avatar in database and cache avatar in memcached, and store css CACHE to local memory.
|
||||
|
||||
|
|
@ -196,10 +196,10 @@ CREATE TABLE `avatar_uploaded` (`filename` TEXT NOT NULL, `filename_md5` CHAR(32
|
|||
You also need to add the settings for backend cloud storage systems to the config files.
|
||||
|
||||
* For NFS: [Setup Seafile cluster with NFS](setup_seafile_cluster_with_nfs.md)
|
||||
* For S3: [Setup With Amazon S3](../../../setup/advanced_topics/setup_with_amazon_s3.md)
|
||||
* For OpenStack Swift: [Setup With OpenStackSwift](../../../setup/advanced_topics/setup_with_swift.md)
|
||||
* For Ceph: [Setup With Ceph](../../../setup/advanced_topics/setup_with_ceph.md)
|
||||
* For OSS: [Setup With Alibaba OSS](../../../setup/advanced_topics/setup_with_oss.md)
|
||||
* For S3: [Setup With Amazon S3](../setup/setup_with_amazon_s3.md)
|
||||
* For OpenStack Swift: [Setup With OpenStackSwift](../setup/setup_with_swift.md)
|
||||
* For Ceph: [Setup With Ceph](../setup/setup_with_ceph.md)
|
||||
* For OSS: [Setup With Alibaba OSS](../setup/setup_with_oss.md)
|
||||
|
||||
### Setup Nginx/Apache and HTTP
|
||||
|
||||
|
|
@ -207,8 +207,8 @@ Nginx/Apache with HTTP need to set it up on each machine running Seafile server.
|
|||
|
||||
Please check the following documents on how to setup HTTP with Nginx/Apache. Note, you only the HTTP setup part the the documents. (HTTPS is not needed)
|
||||
|
||||
* [Nginx](../../ce/https_with_nginx.md)
|
||||
* [Apache](../../ce/https_with_apache.md)
|
||||
* [Nginx](./https_with_nginx.md)
|
||||
* [Apache](./https_with_apache.md)
|
||||
|
||||
|
||||
### Run and Test the Single Node
|
||||
|
|
@ -250,11 +250,11 @@ export CLUSTER_MODE=backend
|
|||
|
||||
## Start Seafile Service on boot
|
||||
|
||||
It would be convenient to setup Seafile service to start on system boot. Follow [this documentation](../../other_deployment_notes/start_seafile_at_system_bootup.md) to set it up on **all nodes**.
|
||||
It would be convenient to setup Seafile service to start on system boot. Follow [this documentation](./start_seafile_at_system_bootup.md) to set it up on **all nodes**.
|
||||
|
||||
## Firewall Settings
|
||||
|
||||
Beside [standard ports of a seafile server](../deploy/using_firewall.md), there are 2 firewall rule changes for Seafile cluster:
|
||||
<!--Beside [standard ports of a seafile server](../deploy/using_firewall.md), t--> There are 2 firewall rule changes for Seafile cluster:
|
||||
|
||||
* On each Seafile server machine, you should open the health check port (default 11001);
|
||||
* On the memcached server, you should open the port 11211. For security resons only the Seafile servers should be allowed to access this port.
|
||||
|
|
@ -271,7 +271,7 @@ First you should setup HTTP(S) listeners. Ports 443 and 80 of ELB should be forw
|
|||
|
||||
Then you setup health check
|
||||
|
||||
|
||||
|
||||
|
||||
Refer to [AWS documentation](http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-sticky-sessions.html) about how to setup sticky sessions.
|
||||
|
||||
|
|
@ -15,7 +15,7 @@ Let's assume you have three nodes in your cluster: A, B, and C.
|
|||
* Node A is backend node that run background tasks.
|
||||
* Node B and C are frontend nodes that serving requests from clients.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## 7.1, 8.0
|
||||
|
|
@ -60,7 +60,7 @@ port = 6000
|
|||
|
||||
host is the IP address of background node, make sure the front end nodes can access the background node via IP:6000 .
|
||||
|
||||
Edit **seafile.conf** to enable virus scan according to [virus scan document](../../../extension/virus_scan/virus_scan.md)
|
||||
Edit **seafile.conf** to enable virus scan according to [virus scan document](../extension/virus_scan.md)
|
||||
|
||||
#### Edit the firewall rules
|
||||
|
||||
|
|
@ -189,7 +189,7 @@ interval = 10m
|
|||
highlight = fvh # this is for improving the search speed
|
||||
```
|
||||
|
||||
Edit **seafile.conf** to enable virus scan according to [virus scan document](../../../extension/virus_scan/virus_scan.md)
|
||||
Edit **seafile.conf** to enable virus scan according to [virus scan document](../extension/virus_scan.md)
|
||||
|
||||
|
||||
### Configure Other Nodes
|
||||
|
|
@ -1,12 +1,12 @@
|
|||
# Enabling HTTPS with Apache
|
||||
|
||||
After completing the installation of [Seafile Server Community Edition](installation.md) and [Seafile Server Professional Edition](../pro/installation.md), communication between the Seafile server and clients runs over (unencrypted) HTTP. While HTTP is ok for testing purposes, switching to HTTPS is imperative for production use.
|
||||
After completing the installation of [Seafile Server Community Edition](./installation_ce.md) and [Seafile Server Professional Edition](./installation_pro.md), communication between the Seafile server and clients runs over (unencrypted) HTTP. While HTTP is ok for testing purposes, switching to HTTPS is imperative for production use.
|
||||
|
||||
HTTPS requires a SSL certificate from a Certificate Authority (CA). Unless you already have a SSL certificate, we recommend that you get your SSL certificate from [Let’s Encrypt](https://letsencrypt.org/) using Certbot. If you have a SSL certificate from another CA, skip the section "Getting a Let's Encrypt certificate".
|
||||
|
||||
A second requirement is a reverse proxy supporting SSL. [Apache](https://httpd.apache.org/), a popular web server and reverse proxy, is a good option. The full documentation of Apache is available at https://httpd.apache.org/docs/.
|
||||
|
||||
The recommended reverse proxy is Nginx. You find instructions for [enabling HTTPS with Nginx here](../deploy/deploy_with_nginx).
|
||||
The recommended reverse proxy is Nginx. You find instructions for [enabling HTTPS with Nginx here](./https_with_nginx.md).
|
||||
|
||||
## Setup
|
||||
|
||||
|
|
@ -76,11 +76,11 @@ Getting a Let's Encrypt certificate is straightforward thanks to [Certbot](https
|
|||
|
||||
First, go to the [Certbot](https://certbot.eff.org/) website and choose your web server and OS.
|
||||
|
||||
|
||||
|
||||
|
||||
Second, follow the detailed instructions then shown.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
@ -146,14 +146,14 @@ sudo service apache2 restart
|
|||
|
||||
### Modifying seahub_settings.py
|
||||
|
||||
The `SERVICE_URL` in [seahub_settings.py](../../config/seafile_config/seahub_settings_py.md) informs Seafile about the chosen domain, protocol and port. Change the `SERVICE_URL`so as to account for the switch from HTTP to HTTPS and to correspond to your host name (the `http://`must not be removed):
|
||||
The `SERVICE_URL` in [seahub_settings.py](../config/seahub_settings_py.md) informs Seafile about the chosen domain, protocol and port. Change the `SERVICE_URL`so as to account for the switch from HTTP to HTTPS and to correspond to your host name (the `http://`must not be removed):
|
||||
|
||||
|
||||
```python
|
||||
SERVICE_URL = 'https://seafile.example.com'
|
||||
```
|
||||
|
||||
The `FILE_SERVER_ROOT` in [seahub_settings.py](../../config/seafile_config/seahub_settings_py.md) informs Seafile about the location of and the protocol used by the file server. Change the `FILE_SERVER_ROOT`so as to account for the switch from HTTP to HTTPS and to correspond to your host name (the trailing `/seafhttp` must not be removed):
|
||||
The `FILE_SERVER_ROOT` in [seahub_settings.py](../config/seahub_settings_py.md) informs Seafile about the location of and the protocol used by the file server. Change the `FILE_SERVER_ROOT`so as to account for the switch from HTTP to HTTPS and to correspond to your host name (the trailing `/seafhttp` must not be removed):
|
||||
|
||||
```python
|
||||
FILE_SERVER_ROOT = 'https://seafile.example.com/seafhttp'
|
||||
|
|
@ -1,12 +1,12 @@
|
|||
# Enabling HTTPS with Nginx
|
||||
|
||||
After completing the installation of [Seafile Server Community Edition](installation.md) and [Seafile Server Professional Edition](../pro/installation.md), communication between the Seafile server and clients runs over (unencrypted) HTTP. While HTTP is ok for testing purposes, switching to HTTPS is imperative for production use.
|
||||
After completing the installation of [Seafile Server Community Edition](./installation_ce.md) and [Seafile Server Professional Edition](./installation_pro.md), communication between the Seafile server and clients runs over (unencrypted) HTTP. While HTTP is ok for testing purposes, switching to HTTPS is imperative for production use.
|
||||
|
||||
HTTPS requires a SSL certificate from a Certificate Authority (CA). Unless you already have a SSL certificate, we recommend that you get your SSL certificate from [Let’s Encrypt](https://letsencrypt.org/) using Certbot. If you have a SSL certificate from another CA, skip the section "Getting a Let's Encrypt certificate".
|
||||
|
||||
A second requirement is a reverse proxy supporting SSL. [Nginx](http://nginx.org/), a popular and resource-friendly web server and reverse proxy, is a good option. Nginx's documentation is available at http://nginx.org/en/docs/.
|
||||
|
||||
If you prefer Apache, you find instructions for [enabling HTTPS with Apache here](../https_with_apache/).
|
||||
If you prefer Apache, you find instructions for [enabling HTTPS with Apache here](./https_with_apache.md).
|
||||
|
||||
## Setup
|
||||
|
||||
|
|
@ -141,7 +141,7 @@ Optional customizable options in the seafile.conf are:
|
|||
* Proxy pass for location `/seafhttp` - if seaf-server is configured to start on a different port than 8082
|
||||
* Maximum allowed size of the client request body (`client_max_body_size`)
|
||||
|
||||
The default value for `client_max_body_size` is 1M. Uploading larger files will result in an error message HTTP error code 413 ("Request Entity Too Large"). It is recommended to syncronize the value of client_max_body_size with the parameter `max_upload_size` in section `[fileserver]` of [seafile.conf](../../config/seafile_config/seafile-conf.md). Optionally, the value can also be set to 0 to disable this feature. Client uploads are only partly effected by this limit. With a limit of 100 MiB they can safely upload files of any size.
|
||||
The default value for `client_max_body_size` is 1M. Uploading larger files will result in an error message HTTP error code 413 ("Request Entity Too Large"). It is recommended to syncronize the value of client_max_body_size with the parameter `max_upload_size` in section `[fileserver]` of [seafile.conf](../config/seafile-conf.md). Optionally, the value can also be set to 0 to disable this feature. Client uploads are only partly effected by this limit. With a limit of 100 MiB they can safely upload files of any size.
|
||||
|
||||
Finally, make sure your seafile.conf does not contain syntax errors and restart Nginx for the configuration changes to take effect:
|
||||
|
||||
|
|
@ -157,11 +157,11 @@ $ nginx -s reload
|
|||
Getting a Let's Encrypt certificate is straightforward thanks to [Certbot](https://certbot.eff.org/). Certbot is a free, open source software tool for requesting, receiving, and renewing Let's Encrypt certificates.
|
||||
|
||||
First, go to the [Certbot](https://certbot.eff.org/) website and choose your webserver and OS.
|
||||
|
||||
|
||||
|
||||
Second, follow the detailed instructions then shown.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
@ -245,14 +245,14 @@ If you have WebDAV enabled it is recommended to add the same:
|
|||
|
||||
### Modifying seahub_settings.py
|
||||
|
||||
The `SERVICE_URL` in [seahub_settings.py](../../config/seafile_config/seahub_settings_py.md) informs Seafile about the chosen domain, protocol and port. Change the `SERVICE_URL`so as to account for the switch from HTTP to HTTPS and to correspond to your host name (the `http://` must not be removed):
|
||||
The `SERVICE_URL` in [seahub_settings.py](../config/seahub_settings_py.md) informs Seafile about the chosen domain, protocol and port. Change the `SERVICE_URL`so as to account for the switch from HTTP to HTTPS and to correspond to your host name (the `http://` must not be removed):
|
||||
|
||||
|
||||
```python
|
||||
SERVICE_URL = 'https://seafile.example.com'
|
||||
```
|
||||
|
||||
The `FILE_SERVER_ROOT` in [seahub_settings.py](../../config/seafile_config/seahub_settings_py.md) informs Seafile about the location of and the protocol used by the file server. Change the `FILE_SERVER_ROOT` so as to account for the switch from HTTP to HTTPS and to correspond to your host name (the trailing `/seafhttp` must not be removed):
|
||||
The `FILE_SERVER_ROOT` in [seahub_settings.py](../config/seahub_settings_py.md) informs Seafile about the location of and the protocol used by the file server. Change the `FILE_SERVER_ROOT` so as to account for the switch from HTTP to HTTPS and to correspond to your host name (the trailing `/seafhttp` must not be removed):
|
||||
|
||||
```python
|
||||
FILE_SERVER_ROOT = 'https://seafile.example.com/seafhttp'
|
||||
|
|
@ -266,7 +266,7 @@ Configure your Seafile Server by specifying the following three parameters:
|
|||
|
||||
In the next step, choose whether to create new databases for Seafile or to use existing databases. The creation of new databases requires the root password for the SQL server.
|
||||
|
||||
|
||||
|
||||
|
||||
When choosing "\[1] Create new ccnet/seafile/seahub databases", the script creates these databases and a MySQL user that Seafile Server will use to access them. To this effect, you need to answer these questions:
|
||||
|
||||
|
|
@ -295,7 +295,7 @@ When choosing "\[2] Use existing ccnet/seafile/seahub databases", this are the p
|
|||
|
||||
If the setup is successful, you see the following output:
|
||||
|
||||
|
||||
|
||||
|
||||
The directory layout then looks as follows:
|
||||
|
||||
|
|
@ -111,7 +111,7 @@ sudo pip3 install --timeout=3600 django==4.2.* future==0.18.* mysqlclient==2.1.*
|
|||
psd-tools django-pylibmc django_simple_captcha==0.6.* pycryptodome==3.16.* cffi==1.15.1 python-ldap==3.4.3 lxml
|
||||
```
|
||||
|
||||
**Note**: The recommended deployment option for Seafile PE on CentOS/Redhat is [Docker](../../setup/single_node_installation/setup_pro_edition.md).
|
||||
**Note**: The recommended deployment option for Seafile PE on CentOS/Redhat is [Docker](../setup/setup_pro_by_docker.md).
|
||||
|
||||
|
||||
**For Seafile 11.0.x on Debian 12 and Ubuntu 24.04 with virtual env**
|
||||
|
|
@ -312,7 +312,7 @@ $ tree -L 2 /opt/seafile
|
|||
|
||||
### Run the setup script
|
||||
|
||||
The setup process of Seafile PE is the same as the Seafile CE. See [Installation of Seafile Server Community Edition with MySQL/MariaDB](../ce/installation.md).
|
||||
The setup process of Seafile PE is the same as the Seafile CE. See [Installation of Seafile Server Community Edition with MySQL/MariaDB](./installation_ce.md).
|
||||
|
||||
After the successful completition of the setup script, the directory layout of Seafile PE looks as follows (some folders only get created after the first start, e.g. `logs`):
|
||||
|
||||
|
|
@ -415,8 +415,8 @@ Then refer to [Django's documentation about using Redis cache](https://docs.djan
|
|||
|
||||
You need at least setup HTTP to make Seafile's web interface work. This manual provides instructions for enabling HTTP/HTTPS for the two most popular web servers and reverse proxies:
|
||||
|
||||
* [Nginx](../ce/https_with_nginx.md)
|
||||
* [Apache](../ce/https_with_apache.md)
|
||||
* [Nginx](./https_with_nginx.md)
|
||||
* [Apache](./https_with_apache.md)
|
||||
|
||||
## Starting Seafile Server
|
||||
|
||||
|
|
@ -48,7 +48,7 @@ mysql> use seahub_db;
|
|||
mysql> source seahub-db.sql;
|
||||
```
|
||||
|
||||
Modify configure files：Append following lines to [ccnet.conf](../../config/seafile_config/ccnet-conf.md):
|
||||
Modify configure files：Append following lines to [ccnet.conf](../config/ccnet-conf.md):
|
||||
|
||||
```
|
||||
[Database]
|
||||
|
|
@ -2,22 +2,22 @@
|
|||
|
||||
We provide two ways to deploy Seafile services. **Docker is the recommended way**. Since version 12.0, binary based deployment for community edition is deprecated and will not be supported in a future release.
|
||||
|
||||
* Using [Docker](../../setup/single_node_installation/setup_community_edition.md)
|
||||
* Using [Docker](../setup/setup_ce_by_docker.md)
|
||||
* Manually installing Seafile and setting up database, memcached and Nginx/Apache. See the following section.
|
||||
|
||||
## Manually deployment options
|
||||
|
||||
* [Deploying Seafile with MySQL](installation.md)
|
||||
* [Deploying Seafile with MySQL](installation_ce.md)
|
||||
* Deploying Seafile with SQLite, note, deploy Seafile with SQLite is not supported since version 11.0
|
||||
* [Enabling Https with Nginx](https_with_nginx.md)
|
||||
* [Enabling Https with Apache](https_with_apache.md)
|
||||
* [Start Seafile at System Bootup](../other_deployment_notes/start_seafile_at_system_bootup.md)
|
||||
* [Logrotate](../other_deployment_notes/using_logrotate.md)
|
||||
* [Start Seafile at System Bootup](start_seafile_at_system_bootup.md)
|
||||
* [Logrotate](using_logrotate.md)
|
||||
|
||||
|
||||
## Trouble shooting
|
||||
|
||||
1. Read [Seafile Server Components Overview](../../introduction/components.md) to understand how Seafile server works. This will save you a lot of time.
|
||||
1. Read [Seafile Server Components Overview](../introduction/components.md) to understand how Seafile server works. This will save you a lot of time.
|
||||
2. Read [FAQ](https://cloud.seatable.io/dtable/external-links/7b976c85f504491cbe8e/)
|
||||
3. Go to our [forum](https://forum.seafile.com/) for help.
|
||||
|
||||
|
|
@ -2,8 +2,8 @@
|
|||
|
||||
There are two ways to deploy Seafile Pro Edition. Since version 8.0, the recommend way to install Seafile Pro Edition is using Docker.
|
||||
|
||||
- Method 1: [Deploy Seafile with Docker](../../setup/single_node_installation/setup_pro_edition.md)
|
||||
- Method 2: [Download and Setup Seafile Professional Server Step by Step](installation.md)
|
||||
- Method 1: Deploy Seafile with [Docker](../setup/setup_pro_by_docker.md)
|
||||
- Method 2: [Download and Setup Seafile Professional Server Step by Step](./installation_pro.md)
|
||||
|
||||
## Migration from community edition
|
||||
|
||||
|
|
@ -11,10 +11,10 @@ There are two ways to deploy Seafile Pro Edition. Since version 8.0, the recomme
|
|||
|
||||
## S3 Storage Backends
|
||||
|
||||
- [Setup Seafile Professional Server With S3](../../setup/advanced_topics/setup_with_amazon_s3.md)
|
||||
- [Setup Seafile Professional Server With OpenStack Swift](../../setup/advanced_topics/setup_with_swift.md)
|
||||
- [Data migration between different backends](../../setup/advanced_topics/migrate.md)
|
||||
- [Using multiple storage backends](../../setup/advanced_topics/multiple_storage_backends.md)
|
||||
- [Setup Seafile Professional Server With S3](../setup/setup_with_amazon_s3.md)
|
||||
- [Setup Seafile Professional Server With OpenStack Swift](../setup/setup_with_swift.md)
|
||||
- [Data migration between different backends](../setup/migrate_backends_data.md)
|
||||
- [Using multiple storage backends](../setup/setup_with_multiple_storage_backends.md)
|
||||
|
||||
## Cluster
|
||||
|
||||
|
|
@ -9,7 +9,7 @@ Please check the **upgrade notes** for any special configuration or changes befo
|
|||
|
||||
## Upgrade from 10.0 to 11.0
|
||||
|
||||
Download the new image, stop the old docker container, modify the Seafile image version in docker-compose.yml to the new version. Taking the [community edition](../setup/single_node_installation/setup_community_edition.md) as an example, you have to modify
|
||||
Download the new image, stop the old docker container, modify the Seafile image version in docker-compose.yml to the new version. Taking the [community edition](../setup/setup_ce_by_docker.md) as an example, you have to modify
|
||||
|
||||
```yml
|
||||
...
|
||||
|
|
@ -129,7 +129,7 @@ The following fields merit particular attention:
|
|||
- `SEAFILE_SERVER_HOSTNAME`: Seafile server hostname or domain
|
||||
- `SEAFILE_SERVER_PROTOCOL`: Seafile server protocol (http or https)
|
||||
|
||||
SSL is now handled by the [caddy server](../setup/single_node_installation/setup_community_edition.md#about-ssl-and-caddy). If you have used SSL before, you will also need modify the seafile.nginx.conf. Change server listen 443 to 80.
|
||||
SSL is now handled by the [caddy server](../setup/setup_ce_by_docker.md#about-ssl-and-caddy). If you have used SSL before, you will also need modify the seafile.nginx.conf. Change server listen 443 to 80.
|
||||
|
||||
Backup the original seafile.nginx.conf file:
|
||||
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ The notification server enables desktop syncing and drive clients to get notific
|
|||
|
||||
The notification server works with Seafile syncing client 9.0+ and drive client 3.0+.
|
||||
|
||||
Please follow the document to [enable notification server](../extension/extra_components/notification-server.md)
|
||||
Please follow the document to [enable notification server](../extension/notification-server.md)
|
||||
|
||||
### Memcached section in the seafile.conf (pro edition only)
|
||||
|
||||
|
|
@ -46,7 +46,7 @@ SAML_ATTRIBUTE_MAPPING = {
|
|||
}
|
||||
```
|
||||
|
||||
Please check the new document on [SAML SSO](../config/authentication/saml2_in_10.0.md)
|
||||
Please check the new document on [SAML SSO](../config/saml2_in_10.0.md)
|
||||
|
||||
### Rate control in role settings (pro edition only)
|
||||
|
||||
|
|
|
|||
|
|
@ -47,7 +47,7 @@ There are several reasons driving this change:
|
|||
* Docker deployments - Our official Docker images do not support SQLite. MySQL is the preferred option.
|
||||
* Migration difficulties - Migrating SQLite databases to MySQL via SQL translation is unreliable.
|
||||
|
||||
To migrate from SQLite database to MySQL database, you can follow the document [Migrate from SQLite to MySQL](../setup_binary/other_deployment_notes/migrate_from_sqlite_to_mysql.md). If you have issues in the migration, just post a thread in our forum. We are glad to help you.
|
||||
To migrate from SQLite database to MySQL database, you can follow the document [Migrate from SQLite to MySQL](../setup_binary/migrate_from_sqlite_to_mysql.md). If you have issues in the migration, just post a thread in our forum. We are glad to help you.
|
||||
|
||||
|
||||
### ElasticSearch change (pro edition only)
|
||||
|
|
|
|||
|
|
@ -92,7 +92,7 @@ From version 1.0, SeaDoc is using seahub_db database to store its operation logs
|
|||
|
||||
### Deploy a new SeaDoc server
|
||||
|
||||
Please see the document [Setup SeaDoc](../extension/extra_components/setup_seadoc.md) to install SeaDoc on a separate machine and integrate with your binary packaged based Seafile server v12.0.
|
||||
Please see the document [Setup SeaDoc](../extension/setup_seadoc.md) to install SeaDoc on a separate machine and integrate with your binary packaged based Seafile server v12.0.
|
||||
|
||||
|
||||
## FAQ
|
||||
|
|
|
|||
140
mkdocs.yml
140
mkdocs.yml
|
|
@ -75,89 +75,89 @@ nav:
|
|||
- Setup:
|
||||
- Overview: setup/overview.md
|
||||
- Single node installation:
|
||||
- Setup community edition: setup/single_node_installation/setup_community_edition.md
|
||||
- Setup pro edition: setup/single_node_installation/setup_pro_edition.md
|
||||
- Setup community edition: setup/setup_ce_by_docker.md
|
||||
- Setup pro edition: setup/setup_pro_by_docker.md
|
||||
- Advanced topics:
|
||||
- Storage Backends:
|
||||
- S3 Backend: setup/advanced_topics/setup_with_amazon_s3.md
|
||||
- Ceph Backend: setup/advanced_topics/setup_with_ceph.md
|
||||
- OpenStack Swift Backend: setup/advanced_topics/setup_with_swift.md
|
||||
- Alibaba OSS: setup/advanced_topics/setup_with_oss.md
|
||||
- Multiple Storage Backends: setup/advanced_topics/multiple_storage_backends.md
|
||||
- Data migration: setup/advanced_topics/migrate.md
|
||||
- Seafile Docker autostart: setup/advanced_topics/seafile_docker_autostart.md
|
||||
- Deploy with an existing MySQL server: setup/advanced_topics/deploy_seafile_with_an_existing_mysql_server.md
|
||||
- Run Seafile as non root user inside docker: setup/advanced_topics/run_seafile_as_non_root_user_inside_docker.md
|
||||
- S3 Backend: setup/setup_with_amazon_s3.md
|
||||
- Ceph Backend: setup/setup_with_ceph.md
|
||||
- OpenStack Swift Backend: setup/setup_with_swift.md
|
||||
- Alibaba OSS: setup/setup_with_oss.md
|
||||
- Multiple Storage Backends: setup/setup_with_multiple_storage_backends.md
|
||||
- Data migration: setup/migrate_backends_data.md
|
||||
- Seafile Docker autostart: setup/seafile_docker_autostart.md
|
||||
- Deploy with an existing MySQL server: setup/setup_with_an_existing_mysql_server.md
|
||||
- Run Seafile as non root user inside docker: setup/run_seafile_as_non_root_user_inside_docker.md
|
||||
- Cluster installation:
|
||||
- Seafile Docker Cluster Deployment: setup/cluster_installation/deploy_seafile_cluster_with_docker.md
|
||||
- Setup with Kubernetes (K8s): setup/cluster_installation/deploy_with_k8s.md
|
||||
- Seafile Docker Cluster Deployment: setup/cluster_deploy_with_docker.md
|
||||
- Setup with Kubernetes (K8s): setup/cluster_deploy_with_k8s.md
|
||||
- Migration:
|
||||
- Migration from Seafile Community: setup/migration/migrate_ce_to_pro_with_docker.md
|
||||
- Migrate from non-docker deployment: setup/migration/non_docker_to_docker.md
|
||||
- Migration from Seafile Community: setup/migrate_ce_to_pro_with_docker.md
|
||||
- Migrate from non-docker deployment: setup/migrate_non_docker_to_docker.md
|
||||
- Setup (binary):
|
||||
- Seafile Community Setup:
|
||||
- Outline: setup_binary/ce/README.md
|
||||
- Installation: setup_binary/ce/installation.md
|
||||
- HTTPS with Nginx: setup_binary/ce/https_with_nginx.md
|
||||
- HTTPS with Apache: setup_binary/ce/https_with_apache.md
|
||||
- Outline: setup_binary/outline_ce.md
|
||||
- Installation: setup_binary/installation_ce.md
|
||||
- HTTPS with Nginx: setup_binary/https_with_nginx.md
|
||||
- HTTPS with Apache: setup_binary/https_with_apache.md
|
||||
- Seafile Professional Setup:
|
||||
- Outline: setup_binary/pro/README.md
|
||||
- Installation: setup_binary/pro/installation.md
|
||||
- Migration from Seafile Community: setup_binary/pro/migrate_from_seafile_community_server.md
|
||||
- Outline: setup_binary/outline_pro.md
|
||||
- Installation: setup_binary/installation_pro.md
|
||||
- Migration from Seafile Community: setup_binary/migrate_from_seafile_community_server.md
|
||||
- Cluster deployment:
|
||||
- Deploy in a cluster: setup_binary/pro/deploy_in_a_cluster.md
|
||||
- Search and background tasks in a cluster: setup_binary/pro/enable_search_and_background_tasks_in_a_cluster.md
|
||||
- Memcache and MariaDB Cluster: setup_binary/pro/memcached_mariadb_cluster.md
|
||||
- Setup Seafile cluster with NFS: setup_binary/pro/setup_seafile_cluster_with_nfs.md
|
||||
- License: setup_binary/pro/seafile_professional_sdition_software_license_agreement.md
|
||||
- Deploy in a cluster: setup_binary/deploy_in_a_cluster.md
|
||||
- Search and background tasks in a cluster: setup_binary/enable_search_and_background_tasks_in_a_cluster.md
|
||||
- Memcache and MariaDB Cluster: setup_binary/memcached_mariadb_cluster.md
|
||||
- Setup Seafile cluster with NFS: setup_binary/setup_seafile_cluster_with_nfs.md
|
||||
- License: setup_binary/seafile_professional_sdition_software_license_agreement.md
|
||||
- Other deployment notes:
|
||||
- Start Seafile at System Bootup: setup_binary/other_deployment_notes/start_seafile_at_system_bootup.md
|
||||
- Logrotate: setup_binary/other_deployment_notes/using_logrotate.md
|
||||
- Config fail2ban: setup_binary/other_deployment_notes/fail2ban.md
|
||||
- Migrate From SQLite to MySQL: setup_binary/other_deployment_notes/migrate_from_sqlite_to_mysql.md
|
||||
- Start Seafile at System Bootup: setup_binary/start_seafile_at_system_bootup.md
|
||||
- Logrotate: setup_binary/using_logrotate.md
|
||||
- Config fail2ban: setup_binary/fail2ban.md
|
||||
- Migrate From SQLite to MySQL: setup_binary/migrate_from_sqlite_to_mysql.md
|
||||
- Extensions:
|
||||
- Extra Seafile components:
|
||||
- SeaDoc Integration: extension/extra_components/setup_seadoc.md
|
||||
- Notification Server: extension/extra_components/notification-server.md
|
||||
- WebDAV extension: extension/extra_components/webdav.md
|
||||
- FUSE extension: extension/extra_components/fuse.md
|
||||
- SeaDoc Integration: extension/setup_seadoc.md
|
||||
- Notification Server: extension/notification-server.md
|
||||
- WebDAV extension: extension/webdav.md
|
||||
- FUSE extension: extension/fuse.md
|
||||
- Online Office:
|
||||
- LibreOffice Online Integration: extension/online_office/libreoffice_online.md
|
||||
- OnlyOffice Integration: extension/online_office/only_office.md
|
||||
- Office Online Server Integration (Pro): extension/online_office/office_web_app.md
|
||||
- LibreOffice Online Integration: extension/libreoffice_online.md
|
||||
- OnlyOffice Integration: extension/only_office.md
|
||||
- Office Online Server Integration (Pro): extension/office_web_app.md
|
||||
- Virus Scan (Pro):
|
||||
- Outline: extension/virus_scan/virus_scan.md
|
||||
- Virus scan with ClamAV: extension/virus_scan/deploy_clamav_with_seafile.md
|
||||
- Virus scan with Kav4fs: extension/virus_scan/virus_scan_with_kav4fs.md
|
||||
- Outline: extension/virus_scan.md
|
||||
- Virus scan with ClamAV: extension/deploy_clamav_with_seafile.md
|
||||
- Virus scan with Kav4fs: extension/virus_scan_with_kav4fs.md
|
||||
- Configuration:
|
||||
- Authentication & Users:
|
||||
- LDAP/AD Integration:
|
||||
- LDAP Integration: config/authentication/ldap_in_11.0_ce.md
|
||||
- LDAP Integration (Pro): config/authentication/ldap_in_11.0_pro.md
|
||||
- LDAP Integration: config/ldap_in_11.0_ce.md
|
||||
- LDAP Integration (Pro): config/ldap_in_11.0_pro.md
|
||||
- Single Sign On:
|
||||
- Outline: config/authentication/single_sign_on.md
|
||||
- OAuth Authentication: config/authentication/oauth.md
|
||||
- Remote User Authentication: config/authentication/remote_user.md
|
||||
- Shibboleth Authentication: config/authentication/shibboleth_authentication.md
|
||||
- Auto Login to SeaDrive on Windows: config/authentication/auto_login_seadrive.md
|
||||
- SAML 2.0 (Pro): config/authentication/saml2_in_10.0.md
|
||||
- Switch authentication: config/authentication/auth_switch.md
|
||||
- Outline: config/single_sign_on.md
|
||||
- OAuth Authentication: config/oauth.md
|
||||
- Remote User Authentication: config/remote_user.md
|
||||
- Shibboleth Authentication: config/shibboleth_authentication.md
|
||||
- Auto Login to SeaDrive on Windows: config/auto_login_seadrive.md
|
||||
- SAML 2.0 (Pro): config/saml2_in_10.0.md
|
||||
- Switch authentication: config/auth_switch.md
|
||||
- Advanced User Management (Pro):
|
||||
- Multi-Institutions Support: config/authentication/multi_institutions.md
|
||||
- Roles and Permissions: config/authentication/roles_permissions.md
|
||||
- Administrator Roles and Permissions: config/authentication/admin_roles_permissions.md
|
||||
- Multi-Tenancy Support: config/authentication/multi_tenancy.md
|
||||
- Advanced File Search configuration (Pro): config/authentication/details_about_file_search.md
|
||||
- Open Cloud Mesh: config/authentication/ocm.md
|
||||
- Multi-Institutions Support: config/multi_institutions.md
|
||||
- Roles and Permissions: config/roles_permissions.md
|
||||
- Administrator Roles and Permissions: config/admin_roles_permissions.md
|
||||
- Multi-Tenancy Support: config/multi_tenancy.md
|
||||
- Advanced File Search configuration (Pro): config/details_about_file_search.md
|
||||
- Open Cloud Mesh: config/ocm.md
|
||||
- Available configuration options:
|
||||
- Outline: config/seafile_config/README.md
|
||||
- Environment variables: config/seafile_config/env.md
|
||||
- ccnet.conf: config/seafile_config/ccnet-conf.md
|
||||
- seafile.conf: config/seafile_config/seafile-conf.md
|
||||
- seahub_settings.py: config/seafile_config/seahub_settings_py.md
|
||||
- seafevents.conf: config/seafile_config/seafevents-conf.md
|
||||
- Seahub customization: config/seafile_config/seahub_customization.md
|
||||
- Email Sending: config/seafile_config/sending_email.md
|
||||
- Outline: config/README.md
|
||||
- Environment variables: config/env.md
|
||||
- ccnet.conf: config/ccnet-conf.md
|
||||
- seafile.conf: config/seafile-conf.md
|
||||
- seahub_settings.py: config/seahub_settings_py.md
|
||||
- seafevents.conf: config/seafevents-conf.md
|
||||
- Seahub customization: config/seahub_customization.md
|
||||
- Email Sending: config/sending_email.md
|
||||
- Administration:
|
||||
- Outline: administration/README.md
|
||||
- Account management: administration/account.md
|
||||
|
|
@ -185,12 +185,12 @@ nav:
|
|||
- Developing:
|
||||
- Outline: develop/README.md
|
||||
- How to Build Seafile:
|
||||
- Outline: develop/build_seafile/README.md
|
||||
- Linux: develop/build_seafile/linux.md
|
||||
- macOS: develop/build_seafile/osx.md
|
||||
- Windows: develop/build_seafile/windows.md
|
||||
- Server development: develop/build_seafile/server.md
|
||||
- Server binary package: develop/build_seafile/rpi.md
|
||||
- Outline: develop/build_seafile.md
|
||||
- Linux: develop/linux.md
|
||||
- macOS: develop/osx.md
|
||||
- Windows: develop/windows.md
|
||||
- Server development: develop/server.md
|
||||
- Server binary package: develop/rpi.md
|
||||
- Translation: develop/translation.md
|
||||
- Web API V2.1: develop/web_api_v2.1.md
|
||||
- PHP API: https://github.com/rene-s/Seafile-PHP-SDK
|
||||
|
|
|
|||
Loading…
Reference in New Issue