ayungavis/Railway Preview Deploy Action
Railway preview deployment GitHub Actions workflow for every pull request opened in your repository like a Vercel
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| railway_api_token | The Railway API token | yes | — |
| project_id | The Railway project ID, you can find it in the Railway dashboard > Settings > General page | yes | — |
| environment_name | The environment name to be base of the preview deployment | yes | — |
| environment_id | The environment ID to be base of the preview deployment. If it's provided, the `environment_name` will be ignored | no | — |
| preview_environment_name | The new environment name to be created for the preview deployment. E.g. `pr-<PR_NUMBER>-<SHORT_COMMIT_HASH>` | yes | — |
| environment_variables | The environment variables to be set in the preview deployment. Should be a JSON object of key value paris. E.g. {"DATABASE_URL": "test_url", "A": "abc", "D": "efg"} | no | — |
| api_service_name | The name of the API service to use for the PR environment. This is used to identify the domain of the deployed PR environment | no | — |
| ignore_service_redeploy | List of service name to ignore when redeploying the PR environment. This is useful for services that don't need to be redeployed on every PR | no | — |
| branch_name | The branch name of the PR to be used for the preview deployment | yes | — |
| reuse_preview_environment | Whether to reuse the existing preview environment if it's already created | no | true |
| cleanup | Whether to cleanup the preview environment after the PR is closed | no | false |
Outputs
| name | description |
|---|---|
| service_domain | The domain of the service that was deployed |