Skip to content

chore(railway): expose readiness diagnostics #50

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Coding-Dev-Tools merged 1 commit into from
Jul 22, 2026
+1 −1
Merged

chore(railway): expose readiness diagnostics #50

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion railway.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@
"dockerfilePath": "Dockerfile"
},
"deploy": {
"healthcheckPath": "/api/ready",
"healthcheckPath": "/api/health",

@chatgpt-codex-connector chatgpt-codex-connector Bot Jul 22, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Restore readiness as the Railway health check

When the customer database or embedder cannot initialize, /api/health still returns 200 unconditionally, while /api/ready returns 503 until both dependencies are usable. Pointing Railway at this liveness endpoint therefore lets a broken deployment be marked healthy and receive traffic, despite the Docker health check and hosted deployment guidance continuing to require /api/ready.

Useful? React with 👍 / 👎.

"healthcheckTimeout": 300,
"restartPolicyType": "ON_FAILURE",
"restartPolicyMaxRetries": 10
Expand Down