Docker Compose .env Changes Need Container Recreation
Editing .env on a running container does nothing — Compose reads it once at start. And $ in a secret gets interpolated away, silently truncating tokens.
Editing .env on a running container does nothing — Compose reads it once at start. And $ in a secret gets interpolated away, silently truncating tokens.
A calendar-sync bridge dropped connections under load with 'connection closed unexpectedly'. Four bridge tweaks later, the durable fix was async-ack plus onError handling in the client.
Editing workflow JSON directly in SQLite leaves a stale activeVersionId and produces the 'all-green, nothing happens' ghost. The CLI import + publish path is the correct deploy.