Skip to content
Preserve railway.toml settings without redeployment before December 1
ytzhs2000
OP

3 days ago

Hi, is there a supported way to preserve a production service's railway.toml settings before December 1, 2026, without redeploying, adding charges, or affecting another environment?

The dashboard fields are read-only. The config migrate --apply docs differ from CLI 5.74.0 source, which separates local generation from cutover and warns that cutover/undo redeploy and may affect inheriting environments. Which behavior is current? If no no-deploy route exists, what happens to an already-running deployment after the cutoff?

Please advise only; do not change the account.

https://docs.railway.com/cli/config

https://github.com/railwayapp/cli/blob/7da7f0d4dd6061656ed0b001c193945887ee645a/src/commands/config/migrate.rs

Awaiting User Response

3 Replies

Railway
BOT

3 days ago

An already-running deployment is not stopped or failed at the December 1, 2026 cutoff. From that date we simply stop reading railway.toml, and the service's own settings take over. The risk is that anything set only in the file, such as a healthcheck, watch patterns or a pre-deploy command, stops applying unless those values also exist on the service.

The CLI is not required to preserve them. You can set the same values directly on the service through the public API's serviceInstanceUpdate mutation. It covers the common toml fields, including build and start commands, healthcheck, restart policy, replicas, region, cron and pre-deploy command. Service settings apply per environment, so you can scope the change to production.

We could not confirm whether that update, or the CLI's migrate and cutover steps in 5.74.0, triggers a redeploy or touches inheriting environments. If you need to rely on any of these routes, test them first in a separate non-production environment.

When you migrate to .railway/railway.ts, migrate every service in an environment together. Migrating only some of them locks that environment out of whole-project applies.


Status changed to Awaiting User Response Railway • 3 days ago


ytzhs2000
OP

3 days ago

We still need help with the original question. Can a Railway team member confirm a supported way to preserve these settings without a redeploy, extra charges, or effects on other environments? We cannot test a write in production. Please advise only; do not change the account.


Status changed to Awaiting Railway Response Railway • 3 days ago


Railway
BOT

3 days ago

We're not making any changes to your account. Two read-only steps can help you assess this against production without writing anything: railway config migrate without --apply only previews the generated .railway/railway.ts, and railway config plan only reads your environment's current state and lists the changes an apply would make. Neither one applies anything. A plan is ready to apply when it shows only the settings you deliberately moved over, with no deletes and no changes to unrelated services.

We can't provide staff or engineering confirmation that applying the change, through the CLI or a settings update, will avoid a redeploy or leave inheriting environments untouched. If you need to rely on that, the way to check it is in a separate non-production environment, not production.

From 2026-12-01, existing railway.toml files are no longer read.


Status changed to Awaiting User Response Railway • 3 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...