Health Check Verification

Showing 3 of 5

1. 1 Wait for deployment to complete

   Poll compose status until the deployment reaches idle or running state, with a maximum timeout of 120 seconds

   # Poll deployment status (max 120s)
   for i in $(seq 1 24); do
     STATUS=$(curl -s https://dokploy.shredbx.com/api/compose.one?composeId=<id> \
       -H "Authorization: Bearer $DOKPLOY_TOKEN" | jq -r '.composeStatus')
     if [ "$STATUS" = "idle" ] || [ "$STATUS" = "running" ]; then
       echo "Deployment complete: $STATUS"
       break
     fi
     sleep 5
   done

2. 2 Check container status

   Verify all compose services show 'running' status with no restart loops or crash backoffs

   # List all containers for the compose project
   docker compose -f docker-compose.prod.yml ps --format json
   # All services should show State: "running"
   # Restart count should be 0

3. 3 Hit health endpoints

   Curl /health on each service at their registered ports to confirm application-level readiness

   # API health check
   curl -sf https://api.shredbx.com/health || echo "FAIL: API unhealthy"
   
   # Web health check
   curl -sf https://shredbx.com/ -o /dev/null || echo "FAIL: Web unreachable"
   
   # Internal service health (via Docker network)
   docker exec sbx-api curl -sf http://localhost:5100/health

• Dokploy API
• docker compose
• curl