mirror of
https://github.com/haiwen/seafile-admin-docs.git
synced 2025-12-26 02:32:50 +00:00
opt: dirs & structures
This commit is contained in:
Junxiang Huang
parent
fe891e91e4
commit
76de6ed573
|
|
@ -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/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/seafile_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/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/seafile_config/sending_email.md).
|
||||
|
|
@ -53,7 +53,7 @@ LDAP improvements and fixes
|
|||
|
||||
* Only import LDAP users to Seafile internal database upon login
|
||||
* Only list imported LDAP users in "organization->members"
|
||||
* Add option to not import users via LDAP Sync (Only update information for already imported users). The option name is IMPORT_NEW_USER. See document <http://manual.seafile.com/deploy/ldap_user_sync.html>
|
||||
* Add option to not import users via LDAP Sync (Only update information for already imported users). The option name is IMPORT_NEW_USER. See document <http://manual.seafile.com/deploy/ldap_user_sync.html> (url might deprecated)
|
||||
|
||||
### 4.4.3 (2015.10.20)
|
||||
|
||||
|
|
@ -292,7 +292,7 @@ Platform
|
|||
Pro only updates
|
||||
|
||||
* Support syncing any sub-folder in the desktop client
|
||||
* Add audit log, see <http://manual.seafile.com/security/auditing.html>. This feature is turned off by default. To turn it on, see <http://manual.seafile.com/deploy_pro/configurable_options.html>
|
||||
* Add audit log, see <http://manual.seafile.com/security/auditing.html> (url might deprecated). This feature is turned off by default. To turn it on, see <http://manual.seafile.com/deploy_pro/configurable_options.html> (url might deprecated)
|
||||
* Syncing LDAP groups
|
||||
* Add permission setting for a sub-folder (beta)
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@
|
|||
|
||||
**Upgrade**
|
||||
|
||||
Please check our document for how to upgrade to 11.0: <https://manual.seafile.com/upgrade/upgrade_notes_for_11.0.x/>
|
||||
Please check our document for how to upgrade to [11.0](../upgrade/upgrade_notes_for_11.0.x.md)
|
||||
|
||||
### 11.0.15 (2024-10-17)
|
||||
|
||||
|
|
@ -163,7 +163,7 @@ Other changes
|
|||
|
||||
**Upgrade**
|
||||
|
||||
Please check our document for how to upgrade to 10.0: <https://manual.seafile.com/upgrade/upgrade_notes_for_10.0.x/>
|
||||
Please check our document for how to upgrade to [10.0](../upgrade/upgrade_notes_for_10.0.x.md).
|
||||
|
||||
### 10.0.16 (2024-06-21)
|
||||
|
||||
|
|
@ -276,7 +276,7 @@ Note, after upgrading to this version, you need to upgrade the Python libraries
|
|||
|
||||
**Upgrade**
|
||||
|
||||
Please check our document for how to upgrade to 9.0: <https://manual.seafile.com/upgrade/upgrade_notes_for_9.0.x/>
|
||||
Please check our document for how to upgrade to [9.0](../upgrade/upgrade_notes_for_9.0.x.md).
|
||||
|
||||
### 9.0.16 (2023-03-22)
|
||||
|
||||
|
|
@ -448,7 +448,7 @@ Deprecated
|
|||
|
||||
**Upgrade**
|
||||
|
||||
Please check our document for how to upgrade to 8.0: <https://manual.seafile.com/upgrade/upgrade_notes_for_8.0.x/>
|
||||
Please check our document for how to upgrade to [8.0](../upgrade/upgrade_notes_for_8.0.x.md).
|
||||
|
||||
### 8.0.17 (2022/01/10)
|
||||
|
||||
|
|
@ -591,7 +591,7 @@ fs_id_list_request_timeout = 300
|
|||
|
||||
**Upgrade**
|
||||
|
||||
Please check our document for how to upgrade to 7.1: [upgrade notes for 7.1.x](../upgrade/upgrade_notes_for_7.1.x.md)
|
||||
Please check our document for how to upgrade to [7.1](../upgrade/upgrade_notes_for_7.1.x.md).
|
||||
|
||||
### 7.1.22 (2021/07/29)
|
||||
|
||||
|
|
@ -781,7 +781,7 @@ fs_id_list_request_timeout = 300
|
|||
|
||||
Since seafile-pro 7.0.0, we have upgraded Elasticsearch to 5.6. As Elasticsearch 5.6 relies on the Java 8 environment and can't run with root, you need to run Seafile with a non-root user and upgrade the Java version.
|
||||
|
||||
Please check our document for how to upgrade to 7.0: [upgrade notes for 7.0.x](../upgrade/upgrade_notes_for_7.0.x.md)
|
||||
Please check our document for how to upgrade to [7.0](../upgrade/upgrade_notes_for_7.0.x.md).
|
||||
|
||||
### 7.0.19 (2020/09/07)
|
||||
|
||||
|
|
@ -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](../deploy_pro/roles_permissions.md#more-about-guest-invitation-feature))
|
||||
* Guest invitation: Add an regex to prevent certain email addresses be invited (see [roles permissions](../config/authentication/advanced_user_management/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
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
|
||||
**Note when upgrade to 5.0 from 4.4**
|
||||
|
||||
You can follow the document on major upgrade (<http://manual.seafile.com/deploy/upgrade.html>)
|
||||
You can follow the document on major upgrade (<http://manual.seafile.com/deploy/upgrade.html>) (url might deprecated)
|
||||
|
||||
In Seafile 5.0, we have moved all config files to folder `conf`, including:
|
||||
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@
|
|||
|
||||
**Upgrade**
|
||||
|
||||
Please check our document for how to upgrade to 11.0: <https://manual.seafile.com/upgrade/upgrade_notes_for_11.0.x/>
|
||||
Please check our document for how to upgrade to [11.0](../upgrade/upgrade_notes_for_11.0.x.md)
|
||||
|
||||
|
||||
### 11.0.12 (2024-08-14)
|
||||
|
|
@ -180,7 +180,7 @@ SDoc editor 0.2
|
|||
|
||||
**Upgrade**
|
||||
|
||||
Please check our document for how to upgrade to 10.0: <https://manual.seafile.com/upgrade/upgrade_notes_for_10.0.x/>
|
||||
Please check our document for how to upgrade to [10.0](../upgrade/upgrade_notes_for_10.0.x.md).
|
||||
|
||||
### 10.0.1 (2023-04-11)
|
||||
|
||||
|
|
@ -326,7 +326,7 @@ use_go_fileserver = true
|
|||
|
||||
## 8.0
|
||||
|
||||
Please check our document for how to upgrade to 8.0: <https://manual.seafile.com/upgrade/upgrade_notes_for_8.0.x/>
|
||||
Please check our document for how to upgrade to [8.0](../upgrade/upgrade_notes_for_8.0.x.md).
|
||||
|
||||
### 8.0.8 (2021/12/06)
|
||||
|
||||
|
|
@ -409,7 +409,7 @@ Progresql support is dropped as we have rewritten the database access code to re
|
|||
|
||||
**Upgrade**
|
||||
|
||||
Please check our document for how to upgrade to 7.1: <https://manual.seafile.com/upgrade/upgrade_notes_for_7.1.x/>
|
||||
Please check our document for how to upgrade to [7.1](../upgrade/upgrade_notes_for_7.1.x.md).
|
||||
|
||||
### 7.1.5 (2020/09/22)
|
||||
|
||||
|
|
|
|||
|
|
@ -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](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/advanced_topics/storage_backends/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**:
|
||||
|
||||
|
|
@ -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
|
||||
|
||||
|
|
@ -1,6 +1,6 @@
|
|||
# Configure Seafile to use LDAP
|
||||
|
||||
Note: This documentation is for the Community Edition. If you're using Pro Edition, please refer to [the Seafile Pro documentation](../deploy_pro/ldap_in_11.0.md).
|
||||
Note: This documentation is for the Community Edition. If you're using Pro Edition, please refer to [the Seafile Pro documentation](../pro/ldap_in_11.0.md).
|
||||
|
||||
## How does LDAP User Management work in Seafile
|
||||
|
||||
|
|
@ -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.
|
||||
|
||||
|
||||
|
|
@ -2,11 +2,11 @@
|
|||
|
||||
Seafile Server supports the following external authentication types:
|
||||
|
||||
* [LDAP (Auth and Sync)](./ldap_in_11.0.md)
|
||||
* [LDAP (Auth and Sync)](../ldap/ce/ldap_in_11.0.md)
|
||||
* [OAuth](./oauth.md)
|
||||
* [Shibboleth](./shibboleth_config_v6.3.md)
|
||||
* [SAML](../deploy_pro/saml2_in_10.0.md)
|
||||
* [CAS](../deploy_pro/cas.md)
|
||||
* [Shibboleth](./shibboleth_authentication.md)
|
||||
* [SAML](./saml2_in_10.0.md)
|
||||
<!--* [CAS](../deploy_pro/cas.md)-->
|
||||
|
||||
Since 11.0 version, switching between the types is possible, but any switch requires modifications of Seafile's databases.
|
||||
|
||||
|
|
@ -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](../maintain/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.
|
||||
|
||||
|
|
@ -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**.
|
||||
|
||||
|
|
@ -211,7 +211,7 @@ We also added an option `SHIB_ACTIVATE_AFTER_CREATION` (defaults to `True`) whic
|
|||
|
||||
Shibboleth has a field called affiliation. It is a list like: `employee@uni-mainz.de;member@uni-mainz.de;faculty@uni-mainz.de;staff@uni-mainz.de.`
|
||||
|
||||
We are able to set user role from Shibboleth. Details about user role, please refer to <https://download.seafile.com/published/seafile-manual/deploy_pro/roles_permissions.md>
|
||||
We are able to set user role from Shibboleth. Details about user role, please refer to [*Roles and Permissions*](../advanced_user_management/roles_permissions.md)
|
||||
|
||||
|
||||
To enable this, modify `SHIBBOLETH_ATTRIBUTE_MAP` above and add `Shibboleth-affiliation` field, you may need to change `Shibboleth-affiliation` according to your Shibboleth SP attributes.
|
||||
|
|
@ -4,7 +4,7 @@ Seafile supports most of the popular single-sign-on authentication protocols. So
|
|||
|
||||
In the Community Edition:
|
||||
|
||||
* [Shibboleth](./shibboleth_config_v6.3.md)
|
||||
* [Shibboleth](./shibboleth_authentication.md)
|
||||
* [OAuth](./oauth.md)
|
||||
* [Remote User (Proxy Server)](./remote_user.md)
|
||||
* [Auto Login to SeaDrive on Windows](./auto_login_seadrive.md)
|
||||
|
|
@ -13,5 +13,5 @@ Kerberos authentication can be integrated by using Apache as a proxy server and
|
|||
|
||||
In Pro Edition:
|
||||
|
||||
* [ADFS or SAML 2.0](../deploy_pro/adfs.md)
|
||||
* [CAS](../deploy_pro/cas.md)
|
||||
* [ADFS or SAML 2.0](./config_seafile_with_ADFS.md)
|
||||
<!--* [CAS](../deploy_pro/cas.md)-->
|
||||
|
|
@ -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
|
||||
|
||||
|
|
@ -45,7 +45,7 @@ SEADOC_SERVER_URL=http://example.seafile.com/sdoc-server
|
|||
|
||||
### Components configurations
|
||||
|
||||
- `COMPOSE_FILE`: `.yml` files for components of [Seafile-docker](../docker/seafile_docker_overview.md), each `.yml` must be separated by the symbol defined in `COMPOSE_PATH_SEPARATOR`. The core components are involved in `seafile-server.yml` and `caddy.yml` which must be taken in this term.
|
||||
- `COMPOSE_FILE`: `.yml` files for components of [Seafile-docker](../setup/overview.md), each `.yml` must be separated by the symbol defined in `COMPOSE_PATH_SEPARATOR`. The core components are involved in `seafile-server.yml` and `caddy.yml` which must be taken in this term.
|
||||
- `COMPOSE_PATH_SEPARATOR`: The symbol used to separate the `.yml` files in term `COMPOSE_FILE`, default is ','.
|
||||
|
||||
### Docker images configurations
|
||||
|
|
@ -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](../extra_setup/setup_seadoc.md). SeaDoc server image, default is `seafileltd/sdoc-server:1.0-latest`.
|
||||
- `SEADOC_IMAGE`: Only valid after integrating [SeaDoc](../../extension/extra_components/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](../extra_setup/setup_seadoc.md). The volume directory of [SeaDoc server data](../extra_setup/setup_seadoc.md#seadoc-directory-structure), default is `/opt/seadoc-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`.
|
||||
|
||||
## MySQL configurations
|
||||
|
||||
|
|
@ -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](../deploy_pro/details_about_file_search.md#access-the-aws-elasticsearch-service-using-https)
|
||||
**NOTE**: [Access the AWS elasticsearch service using HTTPS](../authentication/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](../deploy_pro/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/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](../deploy_pro/setup_with_amazon_s3.md)
|
||||
- [Ceph RADOS](../deploy_pro/setup_with_ceph.md)
|
||||
- [Alibaba Cloud OSS](../deploy_pro/setup_with_oss.md)
|
||||
- [OpenStack Swift](../deploy_pro/setup_with_swift.md)
|
||||
- [S3 or S3-compatible object storage](../../setup/advanced_topics/storage_backends/setup_with_amazon_s3.md)
|
||||
- [Ceph RADOS](../../setup/advanced_topics/storage_backends/setup_with_ceph.md)
|
||||
- [Alibaba Cloud OSS](../../setup/advanced_topics/storage_backends/setup_with_oss.md)
|
||||
- [OpenStack Swift](../../setup/advanced_topics/storage_backends/setup_with_swift.md)
|
||||
|
||||
You may also configure Seafile to use [multiple storage backends](../deploy_pro/multiple_storage_backends.md) at the same time.
|
||||
You may also configure Seafile to use [multiple storage backends](../../setup/advanced_topics/storage_backends/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](../deploy/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/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.
|
||||
|
||||
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:
|
||||
|
||||
|
||||
|
||||
|
|
@ -445,7 +445,7 @@ REST_FRAMEWORK = {
|
|||
|
||||
# Throtting whitelist used to disable throttle for certain IPs.
|
||||
# e.g. REST_FRAMEWORK_THROTTING_WHITELIST = ['127.0.0.1', '192.168.1.1']
|
||||
# Please make sure `REMOTE_ADDR` header is configured in Nginx conf according to https://manual.seafile.com/deploy/deploy_with_nginx.html.
|
||||
# Please make sure `REMOTE_ADDR` header is configured in Nginx conf according to https://manual.seafile.com/12.0/setup_binary/ce/deploy_with_nginx.html.
|
||||
REST_FRAMEWORK_THROTTING_WHITELIST = []
|
||||
|
||||
```
|
||||
|
|
@ -1,26 +0,0 @@
|
|||
# Deploy Seafile Pro Edition
|
||||
|
||||
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](../docker/pro-edition/deploy_seafile_pro_with_docker.md)
|
||||
- Method 2: [Download and Setup Seafile Professional Server Step by Step](download_and_setup_seafile_professional_server.md)
|
||||
|
||||
## Migration from community edition
|
||||
|
||||
- [Migrate from Seafile Community edition](migrate_from_seafile_community_server.md)
|
||||
|
||||
## S3 Storage Backends
|
||||
|
||||
- [Setup Seafile Professional Server With S3](setup_with_amazon_s3.md)
|
||||
- [Setup Seafile Professional Server With OpenStack Swift](setup_with_swift.md)
|
||||
- [Data migration between different backends](migrate.md)
|
||||
- [Using multiple storage backends](multiple_storage_backends.md)
|
||||
|
||||
## Cluster
|
||||
|
||||
- [Deploy seafile servers in a cluster](deploy_in_a_cluster.md)
|
||||
- [Enable search and background tasks in a cluster](enable_search_and_background_tasks_in_a_cluster.md)
|
||||
- [Setup Seafile cluster with NFS](setup_seafile_cluster_with_nfs.md)
|
||||
|
||||
|
||||
|
||||
|
|
@ -2,8 +2,8 @@
|
|||
|
||||
Build Seafile
|
||||
|
||||
* [How to Build Seafile](../build_seafile/README.md)
|
||||
* [How to Setup Development Environment](env.md)
|
||||
* [How to Build Seafile](./build_seafile/README.md)
|
||||
* [How to Setup Development Environment](../config/seafile_config/env.md)
|
||||
|
||||
Seafile Open API
|
||||
|
||||
|
|
|
|||
|
|
@ -249,19 +249,19 @@ After the script finisheds, we would get a `seafile-server_6.0.1_pi.tar.gz` in `
|
|||
|
||||
### <a id="wiki-test-fresh-install"></a>Test a fresh install
|
||||
|
||||
Use the built seafile server package to go over the steps of [Deploying Seafile with SQLite](http://manual.seafile.com/deploy/using_sqlite/).
|
||||
<!-- Use the built seafile server package to go over the steps of [Deploying Seafile with SQLite](http://manual.seafile.com/deploy/using_sqlite/). -->
|
||||
|
||||
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](http://manual.seafile.com/extension/webdav/) server works correctly
|
||||
* Seafile [WebDAV](../../extension/extra_components/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](http://manual.seafile.com/upgrade/upgrade/)
|
||||
* 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](http://manual.seafile.com/extension/webdav/) server works correctly
|
||||
* Seafile [WebDAV](../../extension/extra_components/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
|
||||
|
||||
|
|
@ -1,111 +0,0 @@
|
|||
# Deploy OnlyOffice with Docker
|
||||
|
||||
## Add OnlyOffice to docker-compose.yml
|
||||
|
||||
The following section needs to be added to docker-compose.yml in the services section
|
||||
|
||||
```yml
|
||||
services:
|
||||
...
|
||||
|
||||
oods:
|
||||
image: onlyoffice/documentserver:latest
|
||||
container_name: seafile-oods
|
||||
networks:
|
||||
- seafile-net
|
||||
environment:
|
||||
- JWT_ENABLED=true
|
||||
- JWT_SECRET=your-secret-string
|
||||
```
|
||||
|
||||
## Initialize OnlyOffice local configuration file
|
||||
|
||||
```shell
|
||||
mkdir -p /opt/seafile-oods/DocumentServer/
|
||||
vim /opt/seafile-oods/DocumentServer/local-production-linux.json
|
||||
```
|
||||
|
||||
```json
|
||||
{
|
||||
"services": {
|
||||
"CoAuthoring": {
|
||||
"autoAssembly": {
|
||||
"enable": true,
|
||||
"interval": "5m"
|
||||
}
|
||||
}
|
||||
},
|
||||
"FileConverter": {
|
||||
"converter": {
|
||||
"downloadAttemptMaxCount": 1
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
## Add OnlyOffice to nginx conf
|
||||
|
||||
Add this to seafile.nginx.conf
|
||||
|
||||
```
|
||||
# Required for only office document server
|
||||
map $http_x_forwarded_proto $the_scheme {
|
||||
default $http_x_forwarded_proto;
|
||||
"" $scheme;
|
||||
}
|
||||
map $http_x_forwarded_host $the_host {
|
||||
default $http_x_forwarded_host;
|
||||
"" $host;
|
||||
}
|
||||
map $http_upgrade $proxy_connection {
|
||||
default upgrade;
|
||||
"" close;
|
||||
}
|
||||
server {
|
||||
listen 80;
|
||||
...
|
||||
}
|
||||
|
||||
server {
|
||||
listen 443 ssl;
|
||||
...
|
||||
|
||||
location /onlyofficeds/ {
|
||||
proxy_pass http://oods/;
|
||||
proxy_http_version 1.1;
|
||||
client_max_body_size 100M;
|
||||
proxy_read_timeout 3600s;
|
||||
proxy_connect_timeout 3600s;
|
||||
proxy_set_header Upgrade $http_upgrade;
|
||||
proxy_set_header Connection $proxy_connection;
|
||||
proxy_set_header X-Forwarded-Host $the_host/onlyofficeds;
|
||||
proxy_set_header X-Forwarded-Proto $the_scheme;
|
||||
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
## Modify seahub_settings.py
|
||||
|
||||
Add this to seahub_settings.py
|
||||
|
||||
```python
|
||||
# OnlyOffice
|
||||
ENABLE_ONLYOFFICE = True
|
||||
VERIFY_ONLYOFFICE_CERTIFICATE = True
|
||||
ONLYOFFICE_APIJS_URL = 'http://<your-seafile-doamin>/onlyofficeds/web-apps/apps/api/documents/api.js'
|
||||
ONLYOFFICE_FILE_EXTENSION = ('doc', 'docx', 'ppt', 'pptx', 'xls', 'xlsx', 'odt', 'fodt', 'odp', 'fodp', 'ods', 'fods')
|
||||
ONLYOFFICE_EDIT_FILE_EXTENSION = ('docx', 'pptx', 'xlsx')
|
||||
ONLYOFFICE_JWT_SECRET = 'your-secret-string'
|
||||
```
|
||||
|
||||
## Restart docker container
|
||||
|
||||
```shell
|
||||
docker compose down
|
||||
docker compose up -d
|
||||
```
|
||||
|
||||
Wait some minutes until OnlyOffice finished initializing.
|
||||
|
||||
Now OnlyOffice can be used.
|
||||
|
|
@ -1,3 +0,0 @@
|
|||
# WebDAV and FUSE extensions
|
||||
|
||||
Seafile WebDAV and FUSE extensions make it easy for Seafile to work with third party applications. For example, you can use Documents App in iOS to access files in Seafile via WebDAV interface.
|
||||
|
|
@ -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](../deploy_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/pro/cluster/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:
|
||||
|
||||
|
|
@ -20,11 +20,11 @@ SeaDoc excels at:
|
|||
|
||||
The SeaDoc archticture is demonstrated as below:
|
||||
|
||||
|
||||
|
||||
|
||||
Here is the workflow when a user open sdoc file in browser
|
||||
|
||||
1. When a user open a sdoc file in the browser, a file loading request will be sent to Caddy, and Caddy proxy the request to SeaDoc server (see [Seafile instance archticture](../docker/seafile_docker_overview.md) for the details).
|
||||
1. When a user open a sdoc file in the browser, a file loading request will be sent to Caddy, and Caddy proxy the request to SeaDoc server (see [Seafile instance archticture](../setup/overview.md) for the details).
|
||||
2. SeaDoc server will send the content back if it is already cached, otherwise it sends a request to Seahub.
|
||||
3. Seahub loads the content from Seafile-server, then sends it to SeaDoc server and write the file to the cache at the same time.
|
||||
4. After SeaDoc receives the content, it sends the content to the browser.
|
||||
|
|
@ -42,9 +42,9 @@ SeaDoc has the following deployment methods:
|
|||
|
||||
### Deploy SeaDoc on a new host
|
||||
|
||||
#### Download and modify SeaDoc docker-compose.yml
|
||||
#### Download and modify seadoc.yml
|
||||
|
||||
Download [docker-compose.yml](https://manual.seafile.com/docker/docker-compose/seadoc/0.8/docker-compose.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
|
||||
|
|
@ -75,10 +75,10 @@ Then follow the section: Start SeaDoc.
|
|||
|
||||
```shell
|
||||
# for community edition
|
||||
wget https://manual.seafile.com/12.0/docker/docker-compose/ce/seadoc.yml
|
||||
wget https://manual.seafile.com/12.0/docker/ce/seadoc.yml
|
||||
|
||||
# for pro edition
|
||||
wget https://manual.seafile.com/12.0/docker/docker-compose/pro/seadoc.yml
|
||||
wget https://manual.seafile.com/12.0/docker/pro/seadoc.yml
|
||||
```
|
||||
|
||||
Modify `.env`, and insert `seadoc.yml` into `COMPOSE_FILE`, and enable SeaDoc server
|
||||
|
|
@ -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](../deploy/https_with_nginx.md) with valid TLS/SSL certificates with Seafile to use Collabora Online.
|
||||
**NOTE:** You must [enable https](../../setup_binary/ce/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
|
||||
|
||||
|
|
@ -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
|
||||
|
||||
|
|
@ -21,7 +21,7 @@ pwgen -s 40 1
|
|||
Download the `onlyoffice.yml`
|
||||
|
||||
```shell
|
||||
wget https://manual.seafile.com/12/docker/docker-compose/onlyoffice.yml
|
||||
wget https://manual.seafile.com/12.0/docker/onlyoffice.yml
|
||||
```
|
||||
|
||||
insert `onlyoffice.yml` into `COMPOSE_FILE` list (i.e., `COMPOSE_FILE='...,onlyoffice.yml'`), and add the following configurations of onlyoffice in `.env` file.
|
||||
|
|
@ -33,7 +33,7 @@ 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)
|
||||
|
||||
|
|
@ -1,11 +0,0 @@
|
|||
# Export File Access Log
|
||||
|
||||
Since version 7.0.8 pro, we offer command to export file access log.
|
||||
|
||||
```
|
||||
cd <install-path>/seafile-server-latest
|
||||
./seahub.sh python-env python seahub/manage.py export_file_access_log --start-date 2019-06-01 --end-date 2019-07-01
|
||||
|
||||
```
|
||||
|
||||
|
||||
|
|
@ -1,11 +0,0 @@
|
|||
# Export User Storage Report
|
||||
|
||||
Since version 7.0.8 pro, we offer command to export user storage report.
|
||||
|
||||
```
|
||||
cd <install-path>/seafile-server-latest
|
||||
./seahub.sh python-env python seahub/manage.py export_user_storage_report
|
||||
|
||||
```
|
||||
|
||||
|
||||
|
|
@ -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](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/authentication/sso/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.
|
||||
|
||||
|
|
@ -115,7 +115,7 @@ $seafile_admin_token = '';
|
|||
?>
|
||||
```
|
||||
|
||||
First, replace SEAFILE_SERVER_URL with the URL of your Seafile Server and SHARED_SECRET with the key used in [Configuring Seahub](../deploy/outlook_addin_config.md/#configuring_seahub).
|
||||
First, replace SEAFILE_SERVER_URL with the URL of your Seafile Server and SHARED_SECRET with the key used in [Configuring Seahub](#configuring_seahub).
|
||||
|
||||
Second, add either the user credentials of a Seafile user with admin rights or the API-token of such a user.
|
||||
|
||||
|
|
@ -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](/manual/config/seafile-conf.md#cache-pro-edition-only) to `seafile.conf`.
|
||||
You also need to add [memory cache configurations](../../../config/seafile_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](/manual/config/seafile-conf.md#cache-pro-edition-only) to `seafile.conf`.
|
||||
You also need to add [memory cache configurations](../../../config/seafile_config/seafile-conf.md#cache-pro-edition-only) to `seafile.conf`.
|
||||
|
||||
## Defining Storage Backends
|
||||
|
||||
|
|
@ -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](download_and_setup_seafile_professional_server.md)
|
||||
- Setup the basic Seafile Professional Server following the guide on [Download and setup Seafile Professional Server](../../../setup_binary/pro/installation.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-conf/#cache-pro-edition-only).
|
||||
You also need to add [memory cache configurations](../../../config/seafile_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-conf/#cache-pro-edition-only).
|
||||
You also need to add [memory cache configurations](../../../config/seafile_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-conf/#cache-pro-edition-only).
|
||||
You also need to add [memory cache configurations](../../../config/seafile_config/seafile-conf.md#cache-pro-edition-only).
|
||||
|
||||
We'll explain the configurations below:
|
||||
|
||||
|
|
@ -1,6 +1,6 @@
|
|||
# Setup With Ceph
|
||||
|
||||
Ceph is a scalable distributed storage system. It's recommended to use Ceph's S3 Gateway (RGW) to integarte with Seafile. Seafile can also use Ceph's RADOS object storage layer for storage backend. But using RADOS requires to link with librados library, which may introduce library incompatibility issues during deployment. Furthermore the S3 Gateway provides easier to manage HTTP based interface. If you want to integrate with S3 gateway, please refer to "Use S3-compatible Object Storage" section in [this documentation](./setup_with_amazon_s3.md). The documentation below is for integrating with RADOS.
|
||||
Ceph is a scalable distributed storage system. It's recommended to use Ceph's S3 Gateway (RGW) to integarte with Seafile. Seafile can also use Ceph's RADOS object storage layer for storage backend. But using RADOS requires to link with librados library, which may introduce library incompatibility issues during deployment. Furthermore the S3 Gateway provides easier to manage HTTP based interface. If you want to integrate with S3 gateway, please refer to "Use S3-compatible Object Storage" section in [this documentation](setup_with_amazon_s3.md). The documentation below is for integrating with RADOS.
|
||||
|
||||
## Copy ceph conf file and client keyring
|
||||
|
||||
|
|
@ -63,7 +63,7 @@ ceph_config = /etc/ceph/ceph.conf
|
|||
pool = seafile-fs
|
||||
```
|
||||
|
||||
You also need to add [memory cache configurations](/config/seafile-conf/#cache-pro-edition-only).
|
||||
You also need to add [memory cache configurations](../../../config/seafile_config/seafile-conf.md#cache-pro-edition-only).
|
||||
|
||||
It's required to create separate pools for commit, fs, and block objects.
|
||||
|
||||
|
|
@ -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](download_and_setup_seafile_professional_server.md)
|
||||
* Setup the basic Seafile Professional Server following the guide on [Download and setup Seafile Professional Server](../../../setup_binary/pro/installation.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-conf/#cache-pro-edition-only).
|
||||
You also need to add [memory cache configurations](../../../config/seafile_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-conf/#cache-pro-edition-only).
|
||||
You also need to add [memory cache configurations](../../../config/seafile_config/seafile-conf.md#cache-pro-edition-only).
|
||||
|
||||
### Use HTTPS connections to OSS
|
||||
|
||||
|
|
@ -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](download_and_setup_seafile_professional_server.md)
|
||||
* Setup the basic Seafile Professional Server following the guide on [Download and setup Seafile Professional Server](../../../setup_binary/pro/installation.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-conf/#cache-pro-edition-only).
|
||||
You also need to add [memory cache configurations](../../../config/seafile_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.
|
||||
|
||||
|
|
@ -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](https://manual.seafile.com/deploy_pro/deploy_in_a_cluster/#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/pro/cluster/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 11 PRO](../docker/docker-compose/pro/11.0/docker-compose.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
|
||||
|
||||
|
|
@ -182,7 +182,7 @@ spec:
|
|||
- name: seafile
|
||||
# image: seafileltd/seafile-mc:9.0.10
|
||||
# image: seafileltd/seafile-mc:11.0-latest
|
||||
image: docker.seadrive.org/seafileltd/seafile-pro-mc:11.0-latest
|
||||
image: docker.seadrive.org/seafileltd/seafile-pro-mc:12.0-latest
|
||||
env:
|
||||
- name: DB_HOST
|
||||
value: "mariadb"
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue