Make prisma migrate deploy failure non-fatal in start-with-migrate.js.
Previously, migration failure caused process.exit() which killed the
container, triggering an infinite restart loop. Now logs a warning
and starts the Next.js server anyway (app has DB fallbacks).
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- start-with-migrate.js now waits for the database TCP port to be
reachable before running Prisma migrations (15 retries, 2s interval).
Prevents the container from crashing and restarting in a loop when
postgres is still starting up.
- Add explicit 'name:' to both production and dev compose networks
to prevent docker-compose project prefix mismatch.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
