Claude Fable 5
f0a82bad20
Some checks failed
CD / Build and push images (push) Successful in 3m16s
CI / Lint, typecheck, test (push) Successful in 3m5s
CD / Deploy to Test (push) Successful in 13s
CD / Smoke tests against Test (push) Failing after 3m35s
CD / Promote to Int (push) Has been skipped
CI / Auth e2e pack (push) Successful in 5m6s
CI / Import/export fidelity gate (push) Successful in 43s
CI / Build container images (push) Has been skipped
When the api runs against a database without the setup.completedAt marker, a global SetupGuard answers every non-exempt route with 503 setup_required; only /setup/*, health probes, and the session routes stay reachable. The wizard steps (POST /setup/admin|instance|smtp| registration|complete) write straight to their production homes; the Site Admin step signs its creator in, later steps require that session. Completing sets the marker and locks every step permanently (410, also across restarts, and not reopenable via PATCH /admin/settings). SMTP entered in the wizard is verified with a live delivery test first (failure blocks the step with the transport error as detail) and then persisted to the new env-backed secret store: a mode-600 dotenv file on the new `secrets` volume (SECRETS_FILE). Explicit container env always wins over the store; empty compose-passed strings count as unset. The mail transport now resolves lazily through SmtpConfigService so wizard changes apply without a restart. SETUP_ADMIN_* env pre-seeds the whole wizard at boot for automated deploys; a backfill migration marks instances that already have a Site Admin as completed, and seed/vitest global-setup do the same for fixture databases. The setup e2e suite provisions its own fresh database (CREATE DATABASE + migrate deploy) per run. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EwZ4jR4KFAPvpjWevfUGX1
26 lines
1.0 KiB
JSON
26 lines
1.0 KiB
JSON
{
|
|
"common": {
|
|
"greeting": "Hello {{displayName}},",
|
|
"signoff": "Your Dorfteich",
|
|
"ignoreHint": "If you did not request this e-mail, you can safely ignore it."
|
|
},
|
|
"verifyEmail": {
|
|
"subject": "Confirm your e-mail address",
|
|
"body": "welcome to Dorfteich! Please confirm your e-mail address to activate your account:",
|
|
"action": "Confirm e-mail address",
|
|
"expiry": "The link is valid for 24 hours."
|
|
},
|
|
"resetPassword": {
|
|
"subject": "Reset your password",
|
|
"body": "someone (hopefully you) requested a password reset for your account. Use this link to set a new password:",
|
|
"action": "Set new password",
|
|
"expiry": "The link is valid for one hour. Your current password stays valid until you set a new one."
|
|
},
|
|
"smtpTest": {
|
|
"subject": "SMTP test message",
|
|
"body": "this test message confirms that your Dorfteich can send e-mail through the configured SMTP server. You can reach your instance here:",
|
|
"action": "Open Dorfteich",
|
|
"expiry": "You can simply delete this e-mail."
|
|
}
|
|
}
|