Overview - Ghost

Ghost

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
28991
b1de7f0c Split ghost-dev healthcheck into boot vs steady-state cadence The retries:300 approach kept probing every second indefinitely — fine for cold-boot detection but noisy in steady state. start_interval/interval gives both behaviors: 1Hz probing during the 120s start_period for fast compose --wait clearance, then 30s interval once healthy. Tolerance: start_period 120s of grace + retries:3 × interval:30s = 210s before unhealthy. Covers cold boots well past the 60-90s the team sees on bigger workspaces.
by Steve Larson
Succeeded
28991
55616776 Bumped ghost-dev healthcheck retries to 300 retries:50 with interval:1s gave only ~55s of cold-boot tolerance. On slower hardware the backend takes 60-90s+ to start listening, so docker compose up --wait failed before backend was ready. retries:300 with interval:1s + start_period:5s = ~305s tolerance — matches the original (interval:30s × retries:10) so we never regress on slow hardware. We still keep the speedup because once the backend IS listening, probes fire every 1s and the gate clears in <1s.
by Steve Larson
Succeeded
28991
0434a0fe Loosened gateway depends_on ghost-dev to service_started The Caddy gateway came up fast (<1s) but was blocked behind ghost-dev's healthcheck via depends_on: service_healthy. Caddy retries its upstream on connect-refuse so the brief 502 window during ghost-dev boot is self-healing. compose up --wait now returns when the gateway is running, not when the backend is healthy. Composed with the healthcheck interval tightening, cold pnpm dev docker_up stage converges close to backend_log_ready.
by Steve Larson