compose: forward the anonymous-access and MCP env vars to the app container - #97
Merged
Merged
Conversation
…he app container docker-compose.yml lists the env vars it forwards to the app explicitly, so TPK_ANONYMOUS_ACCESS / TPK_ANONYMOUS_DAILY_TOKEN_LIMIT (#95) and TPK_MCP_HTTP_ENABLED / TPK_MCP_ALLOWED_HOSTS (#74) set in .env never reached the container -- the login page could not offer anonymous access on a compose stack. Both compose files now forward them; the k8s README lists them. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Found when starting a compose stack after #95: no "Continue without signing in" button.
Cause: the feature is off by default, and
docker-compose.ymlforwards an explicit list of env vars to theappcontainer —TPK_ANONYMOUS_ACCESS/TPK_ANONYMOUS_DAILY_TOKEN_LIMIT(#95) were not on it, so setting them in.envhad no effect. The same was true ofTPK_MCP_HTTP_ENABLED/TPK_MCP_ALLOWED_HOSTS(#74), which have been undocumented for compose since they shipped.Change: both compose files (
docker-compose.yml,docker-compose.allinone.yml) forward the four vars with the same${VAR:-}pattern as the others;deploy/k8s/README.mdlists them in its configuration table. No code change.Checked: with
TPK_ANONYMOUS_ACCESS=1in.envanddocker compose up -d app,GET /auth/mewithout a token answers{"username":"anonymous", …, "anonymous": true}and the login page offers the button.To enable anonymous chat on a compose stack:
🤖 Generated with Claude Code