blumeops/fly
Erich Blume f6febb1f77
All checks were successful
Deploy Fly.io Proxy / deploy (push) Successful in 34s
C0: switch fly proxy deploy strategy to immediate
Bluegreen kept timing out — the new green machine couldn't reach
"started" within Fly's 5-minute deploy budget. The cold-start sequence
(tailscaled → tailscale up → wait-for-MagicDNS → nginx startup) eats
most of that, leaving no headroom for healthcheck propagation.

For a single-machine proxy, bluegreen offers little benefit anyway:
no warm second instance, so trading 5-10s of downtime for predictable
completion is the right call.
2026-05-28 07:59:22 -07:00
..
fail2ban C1: deploy adelaide-baby-shower-app to ringtail k3s (#349) 2026-05-11 13:47:18 -07:00
alloy.river Add Forgejo metrics + upstream latency histogram to Fly proxy dashboard 2026-04-17 15:05:59 -07:00
Dockerfile Recurring maintenance batch (2026-05-27) (#360) 2026-05-28 06:01:57 -07:00
error.html
fly.toml C0: switch fly proxy deploy strategy to immediate 2026-05-28 07:59:22 -07:00
nginx.conf C1: deploy adelaide-baby-shower-app to ringtail k3s (#349) 2026-05-11 13:47:18 -07:00
start.sh C1: deploy adelaide-baby-shower-app to ringtail k3s (#349) 2026-05-11 13:47:18 -07:00