blumeops/fly
Erich Blume b667f21e10 Fix 502 errors during Fly.io proxy deploys
The health check returned 200 immediately on nginx start, before
Tailscale connected. Fly.io routed traffic to the new machine with
a cold proxy cache and no MagicDNS, causing upstream DNS timeouts.

Defer the health check by returning 503 until a sentinel file
(/tmp/tailscale-ready) is created after Tailscale connects. This
keeps the old machine serving traffic during the startup window.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-09 11:06:41 -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 2026-02-09 11:06:41 -08:00
start.sh Fix 502 errors during Fly.io proxy deploys 2026-02-09 11:06:41 -08:00