You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I deployed nextweb via Docker Compose. I want the service to work by default through the deepseek model without relying on any configuration in the front-end page. This is my original compose file.
But it didn't work. seeing the logs, nextweb still request the apis of openai instead of deepseek.
Then I update my compose file like this, adding OPENAI_API_KEY and BASE_URL configs, pretend to request custom openai url with specified model deepseek-chat, and it works well.
Bot detected the issue body's language is not English, translate it automatically.
Deepseek support has been added to the new commit of the code
However, the release version and the docker version have not been updated simultaneously (it seems that the last update was two months ago)
Hope @lloydzhou@Dogtiti bosses will update soon
hustlibraco
changed the title
[Bug] DeekSeek related environment not work
[Bug] DeepSeek related environment not work
Jan 8, 2025
📦 Deployment Method
Docker
📌 Version
v2.15.8
💻 Operating System
Other Linux
📌 System Version
Alpine Linux 3.20
🌐 Browser
Chrome
📌 Browser Version
131.0.6778.205
🐛 Bug Description
I deployed nextweb via Docker Compose. I want the service to work by default through the deepseek model without relying on any configuration in the front-end page. This is my original compose file.
But it didn't work. seeing the logs, nextweb still request the apis of openai instead of deepseek.
Then I update my compose file like this, adding OPENAI_API_KEY and BASE_URL configs, pretend to request custom openai url with specified model deepseek-chat, and it works well.
I think there is something wrong with DEEPSEEK_URL and DEEPSEEK_API_KEY config items, or my misconfig, plz let me know the truth, thank you!
📷 Recurrence Steps
No response
🚦 Expected Behavior
No response
📝 Additional Information
No response
The text was updated successfully, but these errors were encountered: