yangdx commited on
Commit
ebe8c66
·
1 Parent(s): 471804d

Update README

Browse files
lightrag/api/README-zh.md CHANGED
@@ -102,6 +102,10 @@ lightrag-gunicorn --workers 4
102
  - `--log-level`:日志级别(默认:INFO)
103
  - --input-dir:指定要扫描文档的目录(默认:./input)
104
 
 
 
 
 
105
  ### 启动时自动扫描
106
 
107
  当使用 `--auto-scan-at-startup` 参数启动任何服务器时,系统将自动:
 
102
  - `--log-level`:日志级别(默认:INFO)
103
  - --input-dir:指定要扫描文档的目录(默认:./input)
104
 
105
+ > ** 要求将.env文件置于启动目录中是经过特意设计的**。 这样做的目的是支持用户同时启动多个LightRAG实例,并为不同实例配置不同的.env文件。
106
+
107
+ > **修改.env文件后,您需要重新打开终端以使新设置生效**。 这是因为每次启动时,LightRAG Server会将.env文件中的环境变量加载至系统环境变量,且系统环境变量的设置具有更高优先级。
108
+
109
  ### 启动时自动扫描
110
 
111
  当使用 `--auto-scan-at-startup` 参数启动任何服务器时,系统将自动:
lightrag/api/README.md CHANGED
@@ -106,6 +106,8 @@ Here are some commonly used startup parameters:
106
 
107
  > 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, allowing different .env files for different instances.
108
 
 
 
109
  ### Auto scan on startup
110
 
111
  When starting any of the servers with the `--auto-scan-at-startup` parameter, the system will automatically:
 
106
 
107
  > 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, allowing different .env files for different instances.
108
 
109
+ > **After changing the .env file, you need to open a new terminal to make the new settings take effect.** This because the LightRAG Server will load the environment variables from .env into the system environment variables each time it starts, and LightRAG Server will prioritize the settings in the system environment variables.
110
+
111
  ### Auto scan on startup
112
 
113
  When starting any of the servers with the `--auto-scan-at-startup` parameter, the system will automatically: