2 days ago
I have my Railway deploys happening through a Github Actions deploy (https://github.com/XIVAuth/XIVAuth/blob/main/.github/workflows/component.railway_deploy.yml), but this seems to come with a notable downside: I no longer have the environment variables like RAILWAY_GIT_COMMIT_SHA in my running services. Is there a way to restore this when using railway up or any other (controlled) CI flow?
I'm using a CI flow specifically so I can control and gate when a release happens, rather than just firing things off of any commit. I could swap over to a release branch, though I'd somewhat prefer not to if it can be reasonably avoided.
Or, an alternative way of asking this: is there a deploy command variant that states "deploy this repo at this commit hash"?
2 Replies
a day ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 1 day ago
a day ago
serviceInstanceDeployV2
2 hours ago
Via serviceInstanceDeployV2: https://github.com/XIVAuth/railway-deploy-tool/. Hacky and not great, but it works.
Status changed to Solved kazwolfe • about 2 hours ago