RAILWAY_PUBLIC_DOMAIN service propagation
therobotcarlson
PROOP

3 months ago

When I update the public domain for a service, is there a way to force an update on all services relying on the RAILWAY_PUBLIC_DOMAIN var? I've been playing a game of whack-a-mole trying to redeploy every service relying on the vars for services I changed so they get the new values. It's pretty bad when updating domains for all services at once

5 Replies

3 months ago

Do you mean force a rebuild (without cache)?


therobotcarlson
PROOP

3 months ago

Rebuild / redeploy yes. For the frontend apps that bake in URLs, a full rebuild is necessary. For the backends it needs a redeploy at the very least.


3 months ago

Railway doesn't support cacheless redeploys (yet) (#A way to deploy without cache one-time)

What you can do is, add ARG RAILWAY_PUBLIC_DOMAIN to your Dockerfile(s), this'll cause a cache miss forcing a rebuild


therobotcarlson
PROOP

3 months ago

I'm not sure the cache is fully the problem. Even just a regular redeploy once the referenced RAILWAY_PUBLIC_DOMAIN changes would suffice. To clarify this is one service referencing the RAILWAY_PUBLIC_DOMAIN of another service. Like the frontend service referencing ${{backend.RAILWAY_PUBLIC_DOMAIN}}


3 months ago

Oh right, I misinterpreted the issue. No, I don't think Railway supports that at the moment

You could perhaps create a #🤗|feedback, and see where that goes


Welcome!

Sign in to your Railway account to join the conversation.

Loading...