Skip to content
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

[Request] 使用Azure API KEY之后,前端是否可以支持自定义开启某些模型 #743

Closed
GuGuGee opened this issue Dec 21, 2023 · 8 comments · Fixed by #773
Closed
Labels
🌠 Feature Request New feature or request | 特性与建议 released

Comments

@GuGuGee
Copy link

GuGuGee commented Dec 21, 2023

🥰 需求描述 | Feature Description

使用Azure API KEY之后,前端是否可以支持自定义开启某些模型

image-20231221114257565

目前默认是和OpenAI API搭建一样,显示所有模型的

🧐 解决方案 | Proposed Solution

我目前用azure api 部署了前端,

给公司的小伙伴使用的时候,会发现其实gpt-4-1106-previewgpt-4-vision-preview是用不了的,

image-20231221114434613

希望前端或者后端可以有一个开关,可以把诸如这俩实际上不可用的模型暂时关闭,这样不会给一些单纯的使用者造成困扰。

谢谢开发者!

📝 补充信息 | Additional Information

No response

@GuGuGee GuGuGee added the 🌠 Feature Request New feature or request | 特性与建议 label Dec 21, 2023
@lobehubbot
Copy link
Member

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿


🥰 Requirement Description | Feature Description

After using Azure API KEY, can the front end support custom opening of certain models?

image-20231221114257565

The current default is the same as the OpenAI API build, which displays all models.

🧐 Solution | Proposed Solution

I currently deploy the front end using azure api,

When used by friends in the company, they will find that gpt-4-1106-preview and gpt-4-vision-preview cannot be used.

image-20231221114434613

I hope there can be a switch on the front end or back end to temporarily turn off these two models that are actually unavailable, so that it will not cause trouble to some simple users.

Thank you developers!

📝 Additional Information |

No response

@lobehubbot
Copy link
Member

👀 @GuGuGee

Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible.
Please make sure you have given us as much context as possible.
非常感谢您提交 issue。我们会尽快调查此事,并尽快回复您。 请确保您已经提供了尽可能多的背景信息。

@opoet
Copy link

opoet commented Dec 22, 2023

有这个设置项,但是如果使用 Docker 部署,目前此变量不会生效,见 #509
https://github.com/lobehub/lobe-chat/wiki/Environment-Variable.zh-CN#next_public_custom_models

@jonnyhou
Copy link

有这个设置项,但是如果使用 Docker 部署,目前此变量不会生效,见 #509 https://github.com/lobehub/lobe-chat/wiki/Environment-Variable.zh-CN#next_public_custom_models

我也遇到这个问题,使用-all,+claude-2,完全无法生效,模型出来还是原始内置的内容。但是在客户端配置的时候是可以生效的,就是太麻烦,每个新访问的客户端都需要配置

@lobehubbot
Copy link
Member

@GuGuGee

This issue is closed, If you have any questions, you can comment and reply.
此问题已经关闭。如果您有任何问题,可以留言并回复。

@lobehubbot
Copy link
Member

🎉 This issue has been resolved in version 0.115.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

@arvinxx
Copy link
Contributor

arvinxx commented Dec 23, 2023

@jonnyhou 尝试使用 CUSTOM_MODELS 变量

@lobehubbot
Copy link
Member

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿


@jonnyhou try using CUSTOM_MODELS variable

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🌠 Feature Request New feature or request | 特性与建议 released
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants