15 days ago
Project owner request for a staging environment. Nine unrelated variable changes are already pending and must not be applied or discarded. The connected branch head is commit 977fa1c0d4dafebe072f036211cba9feb4e4507e, but Railway marked it as no deployment needed because watched paths were not modified. The available deployment actions target the current older source. Separately, the web-platform service is blocked by the legacy region key sfo.
Please confirm the provider-supported workflow to:
- deploy the exact commit above for all five connected application services without applying or discarding the existing staged changes;
- move web-platform from legacy sfo to a currently supported US West region while preserving the same staging environment and resources; and
- keep the nine pending changes untouched.
No secrets or customer data are involved. Please advise whether Railway staff intervention is required.
2 Replies
15 days ago
When a commit is skipped due to watch paths, you can force a deploy from the latest commit on the connected branch by opening the Command Palette (Cmd/Ctrl+K) and selecting "Deploy Latest Commit" on each service. Staged changes are environment-scoped and completely independent of deployments, so they remain untouched. For the region, "sfo" is a legacy identifier; open the service settings for web-platform and select "US West Metal" (California, us-west2) from the region picker. Region changes take effect on the next deploy with no downtime (unless a volume is attached, which triggers a migration). No staff intervention is required for any of this.
Status changed to Awaiting User Response Railway • 15 days ago
15 days ago
Deploy Latest Commit worked: all five application deployments are now green at the exact branch head, and the original nine staged changes remain untouched. The remaining operation is to replace three production-shaped domains and synchronize only PUBLIC_BASE_URL (two web services) and CORE_API_URL (web-company). Adding those public values would join the existing environment-scoped staged set. Is there a provider-supported way to apply only selected new variables or only one service's newly staged changes while leaving the original nine staged changes untouched? We must not apply or discard those nine changes, and we will not rename the domains until the callback/runtime update can remain consistent.
Status changed to Awaiting Railway Response Railway • 15 days ago
15 days ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 15 days ago