Daniel.y commited on
Commit
beace6c
·
unverified ·
2 Parent(s): 0a78449 b8fb722

Merge pull request #1223 from danielaskdd/main

Browse files
Files changed (1) hide show
  1. lightrag/api/README.md +5 -1
lightrag/api/README.md CHANGED
@@ -90,7 +90,9 @@ lightrag-server
90
  ```
91
  lightrag-gunicorn --workers 4
92
  ```
93
- 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.
 
 
94
 
95
  Here are some common used startup parameters:
96
 
@@ -100,6 +102,8 @@ Here are some common used startup parameters:
100
  - `--log-level`: Logging level (default: INFO)
101
  - --input-dir: specifying the directory to scan for documents (default: ./input)
102
 
 
 
103
  ### Auto scan on startup
104
 
105
  When starting any of the servers with the `--auto-scan-at-startup` parameter, the system will automatically:
 
90
  ```
91
  lightrag-gunicorn --workers 4
92
  ```
93
+ The `.env` file **must be placed in the startup directory**.
94
+
95
+ 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.
96
 
97
  Here are some common used startup parameters:
98
 
 
102
  - `--log-level`: Logging level (default: INFO)
103
  - --input-dir: specifying the directory to scan for documents (default: ./input)
104
 
105
+ > 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.
106
+
107
  ### Auto scan on startup
108
 
109
  When starting any of the servers with the `--auto-scan-at-startup` parameter, the system will automatically: