From 37b916feaad0abf6e54a5cb76bbd123b095bcb44 Mon Sep 17 00:00:00 2001 From: Junxiang Huang Date: Thu, 20 Mar 2025 17:52:18 +0800 Subject: [PATCH] add explanation about adding COMPOSE_FILE to md-server.yml --- manual/extension/metadata-server.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/manual/extension/metadata-server.md b/manual/extension/metadata-server.md index 58109e02..43d0c381 100644 --- a/manual/extension/metadata-server.md +++ b/manual/extension/metadata-server.md @@ -32,7 +32,13 @@ Please download the file by following command: ### Modify `.env` -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: +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`). But you still need to modify the `COMPOSE_FILE` list in `.env`, and add `md-server.yml` to enable the metadata server: + +``` +COMPOSE_FILE='...,md-server.yml' +``` + +The following table is all the related environment variables with metadata-server: | Variables | Description | Required | | --- | --- | --- |