From 7c5442b392bbcc879bc89768f8343c9ab9961e45 Mon Sep 17 00:00:00 2001 From: yangdx Date: Sat, 29 Mar 2025 04:05:31 +0800 Subject: [PATCH] Update doc --- lightrag/api/README.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/lightrag/api/README.md b/lightrag/api/README.md index bdfe0a29..0a5d8ef9 100644 --- a/lightrag/api/README.md +++ b/lightrag/api/README.md @@ -90,7 +90,9 @@ lightrag-server ``` lightrag-gunicorn --workers 4 ``` -The `.env` file must be placed in the startup directory. Upon launching, the LightRAG Server will create a documents directory (default is `./inputs`) and a data directory (default is `./rag_storage`). This allows you to initiate multiple instances of LightRAG Server from different directories, with each instance configured to listen on a distinct network port. +The `.env` file **must be placed in the startup directory**. + +Upon launching, the LightRAG Server will create a documents directory (default is `./inputs`) and a data directory (default is `./rag_storage`). This allows you to initiate multiple instances of LightRAG Server from different directories, with each instance configured to listen on a distinct network port. Here are some common used startup parameters: @@ -100,6 +102,8 @@ Here are some common used startup parameters: - `--log-level`: Logging level (default: INFO) - --input-dir: specifying the directory to scan for documents (default: ./input) +> The requirement for the .env file to be in the startup directory is intentionally designed this way. The purpose is to support users in launching multiple LightRAG instances simultaneously. Allow different .env files for different instances. + ### Auto scan on startup When starting any of the servers with the `--auto-scan-at-startup` parameter, the system will automatically: