-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Add support for VolcEngine - the current version supports SDK2 #885
Conversation
- 主要思路,将ak、sk、ep_id组装存储到数据库api_key字段 - 前端了解的少,参考Ollama代码,可能有冗余
Thank you for you contribution! We intend to create an international community, so we encourage using English for issues and pull requests. Would you please update the PR description and the code comments ? |
I have made modifications. Since this is my first PR, please give me some guidance. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
well done
Dear @yungongzi and all, Since VolcEngine's latest model(Doubao series) and SDK v3 has been published for quiet a while, may I know if you considerate to make a new feature to support that? AFAIK, the v3 SDK supports API_KEY, and the LLMs are named as Doubao-[pro|lite]-[4k|32k|128k]. Your sincerely. |
Ok, I'll try my best to finish. |
Great! And thank you very much for your contribution! |
…iflow#885) - The main idea is to assemble **ak**, **sk**, and **ep_id** into a dictionary and store it in the database **api_key** field - I don’t know much about the front-end, so I learned from Ollama, which may be redundant. ### Configuration method - model name - Format requirements: {"VolcEngine model name":"endpoint_id"} - For example: {"Skylark-pro-32K":"ep-xxxxxxxxx"} - Volcano ACCESS_KEY - Format requirements: VOLC_ACCESSKEY of the volcano engine corresponding to the model - Volcano SECRET_KEY - Format requirements: VOLC_SECRETKEY of the volcano engine corresponding to the model ### What problem does this PR solve? _Briefly describe what this PR aims to solve. Include background context that will help reviewers understand the purpose of the PR._ ### Type of change - [x] New Feature (non-breaking change which adds functionality)
Configuration method
model name
Format requirements: {"VolcEngine model name":"endpoint_id"}
Volcano ACCESS_KEY
Volcano SECRET_KEY
What problem does this PR solve?
Briefly describe what this PR aims to solve. Include background context that will help reviewers understand the purpose of the PR.
Type of change