Deploy to different Railway environments based on GitHub Releases/Tag
Anonymous
PROOP

a month ago

Hi,

I’m using Railway with two environments: staging and prod.

My goal is:

  • Auto-deploy to perf on every merge to main

  • Deploy to prodonly when a GitHub Release is created (i.e. by tag / release)

This is similar to how some platforms let you deploy by release/tag instead of a branch.

Questions:

  1. Does Railway natively support triggering deployments by GitHub Releases or tags, not just branches?

  2. If not, is the recommended approach to:

    • disable autodeploy on prod, and

    • deploy prod via Railway CLI from GitHub Actions on release.published?

  3. Is there any built-in “promotion” concept between environments (perf → prod) using the same commit SHA?

Thanks!

Solved$10 Bounty

Pinned Solution

0x5b62656e5d
FREETop 1% Contributor

a month ago

I'm not sure if Railway supports triggers via releases or tags.

However, yes, I'd just run CICD pipelines with Github Actions when a release is published.

1 Replies

0x5b62656e5d
FREETop 1% Contributor

a month ago

I'm not sure if Railway supports triggers via releases or tags.

However, yes, I'd just run CICD pipelines with Github Actions when a release is published.

Status changed to Solved ray-chen • about 1 month ago

Loading...