Skip to content

fix(setup): append compose secrets when .env already exists - #139

Merged
fjlopez merged 1 commit into
devfrom
fix/138-windows-setup-secrets
Nov 1, 2026
Merged

fjlopez merged 1 commit into
devfrom
fix/138-windows-setup-secrets

Conversation

@fjlopez

@fjlopez fjlopez commented Nov 1, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • setup.sh and setup.ps1 append SITMUN_USER_SECRET, MIDDLEWARE_SECRET, and SITMUN_MBTILES_JOB_HANDLE_SECRET when .env already exists and a key is absent. An existing value is kept.
  • The install docs and profile templates no longer tell Windows to run openssl. Copy the profile, then run ./setup.ps1 (or ./setup.sh on Unix).

Fixes #138

Test plan

  • bash tools/tests/test_setup_compose_secrets.sh (copied profile gets three 64-hex secrets, an existing value is kept, a missing .env is still created from the development PostgreSQL profile, README and profile templates no longer mention openssl rand)
  • setup.ps1 was not executed in this environment (no PowerShell). The script change matches the shell path: the three Add-ComposeSecretIfMissing calls run after the missing-file copy.
  • Compose secrets workflow runs the new test on the PR

Windows PowerShell has no openssl, and the install docs told operators
to append the three secrets with bash openssl after copying a profile.
setup.sh and setup.ps1 now fill any missing key on an existing .env.

Fixes #138
@fjlopez
fjlopez merged commit 5786447 into dev Nov 1, 2026
8 checks passed
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