fix: add DB wait-for-ready logic and explicit network names
Some checks failed
Dev Deployment (Zero Downtime) / deploy-dev (push) Failing after 9m24s
Some checks failed
Dev Deployment (Zero Downtime) / deploy-dev (push) Failing after 9m24s
- 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>
This commit is contained in:
@@ -113,6 +113,7 @@ volumes:
|
||||
|
||||
networks:
|
||||
portfolio_net:
|
||||
name: portfolio_net
|
||||
driver: bridge
|
||||
proxy:
|
||||
external: true
|
||||
|
||||
Reference in New Issue
Block a user