gnezim e80eeb69e0
ci-deploy / build-deploy-test (push) Successful in 1m11s
deploy-container: wait for SSR readiness before returning from swap
Run 549's wait-for-health logged two HTTP 502s before its third
attempt succeeded — nginx → docker forwarding hit the new container
during the ~4s window between \`docker run -d\` returning and
Node.js inside finishing its boot. The retry loop covered it but the
log was noisy and a slower boot could blow past the 30×2s budget.

Added a post-run readiness probe inside swap: poll
http://127.0.0.1:${PORT}/ on the host (docker container is published
to 127.0.0.1, runner uses host network mode) until it answers 2xx,
up to 30 attempts × 1s. Skipped under --dry-run so the tests/ci/
shell tests still pass without touching the network.

Net effect: wait-for-url against the public URL now succeeds first
attempt, and the run aborts cleanly if the SSR doesn't come up at
all instead of looking healthy because nginx happens to keep a
warmed connection.
2026-04-28 14:44:12 +03:00
S
Description
No description provided
6.7 GiB
Languages
TypeScript 62.7%
HTML 23.6%
SCSS 11%
JavaScript 1.1%
C# 0.9%
Other 0.6%