fix: increase backend start_period to 120s for migrations
Some checks failed
Deploy to Staging / Build Images (push) Successful in 30s
Deploy to Staging / Verify Staging (push) Has been cancelled
Deploy to Staging / Deploy to Staging (push) Has been cancelled
Deploy to Staging / Notify Staging Ready (push) Has been cancelled
Deploy to Staging / Notify Staging Failure (push) Has been cancelled

The 60s start_period was too short - migrations can take 70+ seconds.
Docker was marking the container unhealthy before migrations completed.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Eric Gullickson
2026-02-03 21:19:48 -06:00
parent 26196d34ea
commit 83224cf207
2 changed files with 3 additions and 3 deletions

View File

@@ -92,7 +92,7 @@ services:
interval: 5s interval: 5s
timeout: 5s timeout: 5s
retries: 5 retries: 5
start_period: 60s start_period: 120s
deploy: deploy:
resources: resources:
limits: limits:
@@ -183,7 +183,7 @@ services:
interval: 5s interval: 5s
timeout: 5s timeout: 5s
retries: 5 retries: 5
start_period: 60s start_period: 120s
deploy: deploy:
resources: resources:
limits: limits:

View File

@@ -151,7 +151,7 @@ services:
interval: 5s interval: 5s
timeout: 5s timeout: 5s
retries: 5 retries: 5
start_period: 60s start_period: 120s
labels: labels:
- "traefik.enable=true" - "traefik.enable=true"
- "traefik.docker.network=motovaultpro_backend" - "traefik.docker.network=motovaultpro_backend"