Skip to content

fix(docker): require the three Compose secrets - #129

Merged
fjlopez merged 1 commit into
devfrom
fix/require-compose-secrets
Oct 27, 2026
Merged

fjlopez merged 1 commit into
devfrom
fix/require-compose-secrets

Conversation

@fjlopez

@fjlopez fjlopez commented Oct 27, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Root Compose refuses to start when SITMUN_USER_SECRET, MIDDLEWARE_SECRET, or SITMUN_MBTILES_JOB_HANDLE_SECRET is unset.
  • setup.sh and setup.ps1 generate those values into a new .env when the keys are absent. Profile files do not store them.
  • tools/scripts/check-compose-secrets.sh fails if docker compose config succeeds without the three secrets.

Test plan

  • bash tools/scripts/check-compose-secrets.sh failed before the :? change (config exited 0) and exits 0 after it.
  • docker compose config with the three secrets set exits 0 and the rendered file does not contain dev-only-insecure.
  • bash -n on setup.sh, check-compose-secrets.sh, and verify-compose-profiles.sh (already run locally).

Fixes #113

Root Compose substituted development defaults when SITMUN_USER_SECRET,
MIDDLEWARE_SECRET, or SITMUN_MBTILES_JOB_HANDLE_SECRET was unset.
Setup generates them into a new .env. Profile files still do not store them.

Fixes #113
@fjlopez
fjlopez merged commit cc5934b into dev Oct 27, 2026
7 checks passed
@fjlopez
fjlopez deleted the fix/require-compose-secrets branch November 1, 2026 16:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant