Railway Provider

Deploy preview environments to Railway services.

How it works

• Build: Previewops creates a synthetic image tag pointing at the source commit. Railway builds from the repo's Dockerfile using its own infrastructure.
• Deploy: creates a Railway service within your project (or re-deploys for the same PR). Polls until deployment reaches SUCCESS status.
• Delete: deletes the Railway service.
• List: lists all services in the project that match the prev-{owner}-{repo} name prefix.

Prerequisites

1. A Railway account with an existing project and environment.
2. A Railway API token.

Step 1 — Create a Railway project

1. Go to railway.app → New Project.
2. Note the Project ID from the project's settings URL or the Settings → General panel.
3. Note the Environment ID (found in Settings → Environments → click environment → ID).

Step 2 — Get a Railway API token

1. Go to Account Settings → Tokens → Create Token.
2. Give it a descriptive name (e.g. previewops).
3. Copy the token and store it as RAILWAY_API_TOKEN in the Previewops secrets.

Step 3 — Configure the repo

provider: railway
providerConfig:
  projectId: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx     # required — Railway project UUID
  environmentId: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx # required — Railway environment UUID

Both IDs are UUIDs. You can find them in the Railway dashboard URL: https://railway.app/project/<projectId>/settings

Step 4 — Verify

Comment /validate-previewops on any open PR. The bot calls { me { id name } } against the Railway GraphQL API and reports the authenticated account name.

Troubleshooting