21 days ago
I have a railway.toml committed to my repository. Testing confirms
the file has no effect — Railway dashboard settings take precedence
and the file is silently ignored.
I also found that railway config was removed from the CLI in v5.49.2
and that railway.toml support ends December 2026.
Questions:
-
What is the correct replacement for declaring service configuration
as code?
-
Is there a migration guide from railway.toml to the replacement?
-
Will Railway notify users before the December 2026 EOL, or do I
need to act before then without a reminder?
1 Replies
21 days ago
The replacement is Infrastructure as Code (.railway/railway.ts, with Python and Go in beta), which is project-scoped rather than per-service. A full migration guide with CLI commands is at docs.railway.com/infrastructure-as-code#migrating-from-config-as-code, and the quickest path is railway config migrate --apply. One important note: as of 2026-08-28, new services can no longer opt into Config as Code, which would explain why your railway.toml is being ignored if the service was created after that date. Existing Config as Code files stop being read entirely on 2026-12-01. When migrating, migrate all services in the environment together rather than one at a time to avoid locking the environment into named-partials mode.
Status changed to Awaiting User Response Railway • 21 days ago
14 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 14 days ago