From e764a1ed529ae762b156a1489f86803eb638d35a Mon Sep 17 00:00:00 2001 From: "Jakub A. W" Date: Thu, 16 Jul 2026 18:41:29 +0200 Subject: [PATCH] chore(deploy): add railway.json build and deploy config Railway templates are composed in the dashboard, but a service deployed from this repo reads railway.json for its build and deploy settings. Without it, Railway autodetects the builder and runs no healthcheck, so a deploy is marked live as soon as the container starts rather than when the gateway can actually serve. Pins the Dockerfile builder and points the healthcheck at /health/ready, which probes storage and the Redis cache but deliberately excludes upstream provider reachability, so a provider outage cannot fail a deploy or pull a healthy instance out of rotation. Restarts are ON_FAILURE so a clean exit is not restart-looped. Co-Authored-By: Claude Opus 4.8 (1M context) --- railway.json | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 railway.json diff --git a/railway.json b/railway.json new file mode 100644 index 00000000..d2e115b0 --- /dev/null +++ b/railway.json @@ -0,0 +1,12 @@ +{ + "$schema": "https://railway.com/railway.schema.json", + "build": { + "builder": "DOCKERFILE", + "dockerfilePath": "Dockerfile" + }, + "deploy": { + "healthcheckPath": "/health/ready", + "restartPolicyType": "ON_FAILURE", + "restartPolicyMaxRetries": 10 + } +}