From b4144b878e69b141e6a1471f7932714437e69cbd Mon Sep 17 00:00:00 2001 From: Daniel Pan Date: Fri, 21 Feb 2025 13:32:08 +0800 Subject: [PATCH 1/8] Clarify memecache use in seaf-server --- manual/config/seafile-conf.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/manual/config/seafile-conf.md b/manual/config/seafile-conf.md index eb5049db..6d709cdf 100644 --- a/manual/config/seafile-conf.md +++ b/manual/config/seafile-conf.md @@ -57,7 +57,7 @@ Seafile uses a system trash, where deleted libraries will be moved to. In this w ## Cache (Pro Edition Only) -Seafile Pro Edition uses memory caches in various cases to improve performance. Some session information is also saved into memory cache to be shared among the cluster nodes. Memcached or Reids can be use for memory cache. +seaf-server component in Seafile Pro Edition uses memory caches in various cases to improve performance. (seaf-server component in community edition does not use cache) Some session information is also saved into memory cache to be shared among the cluster nodes. Memcached or Reids can be use for memory cache. !!! tip Redis support is added in version 11.0. Currently only single-node Redis is supported. Redis Sentinel or Cluster is not supported yet. From 0782e70445e9e9fb7becf4697674a5182558826c Mon Sep 17 00:00:00 2001 From: Junxiang Huang Date: Sun, 23 Feb 2025 14:28:35 +0800 Subject: [PATCH 2/8] fix: some error --- manual/extension/metadata-server.md | 89 ------------------------- manual/repo/docker/md-server.yml | 48 ------------- manual/repo/docker/pro/env | 2 +- manual/setup/use_other_reverse_proxy.md | 2 +- 4 files changed, 2 insertions(+), 139 deletions(-) delete mode 100644 manual/extension/metadata-server.md delete mode 100644 manual/repo/docker/md-server.yml diff --git a/manual/extension/metadata-server.md b/manual/extension/metadata-server.md deleted file mode 100644 index 89e69907..00000000 --- a/manual/extension/metadata-server.md +++ /dev/null @@ -1,89 +0,0 @@ ---- -status: new ---- - -# Metadata server - -Metadata server aims to provide metadata management for your libraries, so as to better understand the relevant information of your libraries. - -## Deployment - -!!! note "Prerequisites" - The startup of Metadata server **requires the use of *Redis* service**, but Seafile server uses *Memcached* as the cache server by default, so you must [deploy ***Redis*** for Seafile](../config/seafile-conf.md#cache-pro-edition-only) before using Metadata server, or use an external Redis service. - -### Download YML file - - Please download YML file **in your `seafile-server.yml` directory** by following command: - - ```sh - wget https://manual.seafile.com/12.0/repo/docker/md-server.yml - ``` - -### Modify `.env` according - -Normally, you don't need to set additional variables in `.env` for metadata server, because the default settings and necessary environment variables will be consistent with Seafile server (e.g., `JWT_PRIVATE_KEY`), and the metadata of libraries will be stored locally (default is `/opt/md-data`). By the way, you can also add or modify relevant environment variables in `.env` according to the information in the following table: - -!!! success "Faster configuration" - Metadata-server docker we use an one-time configuration file, which will be generated directly through the environment variable, eliminating the need for you to repeatedly write configuration files (i.e., **no `md-server.conf`**), which will significantly improve your deployment efficiency. - - -| Variables | Description | Required | -| --- | --- | --- | -| `MD_STORAGE_TYPE` | The type of backend storage. Options: `file` (local storage), `s3`, `oss`. | Optional, default `file` | -| `MD_DATA` | Directory where local data (only valid in `MD_STORAGE_TYPE=file`) and cache are located. | Optional, default `/opt/md-data` | -| `MD_MAX_CACHE_SIZE` | The maximum cache size. | Optional, default `1GB` | -| `MD_S3_HOST` | Host of s3 backend. | Optional | -| `MD_S3_AWS_REGION` | Region of *AWS* s3 backend. | Optional | -| `MD_S3_USE_HTTPS` | Use https connecting to S3 backend. | Optional, default `true` | -| `MD_S3_BUCKET` | Name of S3 bucket for storaging metadata. | **Required** | -| `MD_S3_PATH_STYLE_REQUEST` | S3 backend use path style request. | Optional, default `false` | -| `MD_S3_KEY_ID` | S3 backend authorization key ID. | **Required** | -| `MD_S3_KEY` | S3 backend authorization key secret. | **Required** | -| `MD_S3_USE_V4_SIGNATURE` | Use V4 signature to S3 storage backend. | Optional, default `true` | -| `MD_S3_SSE_C_KEY` | S3 SSE-C key. | Optional | -| `MD_OSS_HOST` | OSS backend host. | Optional | -| `MD_OSS_REGION` | OSS backend region. | Optional | -| `MD_OSS_BUCKET` | Name of OSS bucket for storaging metadata. | **Required** | -| `MD_OSS_KEY_ID` | OSS backend authorization key ID. | **Required** | -| `MD_OSS_KEY` | OSS backend authorization key secret. | **Required** | -| `REDIS_HOST` | Your *Redis* service host. | Optional, default `redis` | -| `REDIS_PORT` | Your *Redis* service port. | Optional, default `6379` | -| `REDIS_PASSWORD` | Your *Redis* access password. | Optional | - - -!!! tip "More descriptions about *Optional* and *Required* in above table" - - In the table above, although many items are marked as *Required*, some of them are only required when the storage backend specified by `MD_STORAGE_TYPE` is used: - - `MD_S3_xxx` only valid in `MD_STORAGE_TYPE=s3` - - `MD_OSS_xxx` only valid in `MD_STORAGE_TYPE=oss` - - - If `MD_STORAGE_TYPE` is `s3` or `oss`, although `MD_xxx_HOST` and `MD_xxx_REGION` are marked as ***Optional***, when you use one of these two storage backends, **you must specify at least one of `MD_xxx_HOST` and `MD_xxx_REGION`, otherwise the service will fail to start**. - -## Start service - -You can use following command to start metadata server: - -```sh -docker compose up -d -``` - -!!! success - If the container startups normally, the follow message you can get from `docker logs -f metadata-server`: - ```log - [md-server] [2025-01-24 06:23:44] [INFO] Environment variable validity checked - [md-server] [2025-01-24 06:23:44] [INFO] Database initialization completed - [md-server] [2025-01-24 06:23:44] [INFO] Configuration file generated - [md-server] [2025-01-24 06:45:17] [INFO] starting seaf-md-server - ``` - -!!! note "About listening port of Metadata server" - - By default, the Metadata server listens on port 8084. You can modify it by specifying `MD_PORT` in .env. At the same time, due to security reasons, this port is not open to the external network. If you need to open this port, you need to modify `md-server.yml` to uncomment the following: - - ```yml - services: - metadata-server: - ... - ports: - - ${MD_PORT:-8084}:${MD_PORT:-8084} - ... - ``` diff --git a/manual/repo/docker/md-server.yml b/manual/repo/docker/md-server.yml deleted file mode 100644 index 6e7b755d..00000000 --- a/manual/repo/docker/md-server.yml +++ /dev/null @@ -1,48 +0,0 @@ -services: - metadata-server: - image: ${MD_IMAGE:-seafileltd/metadata-server:latest} - container_name: metadata-server - volumes: - - ${MD_DATA:-/opt/md-data}:/data - - ${SEAFILE_VOLUME:-/opt/seafile-data}/seafile:/opt/seafile - #ports: - # - ${MD_PORT:-8084}:${MD_PORT:-8084} - environment: - - JWT_PRIVATE_KEY=${JWT_PRIVATE_KEY:?Variable is not set or empty} - - SEAFILE_MYSQL_DB_HOST=${SEAFILE_MYSQL_DB_HOST:-db} - - SEAFILE_MYSQL_DB_PORT=${SEAFILE_MYSQL_DB_PORT:-3306} - - SEAFILE_MYSQL_DB_USER=${SEAFILE_MYSQL_DB_USER:-seafile} - - SEAFILE_MYSQL_DB_PASSWORD=${SEAFILE_MYSQL_DB_PASSWORD:?Variable is not set or empty} - - SEAFILE_MYSQL_DB_SEAFILE_DB_NAME=${SEAFILE_MYSQL_DB_SEAFILE_DB_NAME:-seafile_db} - - SEAFILE_LOG_TO_STDOUT=${SEAFILE_LOG_TO_STDOUT:-false} - - MD_PORT=${MD_PORT:-8084} - - MD_LOG_LEVEL=${MD_LOG_LEVEL:-info} - - MD_MAX_CACHE_SIZE=${MD_MAX_CACHE_SIZE:-1GB} - - MD_STORAGE_TYPE=${MD_STORAGE_TYPE:-file} - - MD_S3_HOST=${MD_S3_HOST:-} - - MD_S3_AWS_REGION=${MD_S3_AWS_REGION:-} - - MD_S3_USE_HTTPS=${MD_S3_USE_HTTPS:-true} - - MD_S3_BUCKET=${MD_S3_BUCKET:-} - - MD_S3_PATH_STYLE_REQUEST=${MD_S3_PATH_STYLE_REQUEST:-false} - - MD_S3_KEY_ID=${MD_S3_KEY_ID:-} - - MD_S3_KEY=${MD_S3_KEY:-} - - MD_S3_USE_V4_SIGNATURE=${MD_S3_USE_V4_SIGNATURE:-true} - - MD_S3_SSE_C_KEY=${MD_S3_SSE_C_KEY:-} - - MD_OSS_HOST=${MD_OSS_HOST:-} - - MD_OSS_REGION=${MD_OSS_REGION:-} - - MD_OSS_BUCKET=${MD_OSS_BUCKET:-} - - MD_OSS_KEY_ID=${MD_OSS_KEY_ID:-} - - MD_OSS_KEY=${MD_OSS_KEY:-} - - REDIS_HOST=${REDIS_HOST:-redis} - - REDIS_PORT=${REDIS_PORT:-6379} - - REDIS_PASSWORD=${REDIS_PASSWORD:-} - depends_on: - db: - condition: service_healthy - - networks: - - seafile-net - -networks: - seafile-net: - name: seafile-net diff --git a/manual/repo/docker/pro/env b/manual/repo/docker/pro/env index 247f8e25..3f9b9b08 100644 --- a/manual/repo/docker/pro/env +++ b/manual/repo/docker/pro/env @@ -69,7 +69,7 @@ SEASEARCH_IMAGE=seafileltd/seasearch:latest SS_STORAGE_TYPE=disk # disk (local storage), s3, oss ### Local storage mode -SS_DATA_PATH=./data # Persistent storage path +SS_DATA_PATH=/opt/seasearch-data # Persistent storage path SS_MAX_OBJ_CACHE_SIZE=10GB ### S3 mode diff --git a/manual/setup/use_other_reverse_proxy.md b/manual/setup/use_other_reverse_proxy.md index 9d87f2c8..7afef44c 100644 --- a/manual/setup/use_other_reverse_proxy.md +++ b/manual/setup/use_other_reverse_proxy.md @@ -127,7 +127,7 @@ Modify `nginx.conf` and add reverse proxy for services ***seafile*** and ***sead } location /socket.io { - proxy_pass http://127.0.0.1:8888/; + proxy_pass http://127.0.0.1:8888; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection 'upgrade'; From 98c0bbebd75a56a3b19714924d684b2e7c9f36e9 Mon Sep 17 00:00:00 2001 From: Junxiang Huang Date: Sun, 23 Feb 2025 14:30:32 +0800 Subject: [PATCH 3/8] fix: some error --- manual/setup/use_seasearch.md | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/manual/setup/use_seasearch.md b/manual/setup/use_seasearch.md index f29693a0..2c97dd24 100644 --- a/manual/setup/use_seasearch.md +++ b/manual/setup/use_seasearch.md @@ -47,8 +47,16 @@ If you would like to use *SeaSearch* as the search engine, the `elasticSearch` s ```yml services: - #elasticsearch: # remove or note the whole `elasticsearch` section - #... + seafile: + ... + depends_on: + ... + #elasticsearch: # remove or note the `elasticsearch` service Dependency + #condition: service_started + + + #elasticsearch: # remove or note the whole `elasticsearch` section + #... ``` ## Modify `seafevents.conf` From 5b0818e95974917705f6bb8d2c6adf6216db4434 Mon Sep 17 00:00:00 2001 From: Daniel Pan Date: Mon, 24 Feb 2025 13:43:14 +0800 Subject: [PATCH 4/8] Improve upgrade document for 11.0 to 12.0 --- manual/upgrade/upgrade_notes_for_12.0.x.md | 54 +++++++++++----------- 1 file changed, 28 insertions(+), 26 deletions(-) diff --git a/manual/upgrade/upgrade_notes_for_12.0.x.md b/manual/upgrade/upgrade_notes_for_12.0.x.md index 45749a73..6d20e6b2 100644 --- a/manual/upgrade/upgrade_notes_for_12.0.x.md +++ b/manual/upgrade/upgrade_notes_for_12.0.x.md @@ -85,38 +85,33 @@ Note, you should install Python libraries system wide using root user or sudo mo The following instruction is for binary package based installation. If you use Docker based installation, please see [*Updgrade Docker*](./upgrade_docker.md) -!!! note "Notification Server" - If you has deployed the [Notification Server](../extension/notification-server.md). The *Notification Server* should be **re-deployed** with the same version as Seafile server. +### 1) Clean database tables before upgrade - For example: - - - Seafile server: 12.0.3 - - notification-server: 12.0.3 +If you have a large number of `Activity` in MySQL, clear this table first [Clean Database](../../administration/clean_database). Otherwise, the database upgrade will take a long time. - You can modify `.env` in your Notification Server host to re-deploy: +### 2) Install new system libraries and Python libraries - ```sh - NOTIFICATION_SERVER_IMAGE=seafileltd/notification-server:12.0-latest - ``` +Install new system libraries and Python libraries for your operation system as documented above. - Restart Notification Server: - ```sh - docker compose restart - ``` +### 3) Stop Seafile-11.0.x server -!!! tip "Clean Database" - If you have a large number of `Activity` in MySQL, clear this table first [Clean Database](../../administration/clean_database). Otherwise, the database upgrade will take a long time. +In the folder of Seafile 11.0.x, run the commands: -### 1) Stop Seafile-11.0.x server +```sh +./seahub.sh stop +./seafile.sh stop +``` -### 2) Start from Seafile 12.0.x, run the script +### 4) Run Seafile 12.0.x upgrade script + +In the folder of Seafile 12.0.x, run the upgrade script ```sh upgrade/upgrade_11.0_12.0.sh ``` -### 3) Create the `.env` file in `conf/` directory +### 5) Create the `.env` file in `conf/` directory conf/.env @@ -141,18 +136,25 @@ SEAFILE_MYSQL_DB_SEAHUB_DB_NAME=seahub_db pwgen -s 40 1 ``` -### 4) Start Seafile-12.0.x server +### 6) Start Seafile-12.0.x server -### 5) Upgrade notification server +In the folder of Seafile 12.0.x, run the command: -Since seafile 12.0, we use docker to deploy the notification server. Please follow the document of [notification server](../extension/notification-server.md). +``` +./seafile.sh start # starts seaf-server +./seahub.sh start # starts seahub +``` + +### 7) (Optional) Upgrade notification server + +Since seafile 12.0, we use docker to deploy the notification server. Please follow the document of [notification server](../extension/notification-server.md) to re-deploy notification server. !!! note Notification server and Seafile binary package - Notification server is designed to be work with Docker based deployment. To make it work with **Seafile binary package** on the same server is, you will need to add Nginx rules for notification server properly. + Notification server is designed to be work with Docker based deployment. To make it work with **Seafile binary package** on the same server, you will need to add Nginx rules for notification server properly. -## Upgrade SeaDoc from 0.8 to 1.0 +### 8) (Optional) Upgrade SeaDoc from 0.8 to 1.0 If you have deployed SeaDoc v0.8 with Seafile v11.0, you can upgrade it to 1.0 use the following two steps: @@ -164,11 +166,11 @@ If you have deployed SeaDoc v0.8 with Seafile v11.0, you can upgrade it to 1.0 u Deploying SeaDoc and **Seafile binary package** on the same server is no longer officially supported. You will need to add Nginx rules for SeaDoc server properly. -### Delete sdoc_db +#### 8.1) Delete sdoc_db From version 1.0, SeaDoc is using seahub_db database to store its operation logs and no longer need an extra database sdoc_db. The database tables in seahub_db are created automatically when you upgrade Seafile server from v11.0 to v12.0. You can simply delete sdoc_db. -### Deploy a new SeaDoc server +#### 8.2) Deploy a new SeaDoc server 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. From 53e1d1c71c396768d343f355e1e4fd9af8b85871 Mon Sep 17 00:00:00 2001 From: Daniel Pan Date: Mon, 24 Feb 2025 16:40:52 +0800 Subject: [PATCH 5/8] Update document on upgrade Seafile cluster (binary) --- manual/upgrade/upgrade_a_cluster_binary.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/manual/upgrade/upgrade_a_cluster_binary.md b/manual/upgrade/upgrade_a_cluster_binary.md index 404faffa..680b4317 100644 --- a/manual/upgrade/upgrade_a_cluster_binary.md +++ b/manual/upgrade/upgrade_a_cluster_binary.md @@ -20,7 +20,7 @@ In general, to upgrade a cluster, you need: Doing maintanence upgrading is simple, you only need to run the script `./upgrade/minor_upgrade.sh` at each node to update the symbolic link. -## Upgrade from Seafile 11 cluster (all nodes) +## Upgrade a cluster from Seafile 11 to 12 !!! tip "Clean Database" If you have a large number of `Activity` in MySQL, clear this table first [Clean Database](../../administration/clean_database). Otherwise, the database upgrade will take a long time. @@ -53,7 +53,7 @@ Doing maintanence upgrading is simple, you only need to run the script `./upgrad 3. [Download](../setup_binary/installation_pro.md#downloading-the-install-package) and [uncompress](../setup_binary/installation_pro.md#uncompressing-the-package) the package -4. Upgrade +4. Run the upgrade script in a single node ```sh seafile-pro-server-12.x.x/upgrade/upgrade_11.0_12.0.sh @@ -78,6 +78,6 @@ Doing maintanence upgrading is simple, you only need to run the script `./upgrad ./seafile-background-tasks.sh start ``` -7. Refer [here](./upgrade_notes_for_12.0.x.md#5-upgrade-notification-server) to upgrade notification server +7. (Optional) Refer [here](./upgrade_notes_for_12.0.x.md#5-upgrade-notification-server) to upgrade notification server -8. Refer [here](./upgrade_notes_for_12.0.x.md#upgrade-seadoc-from-08-to-10) to upgrade SeaDoc server +8. (Optional) Refer [here](./upgrade_notes_for_12.0.x.md#upgrade-seadoc-from-08-to-10) to upgrade SeaDoc server From 6e5e382fa0e17e0d067d48f1334e985586c695d6 Mon Sep 17 00:00:00 2001 From: Junxiang Huang Date: Tue, 25 Feb 2025 10:08:26 +0800 Subject: [PATCH 6/8] fix: upgrade from docker links --- manual/upgrade/upgrade_docker.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/manual/upgrade/upgrade_docker.md b/manual/upgrade/upgrade_docker.md index 4ba5c131..96c54a64 100644 --- a/manual/upgrade/upgrade_docker.md +++ b/manual/upgrade/upgrade_docker.md @@ -21,7 +21,7 @@ mv docker-compose.yml docker-compose.yml.bak ### Download Seafile 12.0 Docker files -Download [.env](../docker/ce/env), [seafile-server.yml](../docker/ce/seafile-server.yml) and [caddy.yml](../docker/caddy.yml), and modify .env file according to the old configuration in `docker-compose.yml.bak` +Download `.env`, `seafile-server.yml` and `caddy.yml`, and modify `.env` file according to the old configuration in `docker-compose.yml.bak` === "Seafile community edition" From 07be06e9d1dea1726b0d8807e12025bc6aff849d Mon Sep 17 00:00:00 2001 From: Junxiang Huang Date: Tue, 25 Feb 2025 10:11:28 +0800 Subject: [PATCH 7/8] opt: onlyoffice deployment --- manual/extension/only_office.md | 1 + manual/setup/use_other_reverse_proxy.md | 15 +++++++++++++++ 2 files changed, 16 insertions(+) diff --git a/manual/extension/only_office.md b/manual/extension/only_office.md index c4481df5..bd71e9c1 100644 --- a/manual/extension/only_office.md +++ b/manual/extension/only_office.md @@ -43,6 +43,7 @@ Also modify `seahub_settings.py` ENABLE_ONLYOFFICE = True ONLYOFFICE_APIJS_URL = 'https://seafile.example.com:6233/web-apps/apps/api/documents/api.js' ONLYOFFICE_FILE_EXTENSION = ('doc', 'docx', 'ppt', 'pptx', 'xls', 'xlsx', 'odt', 'fodt', 'odp', 'fodp', 'ods', 'fods', 'csv', 'ppsx', 'pps') +ONLYOFFICE_EDIT_FILE_EXTENSION = ('docx', 'pptx', 'xlsx') ONLYOFFICE_JWT_SECRET = '' ``` diff --git a/manual/setup/use_other_reverse_proxy.md b/manual/setup/use_other_reverse_proxy.md index 7afef44c..54268764 100644 --- a/manual/setup/use_other_reverse_proxy.md +++ b/manual/setup/use_other_reverse_proxy.md @@ -158,6 +158,21 @@ Modify `nginx.conf` and add reverse proxy for services ***seafile*** and ***sead error_log /var/log/nginx/notification.error.log; } ``` +=== "onlyoffice" + ```conf + location /onlyofficeds/ { + proxy_pass http://127.0.0.1:6233/; + 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 .env From 8b00042165ccf49de62d6e0fb6b843473e6d5105 Mon Sep 17 00:00:00 2001 From: Junxiang Huang Date: Tue, 25 Feb 2025 11:00:33 +0800 Subject: [PATCH 8/8] resolve merge conflicts --- manual/repo/docker/md-server.yml | 48 ++++++++++++++++++++++++++++++++ 1 file changed, 48 insertions(+) create mode 100644 manual/repo/docker/md-server.yml diff --git a/manual/repo/docker/md-server.yml b/manual/repo/docker/md-server.yml new file mode 100644 index 00000000..7aa2c941 --- /dev/null +++ b/manual/repo/docker/md-server.yml @@ -0,0 +1,48 @@ +services: + metadata-server: + image: ${MD_IMAGE:-seafileltd/metadata-server:latest} + container_name: metadata-server + volumes: + - ${MD_DATA:-/opt/md-data}:/data + - ${SEAFILE_VOLUME:-/opt/seafile-data}/seafile:/opt/seafile + #ports: + # - ${MD_PORT:-8084}:${MD_PORT:-8084} + environment: + - JWT_PRIVATE_KEY=${JWT_PRIVATE_KEY:?Variable is not set or empty} + - SEAFILE_MYSQL_DB_HOST=${SEAFILE_MYSQL_DB_HOST:-db} + - SEAFILE_MYSQL_DB_PORT=${SEAFILE_MYSQL_DB_PORT:-3306} + - SEAFILE_MYSQL_DB_USER=${SEAFILE_MYSQL_DB_USER:-seafile} + - SEAFILE_MYSQL_DB_PASSWORD=${SEAFILE_MYSQL_DB_PASSWORD:?Variable is not set or empty} + - SEAFILE_MYSQL_DB_SEAFILE_DB_NAME=${SEAFILE_MYSQL_DB_SEAFILE_DB_NAME:-seafile_db} + - SEAFILE_LOG_TO_STDOUT=${SEAFILE_LOG_TO_STDOUT:-false} + - MD_PORT=${MD_PORT:-8084} + - MD_LOG_LEVEL=${MD_LOG_LEVEL:-info} + - MD_MAX_CACHE_SIZE=${MD_MAX_CACHE_SIZE:-1GB} + - MD_STORAGE_TYPE=${MD_STORAGE_TYPE:-file} + - MD_S3_HOST=${MD_S3_HOST:-} + - MD_S3_AWS_REGION=${MD_S3_AWS_REGION:-} + - MD_S3_USE_HTTPS=${MD_S3_USE_HTTPS:-true} + - MD_S3_BUCKET=${MD_S3_BUCKET:-} + - MD_S3_PATH_STYLE_REQUEST=${MD_S3_PATH_STYLE_REQUEST:-false} + - MD_S3_KEY_ID=${MD_S3_KEY_ID:-} + - MD_S3_KEY=${MD_S3_KEY:-} + - MD_S3_USE_V4_SIGNATURE=${MD_S3_USE_V4_SIGNATURE:-true} + - MD_S3_SSE_C_KEY=${MD_S3_SSE_C_KEY:-} + - MD_OSS_HOST=${MD_OSS_HOST:-} + - MD_OSS_REGION=${MD_OSS_REGION:-} + - MD_OSS_BUCKET=${MD_OSS_BUCKET:-} + - MD_OSS_KEY_ID=${MD_OSS_KEY_ID:-} + - MD_OSS_KEY=${MD_OSS_KEY:-} + - REDIS_HOST=${REDIS_HOST:-redis} + - REDIS_PORT=${REDIS_PORT:-6379} + - REDIS_PASSWORD=${REDIS_PASSWORD:-} + depends_on: + db: + condition: service_healthy + + networks: + - seafile-net + +networks: + seafile-net: + name: seafile-net \ No newline at end of file