#21: raise the development secrets to the length the guard now requires

The auth service refuses to start with a JWT_SECRET under 32 characters,
which is the point - but .env.example still carried a 30-character value,
so the stack could not come up with the file it ships with. CI caught it
on the compose-up job: auth reported unhealthy and everything depending
on it stopped.

Reproduced locally against the same file before and after; the stack now
starts from a clean checkout.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Lucas RayanandClaude Opus 5 committed 2026-08-02 13:56:40 -03:00
1 parent 9062c14d70
commit 7a4ca10a39
1 file changed
+2 -2
+2 -2
View File
@@ -16,10 +16,10 @@ POSTGRES_PASSWORD=change-me-in-local-dev
REDIS_PASSWORD=change-me-in-local-dev REDIS_PASSWORD=change-me-in-local-dev
# --- Shared secrets (local dev values — never reuse in production) --- # --- Shared secrets (local dev values — never reuse in production) ---
JWT_SECRET=local-dev-jwt-secret-change-me JWT_SECRET=local-dev-jwt-secret-change-me-at-least-32-chars
# Encrypts DKIM private keys and provider tokens at rest. Losing it makes every # Encrypts DKIM private keys and provider tokens at rest. Losing it makes every
# stored secret unrecoverable — back it up separately from the database. # stored secret unrecoverable — back it up separately from the database.
LAMBDAMAIL_MASTER_KEY=local-dev-master-key-32-bytes-min LAMBDAMAIL_MASTER_KEY=local-dev-master-key-32-bytes-minimum-value
# --- Host identity --- # --- Host identity ---
PRIMARY_MAIL_HOST=mail.localhost PRIMARY_MAIL_HOST=mail.localhost