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	Give the readiness probe long enough for a restart to finish	2026-07-27 14:46:47 +02:00
kuma-bridge	fix(monitoring): cap monitoring retries at the run budget; dependency-free liveness probe	2026-07-25 20:19:32 +02:00
nginx	fix(nginx): the live hostnames were missing from the admin denylist	2026-07-26 18:43:44 +02:00
php	fix(engine): install wireguard-tools + bring up wg0; lock-coordinate host removal	2026-07-25 10:57:51 +02:00
supervisor	fix(ui): make modal cancel buttons work; serve the app over the HTTPS domains	2026-07-25 21:24:03 +02:00
entrypoint.sh	fix(docker): build assets on start when the manifest is missing	2026-07-25 21:45:27 +02:00