Repository navigation
chore(railway): migrate from railway.toml to railway.ts - #288
Anmol-Baranwal wants to merge 5 commits into
Conversation
Railway stops reading railway.toml files on Dec 1, 2026. Add .railway/railway.ts with the same build and deploy settings for all 8 Outpost services, plus the railway SDK it needs.
Settings now live in .railway/railway.ts. Update the deployment docs and the release bot README to match.
|
Hey @Anmol-Baranwal, thanks for getting ahead of the Railway change. Every service keeps the same Dockerfile, restart policy and health check as its old There's one thing I'd like to sort out before this lands, and it's in the docs rather than the config. The Railway section in A short note next to those steps would cover it. It could say the file is set up for CopilotKit's project, and that a fork needs to change the repo name and fill in its own environments and variables before applying. If you'd rather keep the old per-service file approach documented for self-hosters instead, that works for me too. One more thing. The description says to keep this as a draft until the Railway variables are copied in, but it's currently open as a regular PR. Could you switch it to a draft so nobody merges it early by accident? Once the cutover steps are done I'm happy to pair on the plan check if that helps. |
Railway stops reading
railway.tomlfiles on Dec 1, 2026. This moves all 8 Outpost services to.railway/railway.ts, Railway's new config format, and removes the oldrailway.tomlfiles.What's in it
main, staging fromstagingrailway.tsSafety
Before merging (needs Railway access)
Keep this as a draft until then. The services still read the old files, so merging early breaks their next deploy.
railway config pullfor staging and production, and copy the variables into.railway/railway.tsrailway config planand check it removes nothingrailway config applyFull steps are at the top of
.railway/railway.ts.