nexxo b85c12e8b9 Give the readiness probe long enough for a restart to finish ... The gateway is restarted twice in a deployment — once by `up -d`, then again after the hub whose network namespace it lives in — and `docker compose exec` into a container that is still coming up fails outright rather than waiting. Twenty seconds did not cover that, so the first run of the new probe reported a gateway that answers as down, and the resolver stayed out of client configs for one more deployment. The health site also now binds the hub address instead of only matching on it. Nothing was published either way, but the file should do what its comment says. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>		2026-07-27 14:46:47 +02:00
..
caddy	Make the private hostnames look like nothing is there, and close the way past the proxy	2026-07-27 11:26:48 +02:00
lib	feat(deploy): releases you can pin to, and a version that tells the truth	2026-07-26 15:21:38 +02:00
clupilot.env.example	fix(deploy): an answer file with a space in a value killed the install	2026-07-26 18:49:58 +02:00
install-agent.sh	Serve the console inside the tunnel, without publishing the internal network	2026-07-27 10:14:33 +02:00
install.sh	Give the status page its own hostname, and name the right one for Stripe	2026-07-27 08:08:57 +02:00
update-agent.sh	Ask the tunnel gateway where it actually listens	2026-07-27 14:43:23 +02:00
update.sh	Give the readiness probe long enough for a restart to finish	2026-07-27 14:46:47 +02:00