compose: forward AI provider + mailer/SMTP env to the backend #242
Reference in New Issue
Block a user
Delete Branch "compose-ai-smtp-passthrough"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow-up to #241. The backend env block is an explicit allow-list, so the documented model-provider keys (
ANTHROPIC_*,OPENAI_*,XAI_*,OLLAMA_*,DEFAULT_*_PROVIDER,LLM_MAX_TOKENS,EMBEDDING_DIMENSIONS) and mailer settings (MAILER,SMTP_*,APP_BASE_URL,REQUIRE_EMAIL_VERIFICATION) never reached the container — setting them in.envwas a no-op. The assistant/AI-policy and the SMTP mailer run in the backend, so forward them there.Side fix:
APP_BASE_URLwas also dropped, so outbound email links used the code defaulthttp://localhostinstead of the configured domain. Now forwarded — verified live: backend reportsAPP_BASE_URL=https://provenance.paul.farm.Verified on prod: all forwarded vars present in the backend container; app healthy (
/health/ready200,/api/v1/public/trees200).Worker left as-is (consumes neither today).
env_file: .envis the alternative to a growing allow-list — deferred to avoid forwarding unrelated secrets into the app process.🤖 Generated with Claude Code