fix: add Railway healthcheck + Dockerfile-naming warning (post-incident) - #54
Merged
Merged
Conversation
Follow-up to the 2026-09-09/10 production outage (PR #51 -> #53): two defensive measures so this class of failure can't silently recur. 1. railway.json: point deploy.healthcheckPath at the existing (already built, already unauthenticated) /health endpoint in backend/main.py, with a 300s timeout generous enough for litestream restore to finish. With this configured, a future deploy that builds successfully but never actually starts serving traffic will be caught by Railway and the last good deployment kept live, instead of silently going dark the way this incident did (Completed status, 0% CPU/memory, every request timing out at Railway's 15s gateway limit, for 20+ hours before anyone noticed). 2. nixpacks.toml: a prominent warning comment explaining that Railway auto-detects and prioritizes any repo-root file literally named "Dockerfile" over the "builder": "NIXPACKS" setting in railway.json (confirmed via Railway's own docs) -- which is exactly what caused the outage when PR #51 added one for an unrelated reason (Glama.ai MCP listing verification).
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to the 2026-09-09/10 production outage (PR #51 -> #53): two defensive measures so this class of failure can't silently recur.
railway.json: point deploy.healthcheckPath at the existing (already built, already unauthenticated) /health endpoint in backend/main.py, with a 300s timeout generous enough for litestream restore to finish. With this configured, a future deploy that builds successfully but never actually starts serving traffic will be caught by Railway and the last good deployment kept live, instead of silently going dark the way this incident did (Completed status, 0% CPU/memory, every request timing out at Railway's 15s gateway limit, for 20+ hours before anyone noticed).
nixpacks.toml: a prominent warning comment explaining that Railway auto-detects and prioritizes any repo-root file literally named "Dockerfile" over the "builder": "NIXPACKS" setting in railway.json (confirmed via Railway's own docs) -- which is exactly what caused the outage when PR build: add Dockerfile for Glama MCP server verification #51 added one for an unrelated reason (Glama.ai MCP listing verification).