docs(ops): name the crash loop the cutover runbook was most likely to cause (#175) #191

2026-08-26T08:41:17-05:00

bermudalamb commented

2026-08-26 08:41:17 -05:00

Step 7 listed a missing ADMIN_GATE_SECRET — a warning the container starts through — and said nothing about the three PayPal secrets, which are a hard error that crash-loops it. That is backwards: the secrets are the likeliest thing to be missing after a stack replacement, because Portainer stack variables belong to the stack and are discarded with it, and DEMO_MODE is false in production so the app refuses to start without them. Hit for real following the runbook.

The verify section now shows the actual log block, says what it means, and gives the way to tell a missing variable from a misnamed one: a hardcoded value cannot be missing, so its absence from the error list proves nothing, while an interpolated variable that stays quiet while others complain proves substitution works and those others are simply unset. That is the reading that turns the log into a diagnosis instead of a list.

It also says the loop is harmless while the values are fetched — the container refuses before it serves anything or touches data — and where the values live if the old stack is already gone, since the webhook id in particular is readable rather than only recreatable.

Step 2 now names every interpolated variable rather than describing them in general, and states the consequence of each class going missing. A general instruction to record the environment is easy to read as already done.

Step 7 listed a missing `ADMIN_GATE_SECRET` — a warning the container starts through — and said nothing about the three PayPal secrets, which are a hard error that crash-loops it. That is backwards: the secrets are the likeliest thing to be missing after a stack replacement, because Portainer stack variables belong to the stack and are discarded with it, and `DEMO_MODE` is false in production so the app refuses to start without them. Hit for real following the runbook. The verify section now shows the actual log block, says what it means, and gives the way to tell a missing variable from a misnamed one: a hardcoded value cannot be missing, so its absence from the error list proves nothing, while an interpolated variable that stays quiet while others complain proves substitution works and those others are simply unset. That is the reading that turns the log into a diagnosis instead of a list. It also says the loop is harmless while the values are fetched — the container refuses before it serves anything or touches data — and where the values live if the old stack is already gone, since the webhook id in particular is readable rather than only recreatable. Step 2 now names every interpolated variable rather than describing them in general, and states the consequence of each class going missing. A general instruction to record the environment is easy to read as already done.

bermudalamb self-assigned this 2026-08-26 08:41:17 -05:00

bermudalamb added this to the Code Quality and Hardening 2 project 2026-08-26 08:41:17 -05:00

bermudalamb added 1 commit 2026-08-26 08:41:17 -05:00

docs(ops): name the crash loop the cutover runbook was most likely to cause (#175 )

SonarQube Analysis / sonarqube (pull_request) Failing after 27m56s

Details

Linting / lint (pull_request) Successful in 3m7s

Details

0cec9b3c1f

Step 7 listed a missing `ADMIN_GATE_SECRET` — a warning the container starts through — and said nothing about the three PayPal secrets, which are a hard error that crash-loops it. That is backwards: the secrets are the likeliest thing to be missing after a stack replacement, because Portainer stack variables belong to the stack and are discarded with it, and `DEMO_MODE` is false in production so the app refuses to start without them. Hit for real following the runbook.

The verify section now shows the actual log block, says what it means, and gives the way to tell a missing variable from a misnamed one: a hardcoded value cannot be missing, so its absence from the error list proves nothing, while an interpolated variable that stays quiet while others complain proves substitution works and those others are simply unset. That is the reading that turns the log into a diagnosis instead of a list.

It also says the loop is harmless while the values are fetched — the container refuses before it serves anything or touches data — and where the values live if the old stack is already gone, since the webhook id in particular is readable rather than only recreatable.

Step 2 now names every interpolated variable rather than describing them in general, and states the consequence of each class going missing. A general instruction to record the environment is easy to read as already done.

bermudalamb merged commit 5f21d97178 into main

2026-08-26 08:41:27 -05:00

bermudalamb deleted branch feature/190-cutover-runbook-secrets

2026-08-26 08:41:27 -05:00

bermudalamb referenced this issue from a commit

2026-08-26 09:17:30 -05:00

feat(ops): put production in demo mode to complete the cutover (#191)

bermudalamb referenced this issue from a commit

2026-08-26 09:17:30 -05:00

docs(ops): point the demo-mode notes at the right issue (#190)

bermudalamb referenced this pull request

2026-08-27 11:07:29 -05:00