Environment Variables

Railway provides the following additional system environment variables to all builds and deployments.

NameDescription
RAILWAY_STATIC_URLThe public domain, of the form example.up.railway.app
RAILWAY_GIT_COMMIT_SHAThe git SHA of the commit that triggered the deployment. Example: d0beb8f5c55b36df7d674d55965a23b8d54ad69b
RAILWAY_GIT_AUTHORThe user of the commit that triggered the deployment. Example gschier
RAILWAY_GIT_BRANCHThe branch that triggered the deployment. Example main
RAILWAY_GIT_REPO_NAMEThe name of the repository that triggered the deployment. Example myproject
RAILWAY_GIT_REPO_OWNERThe name of the repository owner that triggered the deployment. Example mycompany
RAILWAY_GIT_COMMIT_MESSAGEThe message of the commit that triggered the deployment. Example Fixed a few bugs

Templated Variables

Variables can reference other variables using the ${{ MY_VAR }} templating syntax. This can help reduce duplication if you need the same value in more than one variable, or need to present a plugin-provided variable differently.

Note: The above RAILWAY_* variables aren't yet supported in templates

Construct "Meta" Variables

If you find yourself needing the same value in more than one place, you can create a template to avoid duplication. The following example constructs a URL from an AWS S3 configuration:

"Rename" Plugin Variables

Railway plugins provide a fixed set of variables. If your application requires a variable to be under different name, create a new custom variable that uses a template to reference the original:


Edit this file on GitHub