Wire demo-mode/seed env vars into compose - #311
Merged
Conversation
2 tasks
haksungjang
force-pushed
the
compose-env-wiring/demo-seed
branch
from
September 3, 2026 05:20
12c07b4 to
7c84417
Compare
3 vars documented in .env.example (demo SaaS sandbox-scan allowance, demo read-only lockdown, seed_demo.py bootstrap super-admin password override) were never referenced in x-backend-env, so setting them in .env had no effect on the running container. Adds them with defaults matching core/config.py exactly. Part of the compose env-var wiring audit.
haksungjang
force-pushed
the
compose-env-wiring/demo-seed
branch
from
September 3, 2026 08:50
7c84417 to
647d74c
Compare
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.
Summary
.env.example(demo SaaS sandbox-scan allowance, demo read-only lockdown,seed_demo.pybootstrap super-admin password override) were never referenced inx-backend-env, so setting them in.envhad no effect on the running container.core/config.pyexactly.Context
Part of the same compose env-var wiring audit as #300/#301/#303/#304/#306/#307/#308/#309/#310.
Test plan