-
Notifications
You must be signed in to change notification settings - Fork 459
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
[Bug] docker部署,NEXT_PUBLIC_GEMINI_MODEL_LIST 未起作用 #47
Comments
Title: [Bug] docker deployment, NEXT_PUBLIC_GEMINI_MODEL_LIST does not work |
目前已经定位到问题的原因,该问题是由于 Next.js 的 standalone 模式导致的,我会想一想解决方案 |
The cause of the problem has been located. The problem is caused by the standalone mode of Next.js. I will think about the solution. |
@Amery2010 你使用的什么部署,我试过docker和cf pages部署模型切换都没用,我看到你的部署可以使用最新模型 |
@Amery2010 What deployment are you using? I tried switching docker and cf pages deployment models but it didn’t work. I saw that your deployment can use the latest model. |
目前试用页面使用的是 vercel 一键部署,docker 目前已知自定义模型列表存在问题,cf pages 如果是静态部署,也是不支持动态变量的。 |
The current trial page uses vercel one-click deployment. Docker is currently known to have problems with the custom model list. If cf pages are deployed statically, they do not support dynamic variables. |
I refactored the way to get global variables in version v1.3.0 and fixed this problem in another way. |
Bug Description
NEXT_PUBLIC_GEMINI_MODEL_LIST=+all,+gemini-1.5-pro-exp-0801
此环境变量未生效,重新部署依然无效
Steps to Reproduce
docker run -d --name talk-with-gemini
-p 5481:3000
-e GEMINI_API_KEY=
-e GEMINI_API_BASE_URL=
-e ACCESS_PASSWORD=
-e NEXT_PUBLIC_GEMINI_MODEL_LIST=+all,+gemini-1.5-pro-exp-0801,+gemma-2-2b-it,+gemma-2-9b-it,gemma-2-27b-it
xiangfa/talk-with-gemini
Expected Behavior
寻求解决方案
Screenshots
Deployment Method
Desktop OS
Ubuntu
Desktop Browser
Microsoft Edge,128.0.2739.5
Desktop Browser Version
128.0.2739.5
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: