gardel/lightrag
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge pull request #1223 from danielaskdd/main

Browse Source 
Update doc
This commit is contained in:
Daniel.y
2025-03-29 04:06:50 +08:00
committed by GitHub
parent 1d18d66400 7c5442b392
commit d543f860ca
1 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
lightrag/api/README.md
View File

@@ -90,7 +90,9 @@ lightrag-server
``` ```
lightrag-gunicorn --workers 4 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: Here are some common used startup parameters:
@@ -100,6 +102,8 @@ Here are some common used startup parameters:
- `--log-level`: Logging level (default: INFO) - `--log-level`: Logging level (default: INFO)
- --input-dir: specifying the directory to scan for documents (default: ./input) - --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 ### Auto scan on startup
When starting any of the servers with the `--auto-scan-at-startup` parameter, the system will automatically: When starting any of the servers with the `--auto-scan-at-startup` parameter, the system will automatically: