clarified the docs on UI deployment via docker compose#7085
clarified the docs on UI deployment via docker compose#7085virajmehta wants to merge 1 commit intomainfrom
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1ef70d5b17
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| - ${ENV_FILE:-.env} | ||
| # If your gateway is deployed locally, set | ||
| # environment: | ||
| # TENSORZERO_GATEWAY_URL: http://gateway:3000 |
There was a problem hiding this comment.
This comment suggests TENSORZERO_GATEWAY_URL: http://gateway:3000 when the gateway is deployed locally, but in this Compose snippet only the ui service is defined, so gateway is not a guaranteed DNS name and the UI will fail to connect in the common case where the gateway is running on the host machine. In that setup, users need a host-reachable address (for example host.docker.internal with the appropriate host mapping on Linux), so this guidance can cause a broken deployment.
Useful? React with 👍 / 👎.
2 participants
Note
Low Risk
Low risk documentation-only change that adds guidance for setting
TENSORZERO_GATEWAY_URLin a local Docker Compose setup; no runtime behavior is modified.Overview
Clarifies the
docker-composeexample indocs/deployment/tensorzero-ui.mdxby adding a commentedenvironmentsnippet showing how to setTENSORZERO_GATEWAY_URLwhen the gateway is deployed locally (e.g.,http://gateway:3000).Written by Cursor Bugbot for commit 1ef70d5. This will update automatically on new commits. Configure here.