-
-
Notifications
You must be signed in to change notification settings - Fork 9.5k
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] MIDJOURNEY_PROXY_URL 在Docker中不生效 #3013
Comments
👀 @htdohk Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible. |
📦 Deployment environmentDocker 📌 Software versionv1.1.7 💻 System environmentmacOS 🌐 BrowserChrome 🐛 Problem descriptionWhen deploying using Docker, if you want to set environment variables for the midjourney plug-in, fill them in composer 📷 Steps to reproduceNo response 🚦 Expected resultsNo response 📝 Supplementary informationNo response |
Vercel中的环境变量为: @arvinxx 请帮忙支持,谢谢 |
plugin settings 是服务端环境变量,它没法发到前端。(否则像serpapi key这种就会暴露) 目前 mj 插件的走的是 standardalone 的 iframe 嵌入,而 lobechat主体和插件的通信是前端 postMessage 的方案。所以目前还不支持这种环境变量的透传。 未来可能会想一个方案允许这种变量发到前端,然后再在前端进行通信 |
Plugin settings are server-side environment variables, which cannot be sent to the front-end. (Otherwise things like serpapi key will be exposed) At present, the mj plug-in uses standardalone's iframe embedding, and the communication between the lobechat main body and the plug-in is the front-end postMessage solution. Therefore, transparent transmission of such environment variables is not currently supported. In the future, we may think of a solution that allows such variables to be sent to the front end, and then communicated at the front end. |
感谢回复,期待解决~ |
Thanks for the reply, looking forward to solving it~ |
📦 部署环境
Docker
📌 软件版本
v1.1.7
💻 系统环境
macOS
🌐 浏览器
Chrome
🐛 问题描述
使用Docker部署时,想为midjourney插件设置环境变量,在composer里面填写
PLUGIN_SETTINGS: "midjourney:MIDJOURNEY_PROXY_URL=https://xxx.yyy.zzz"
但客户端报错,似乎不能正确识别代理URL。该URL已在midjourney-webui.lobehub.com验证可用。请问这条环境变量应该怎么书写呢?
📷 复现步骤
No response
🚦 期望结果
No response
📝 补充信息
No response
The text was updated successfully, but these errors were encountered: