-
Notifications
You must be signed in to change notification settings - Fork 60.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Doc]文档似乎不是很清晰 #5007
Comments
Please follow the issue template to update title and description of your issue. |
Title: [Doc]The documentation seems not very clear |
I'm experiencing the same bug, if I use @Azure to work with the model, I can't generate the title |
https://github.com/search?q=repo%3A ChatGPT NextWeb%2F ChatGPT-Next-Web+SUMMARIZE_MODEL type=issues |
不是文档写不清晰的问题,是目前有azure openai有bug,现在应该在修代码而不是文档 |
It’s not a problem that the documentation is unclear, it’s that there are bugs in Azure OpenAI, and now we should be fixing the code instead of the documentation. |
按前面的命令启动docker没有发现azure的问题。
如果你这边有其他的问题。可以提供一下具体的配置以及报错信息,方便排查。 |
No problem with Azure was found when starting docker according to the previous command.
If you have any other questions here. You can provide specific configuration and error information to facilitate troubleshooting. |
Can the summary request use azure openai in future versions? |
I can help to fix the document |
Bug Description
试图使用docker(podman)部署nextchatweb来使用azure openai api。看文档没找到正确的路子,最后发现要这么配置环境变量:
有几个坑:
AZURE_URL
不是https://{azure-resource-url}/openai/deployments/{deploy-name}
,而是https://{azure-resource-url}/openai
CUSTOM_MODELS
,删除所有模型,仅手动增加azure的模型。否则页面会使用openai的模型而报错。关键在于我没有配置openai的相关东西,默认还走openai,应该默认走azure才合理。另外我发现,总结对话的题目用的还是openai接口,我的日志里出现了访问openai超时的日志,并且无法生成对话标题。这应该也是默认行为不太合理的问题。
Steps to Reproduce
以如下命令部署:
Expected Behavior
期望修正文档,以及修改默认行为,避免使用未配置的openai接口
Screenshots
No response
Deployment Method
Desktop OS
No response
Desktop Browser
No response
Desktop Browser Version
No response
Smartphone Device
No response
Smartphone OS
No response
Smartphone Browser
No response
Smartphone Browser Version
No response
Additional Logs
No response
The text was updated successfully, but these errors were encountered: