fix(docker): 120 s de marge au healthcheck de l'API au premier lancement

Les migrations Prisma passent avant que l'API réponde. Avec 30 s, le conteneur
web, qui attend une API saine, abandonnait au premier docker compose up
(signalé sur r/GenealogieFR le 11/10).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

CHANGELOG.md

@@ -16,6 +16,7 @@ Notable changes to Parenthèse. Dates are in YYYY-MM-DD format.
 
 ### Fixes
 
+- Docker: on a first `docker compose up`, the API now gets 120 s to run its migrations before its health check counts (was 30 s). The web container waits for a healthy API and used to give up, so it had to be started again by hand.
 - Children of a family with only one known parent (common in GEDCOM files) are linked to that parent, under a single "Unknown" partner, instead of floating in the tree without a link.
 - Importing a GEDCOM file into a tree that already holds it no longer duplicates everyone: people with the same first name, last name, birth and death dates are reused, and existing unions and parent links are kept.
 

docker-compose.yml

@@ -50,7 +50,9 @@ services:
       interval: 15s
       timeout: 5s
       retries: 5
-      start_period: 30s
+      # Premier lancement : les migrations passent avant que l'API réponde, 30 s ne suffisaient pas
+      # et le conteneur web, qui attend une API prête, abandonnait (signalé sur Reddit le 11/10).
+      start_period: 120s
 
   web:
     image: ghcr.io/iliesallali/parenthese-web:${PARENTHESE_VERSION:-latest}