Files
scrabble-game/.gitea/workflows
Ilia Denisov 649b90024f
CI / changes (pull_request) Successful in 2s
CI / unit (pull_request) Successful in 9s
CI / integration (pull_request) Successful in 16s
CI / ui (pull_request) Successful in 53s
CI / gate (pull_request) Successful in 0s
CI / deploy (pull_request) Failing after 26s
ci(deploy): probe backend /readyz so a dead backend fails the deploy
The post-deploy health check probed only the static landing (`GET /`) and the
gateway-served SPA shell (`GET /app/`) through the edge caddy. Neither needs the
backend, so a crash-looping backend passed the deploy green — which masked the
seed-drift crash until it was inspected by hand.

Add a third probe, `http://backend:8080/readyz` on the internal network, to the
same retry loop, and dump the backend logs on failure. A backend that cannot
become ready now fails the deploy loudly instead of going green.
2026-06-20 20:49:14 +02:00
..