Self-host with Docker Compose and optional server-held keys
維護者通常 1 天內回覆
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 18/100
研究方向
Start with docker/Dockerfile.app, apps/agent/Dockerfile (to be added) and apps/mcp/Dockerfile, then check the agent's server_credentials_available handling and the chat UI's browser key prompt. Done means docker compose up serves the app, agent and MCP server on 127.0.0.1, and with NEXT_PUBLIC_SERVER_KEYS=true the key prompt is skipped while the default hosted behaviour is unchanged. PR #101 is already open against this issue, so check with the maintainers before starting a parallel implementation.
由索引模型根據 Issue 內容生成。
描述
Problem
Running the app day to day on your own machine takes three processes (app, agent, MCP), and the existing apps/mcp/Dockerfile can't build from the repo: it expects an apps/mcp/pnpm-lock.yaml that doesn't exist, and @repo/design-system is a workspace dependency. Separately, the chat UI always asks for browser keys before sending, even when the agent already has shared keys in apps/agent/.env. The agent accepts header-less requests in that case (server_credentials_available), so the prompt is the only thing in the way.
Proposal
- A
docker-compose.ymlthat builds and runs the app, agent and MCP server, bound to127.0.0.1withrestart: unless-stopped. It reusesdocker/Dockerfile.app, addsapps/agent/Dockerfile(uv, frozen lock), and addsdocker/Dockerfile.mcp, which builds from the workspace root. - An opt-in, build-time
NEXT_PUBLIC_SERVER_KEYS=truethat treats server-held keys as configured, so the browser key prompt is skipped. It's off by default, so the hosted BYOK experience is unchanged. Compose sets it.
I noticed #9/#10 proposed Compose earlier and were closed; I don't know why. If self-hosting via Compose isn't something you want in this repo, that's fine. If it is, I have a PR ready and am happy to reshape it.
- 主要語言
- TypeScript
- 星號
- 3.9k
- 分支
- 414
- 平均合併
- 4 小時
- 30 天內合併 PR
- 6
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
CopilotKit/OpenIntelligentUI 的其他 Issue
-
Script dedup key truncation may cause collisions可能已有人在做 @saschabuehrle 於 217 天前認領。 未關閉bug
難度 2/5 1-3 小時 新手友好度 72/100
CopilotKit/OpenIntelligentUI#37 ·
維護者通常 1 天內回覆
-
enhancement
難度 2/5 1-3 小時 新手友好度 72/100
CopilotKit/OpenIntelligentUI#29 ·
維護者通常 1 天內回覆
-
Support OpenAI-compatible gateways (OpenRouter) via vendor/model names可能已有人在做 @kannan983 於 17 天前認領。 未關閉
難度 2/5 1-3 小時 新手友好度 25/100
CopilotKit/OpenIntelligentUI#97 ·
維護者通常 1 天內回覆
-
UI未關閉
難度 5/5 一週以上 新手友好度 8/100
CopilotKit/OpenIntelligentUI#96 ·
維護者通常 1 天內回覆
-
難度 4/5 3-5 天 新手友好度 48/100
CopilotKit/OpenIntelligentUI#87 · 2 則留言 ·
維護者通常 1 天內回覆
查看 CopilotKit/OpenIntelligentUI 的全部 Issue
相似的 Issue
-
[Bug]: Payment providers removed from config are never disabled in payment_provider可能已有人在做 @medusa-os-bot 今天認領。 未關閉type: bug
難度 2/5 半天 新手友好度 82/100
medusajs/medusa#17544 · 1 則留言 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 74/100
software-mansion/argent#1651 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 76/100
維護者通常 1 天內回覆
-
lane:reliability
難度 2/5 1-3 小時 新手友好度 78/100
維護者通常 1 天內回覆
-
needs-triage
難度 2/5 1-3 小時 新手友好度 70/100
維護者通常 1 天內回覆