From e4eafeeb08a8a17f72bec42e7072f388dea31682 Mon Sep 17 00:00:00 2001 From: Huang Junxiang Date: Thu, 20 Mar 2025 15:34:49 +0800 Subject: [PATCH] opt: metadata deployment description (#481) --- manual/extension/metadata-server.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/manual/extension/metadata-server.md b/manual/extension/metadata-server.md index 284a868d..58109e02 100644 --- a/manual/extension/metadata-server.md +++ b/manual/extension/metadata-server.md @@ -32,10 +32,7 @@ Please download the file by following command: ### Modify `.env` -!!! 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. - -By default, you don't need to add additional variables to your `.env` (except for standalone deployment) to get the metadata server started, because it will read the exact same configuration as the Seafile server (including `JWT_PRIVATE_KEY` ) and keep the repository metadata locally (default `/opt/md-server`). The following table is all the related environment variables with metadata-server: +Metadata server read all configurations from environtment and **does not need a dedicated configuration file**, and you don't need to add additional variables to your `.env` (except for standalone deployment) to get the metadata server started, because it will read the exact same configuration as the Seafile server (including `JWT_PRIVATE_KEY` ) and keep the repository metadata locally (default `/opt/seafile-data/seafile/md-data`). The following table is all the related environment variables with metadata-server: | Variables | Description | Required | | --- | --- | --- |