https://sonarly.com/issue/41408?type=bug
Fresh self-host installs can fail during bootstrap because Docker marks `server` unhealthy before initialization completes, even though Nest eventually starts successfully.
Fix: Implemented a startup-tolerance fix in the self-host docker compose path by increasing the server healthcheck grace budget where the failure occurs.
Changes made:
- Updated `server` healthcheck in `packages/twenty-docker/docker-compose.yml`:
- added `start_period: 90s`
- increased `retries` from `20` to `24`
Why:
- Fresh installs can take longer during first bootstrap (migrations/init/registration). Adding a start period plus additional retries prevents Docker from marking the container unhealthy before the app is actually ready. This targets the exact failure mode (`server` unhealthy during first boot) in the right layer (docker compose runtime health policy).
Authored by Sonarly by autonomous analysis (run 47223).
sonarly-bot
fb5e6b1021