Matt 9a9a73dde2 fix(docker): query _prisma_migrations directly for failed-migration auto-resolve ...

The previous regex against `prisma migrate status` output silently drifted
out of sync with Prisma 6's wording, so today's failed migration on prod
was never auto-resolved — the container crash-looped and required a
manual DELETE on _prisma_migrations to recover.

Truth lives in the table: a row with `finished_at IS NULL AND
rolled_back_at IS NULL` is an unresolved failure. Query that directly via
the Prisma client (already shelled out for the user-count check below)
and loop until none remain (with a 5-iteration safety bound).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-07 17:10:44 +02:00

..

nginx

Add email password change feature and fix nginx config

2026-01-30 16:15:08 +01:00

.env.production

Fix S3/SMTP connectivity and add one-click invite flow

2026-01-31 14:13:16 +01:00

docker-compose.dev.yml

fix: batch 4 — connection pooling, graceful shutdown, email verification UX

2026-03-07 18:16:29 +01:00

docker-compose.yml

fix: batch 4 — connection pooling, graceful shutdown, email verification UX

2026-03-07 18:16:29 +01:00

docker-entrypoint.sh

fix(docker): query _prisma_migrations directly for failed-migration auto-resolve

2026-05-07 17:10:44 +02:00

Dockerfile

fix: batch 5 — input validation tightening + health check endpoint

2026-03-07 18:26:28 +01:00

Dockerfile.dev

Fix Docker build: add .npmrc for Tremor peer dep conflict

2026-02-20 21:56:26 +01:00