18 days ago
For an existing service with a staged Custom Start Command change, how can I deploy new source via railway up and that command together in exactly one deployment, without first redeploying the old image? My CLI exposes no staged-change option, and environmentPatchCommit exposes no deployment-suppression argument. Alt-click previously resulted in a container start. Please confirm a supported procedure, or whether this is unsupported.
1 Replies
18 days ago
Commit the staged start command without triggering a deploy first, then run railway up. In the dashboard, hold Alt and click the Deploy button (or press Alt+Shift+Enter) to commit the staged change without redeploying. Alternatively, call environmentPatchCommitStaged via the API. Either way, the config is committed but no deployment fires. The subsequent railway up then creates a single deployment that uses the new source together with the already-committed start command.
Status changed to Awaiting User Response Railway • 18 days ago
10 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 • 10 days ago