blumeops/fly
Erich Blume bd61da4f85
All checks were successful
Deploy Fly.io Proxy / deploy (push) Successful in 1m20s
Fix 502 errors during Fly.io proxy deploys (#131)
## Summary
- Health check (`/healthz`) now returns 503 until Tailscale is connected
- `start.sh` creates `/tmp/tailscale-ready` sentinel after `tailscale up` succeeds
- Fly.io keeps the old machine serving traffic during the ~7s startup window

Previously, nginx passed the health check immediately, Fly.io routed traffic to the new machine, but MagicDNS wasn't available yet — causing upstream DNS timeouts and 502s on every request until Tailscale connected.

## Deployment and Testing
- [ ] Merge and `fly deploy` from `fly/` directory
- [ ] Verify deploy completes with zero 502s (check Grafana docs-apm dashboard)
- [ ] Confirm health check transitions from 503 → 200 in `fly logs`

Reviewed-on: https://forge.ops.eblu.me/eblume/blumeops/pulls/131
2026-02-09 11:07:36 -08:00
..
alloy.river Log real client IPs via Fly-Client-IP header (#130) 2026-02-09 11:02:06 -08:00
Dockerfile Add Fly.io proxy observability via embedded Alloy (#123) 2026-02-08 10:05:38 -08:00
fly.toml Add Fly.io public reverse proxy for docs.eblu.me (#120) 2026-02-08 02:36:19 -08:00
nginx.conf Fix 502 errors during Fly.io proxy deploys (#131) 2026-02-09 11:07:36 -08:00
start.sh Fix 502 errors during Fly.io proxy deploys (#131) 2026-02-09 11:07:36 -08:00