Merge pull request #477 from RealTong/fix-cn-readme

fix: 🐛 modify document

Dockerfile

@@ -8,7 +8,7 @@ RUN apt-get install -y wget \
     && rm -rf /var/lib/apt/lists/* \
     && echo "Chrome: " && google-chrome --version
 WORKDIR /app
-COPY package*.json .
+COPY package*.json ./
 RUN npm install
 COPY . .
 ENV WECHATY_PUPPET_WECHAT_ENDPOINT=/usr/bin/google-chrome

README.md

@@ -160,9 +160,9 @@ After some validation is complete, you can begin the deployment.You will see the
 
 Some environment variables need to be configured:
 
-- **CHAT_GPT_EMAIL** : Your OpenAI Account email, if you have session_token, It's optional.
+- **CHAT_GPT_EMAIL** : Your OpenAI Account email.
 
-- **CHAT_GPT_PASSWORD** : Your OpenAI Account password, *if you have session_token, It's optional*.
+- **CHAT_GPT_PASSWORD** : Your OpenAI Account password.
 
 - **CHAT_GPT_RETRY_TIMES** : The number of times to retry when the OpenAI API returns 429 or 503.
 
@@ -184,7 +184,7 @@ Log in successfully and start sending and receiving messages(This process can ta
 
 Besides, in deployment, you may encounter the following issues:
 
-- **Error: ⚠️ No chatgpt item in pool** : This error means that you have not configured the OpenAI account information correctly. You can solve this problem from the following aspects:1. Check whether the token or openAI account and password are filled in correctly. 2. The token may have expired (experience shows that the expiration time of the token is **24** hours), you can go to the chatGPT official website to re-obtain the token. 3. Redeploy Current Services.Note that the above should be modified on the Variables page in Railway Dashboard.
+- **Error: ⚠️ No chatgpt item in pool** : This error means that you have not configured the OpenAI account information correctly. You can solve this problem from the following aspects:1. Check whether the token or openAI account and password are filled in correctly. 2. Redeploy Current Services.Note that the above should be modified on the Variables page in Railway Dashboard. 3. Please make sure that CloudFlare human authentication is present, if it is, Headless browser may not be able to simulate logging into OpenAI.
 - **After the deployment is complete, the QR code is not generated**.Try **refreshing** the page to see again if the Deploy Logs panel generated a link and QR code.
 - **The generated QR code cannot be scanned**.On the generated QR code, there is a link that can be clicked to scan the QR code.
 - **Message feedback is very slow**.Because Railway's servers are deployed overseas, there is an increase in message feedback latency, but it is still within the acceptance range. If you are time sensitive, you can use your own server deployment.

README_ZH.md

@@ -157,9 +157,9 @@ npm run dev
 
 您需要配置一些环境变量：
 
-- **CHAT_GPT_EMAIL** ：您的 OpenAI 帐户电子邮件，如果您有 session_token，则可不填。
+- **CHAT_GPT_EMAIL** ：您的 OpenAI 帐户电子邮件。
 
-- **CHAT_GPT_PASSWORD** ：您的 OpenAI 帐户密码，如果您有 session_token，则可不填。
+- **CHAT_GPT_PASSWORD** ：您的 OpenAI 帐户密码。
 
 - **CHAT_GPT_RETRY_TIMES** ：当 OpenAI API 返回 429 或 503 时重试的次数。
 
@@ -181,7 +181,7 @@ npm run dev
 
 此外，在部署中，您可能会遇到以下问题：
 
-- **Error: ⚠️ No chatgpt item in pool**：此错误表示验证信息有问题。您可以从以下几个方面解决此问题：1.检查 token 或 openAI 账号和密码是否正确填写。2. token 可能已经过期（经验表明 token 的过期时间为**24**小时），您可以到 chatGPT 官网重新获取 token。3. 重新部署当前服务。请注意，应在铁路仪表板的 **Variables** 页面上修改上述内容。
+- **Error: ⚠️ No chatgpt item in pool**：此错误表示验证信息有问题。您可以从以下几个方面解决此问题：1.检查 token 或 openAI 账号和密码是否正确填写。2. 重新部署当前服务。请注意，应在铁路仪表板的 **Variables** 页面上修改上述内容。 3. 请确认是否出现了CloudFlare人机验证, 如果出现了CloudFlare的人机验证, 则可能导致 Headless 浏览器无法成功模拟登录。
 - **部署完成后，不会生成二维码**。尝试**刷新**页面，再次查看 Deploy Logs 面板是否生成了链接和二维码。
 - **生成的二维码无法扫描**。在生成的二维码上，有一个链接可以点击扫描二维码。
 - **消息反馈缓慢**。由于 Railway 的服务器部署在海外，消息反馈延迟会有所增加，但仍在可接受范围内。如果您对时间敏感，则可以使用自己的服务器部署。