Configure Railway to deploy every push to a repo by going to Deployments > Triggers in your project. Here you can select a GitHub repo and branch to deploy from. If you have more than 1 Railway environment, you can select which environment to use.
It is possible to create multiple triggers. With this workflow you can connect to your repo and
- Deploy main using the production environment
- Deploy staging using the staging environment
Project tokens can be used in environments where you cannot login (e.g. remote servers or CI). You can create project tokens for a specific Railway environment on the project page.
Project tokens allow the CLI to access all the environment variables associated
with a specific project and environment. Use the token by setting the
RAILWAY_TOKEN environment variable and then running
Under Project Settings > Integrations in your project dashboard, you can connect to your Vercel account, specify a team, project, and production/preview environments. We will then provide your production and preview deploys on Vercel with all the environment variables needed to connect to your Railway environments.
This allows you to keep production and preview deploy databases separate.
We are working on adding more integrations to various serverless platforms.
However, if you want to use Railway for a platform we do not support, you can
manually add the environment variables for each plugin (e.g. the
for the Postgres plugin).
Self Hosted Server
You can deploy to a separate server (e.g. AWS, GCP, DigitalOcean) and still
connect to your Railway plugins. On the server, you can either login to the CLI
railway login or use a project token. Then prefix the
server start command with
Edit this file on GitHub