Railway Sync
Learn how to configure a Railway Sync for Infisical.
Prerequisites:
- Create a Railway Connection
Add Sync
Navigate to Project > Integrations and select the Secret Syncs tab. Click on the Add Sync button.
Select 'Railway'
Configure source
Configure the Source from where secrets should be retrieved, then click Next.
- Environment: The project environment to retrieve secrets from.
- Secret Path: The folder path to retrieve secrets from.
If you need to sync secrets from multiple folder locations, check out secret imports.
Configure destination
Configure the Destination to where secrets should be deployed, then click Next.
- Railway Connection: The Railway Connection to authenticate with.
- Project: The Railway project to sync secrets to.
- Environment: The Railway environment to sync secrets to.
- Service: The Service to sync secrets to.
- If not provided: Secrets will be synced as shared variables on Railway.
Configure Sync Options
Configure the Sync Options to specify how secrets should be synced, then click Next.
- Initial Sync Behavior: Determines how Infisical should resolve the initial sync.
- Overwrite Destination Secrets: Removes any secrets at the destination endpoint not present in Infisical.
- Import Secrets (Prioritize Infisical): Imports secrets from the destination endpoint before syncing, prioritizing values from Infisical over Railway when keys conflict.
- Import Secrets (Prioritize Railway): Imports secrets from the destination endpoint before syncing, prioritizing values from Railway over Infisical when keys conflict.
- Key Schema: Template that determines how secret names are transformed when syncing, using
{{secretKey}}
as a placeholder for the original secret name and{{environment}}
for the environment.
We highly recommend using a Key Schema to ensure that Infisical only manages the specific keys you intend, keeping everything else untouched.
- Auto-Sync Enabled: If enabled, secrets will automatically be synced from the source location when changes occur. Disable to enforce manual syncing only.
- Disable Secret Deletion: If enabled, Infisical will not remove secrets from the sync destination. Enable this option if you intend to manage some secrets manually outside of Infisical.
Configure details
Configure the Details of your Railway Sync, then click Next.
- Name: The name of your sync. Must be slug-friendly.
- Description: An optional description for your sync.
Review configuration
Review your Railway Sync configuration, then click Create Sync.
Sync created
If enabled, your Railway Sync will begin syncing your secrets to the destination endpoint.
Add Sync
Navigate to Project > Integrations and select the Secret Syncs tab. Click on the Add Sync button.
Select 'Railway'
Configure source
Configure the Source from where secrets should be retrieved, then click Next.
- Environment: The project environment to retrieve secrets from.
- Secret Path: The folder path to retrieve secrets from.
If you need to sync secrets from multiple folder locations, check out secret imports.
Configure destination
Configure the Destination to where secrets should be deployed, then click Next.
- Railway Connection: The Railway Connection to authenticate with.
- Project: The Railway project to sync secrets to.
- Environment: The Railway environment to sync secrets to.
- Service: The Service to sync secrets to.
- If not provided: Secrets will be synced as shared variables on Railway.
Configure Sync Options
Configure the Sync Options to specify how secrets should be synced, then click Next.
- Initial Sync Behavior: Determines how Infisical should resolve the initial sync.
- Overwrite Destination Secrets: Removes any secrets at the destination endpoint not present in Infisical.
- Import Secrets (Prioritize Infisical): Imports secrets from the destination endpoint before syncing, prioritizing values from Infisical over Railway when keys conflict.
- Import Secrets (Prioritize Railway): Imports secrets from the destination endpoint before syncing, prioritizing values from Railway over Infisical when keys conflict.
- Key Schema: Template that determines how secret names are transformed when syncing, using
{{secretKey}}
as a placeholder for the original secret name and{{environment}}
for the environment.
We highly recommend using a Key Schema to ensure that Infisical only manages the specific keys you intend, keeping everything else untouched.
- Auto-Sync Enabled: If enabled, secrets will automatically be synced from the source location when changes occur. Disable to enforce manual syncing only.
- Disable Secret Deletion: If enabled, Infisical will not remove secrets from the sync destination. Enable this option if you intend to manage some secrets manually outside of Infisical.
Configure details
Configure the Details of your Railway Sync, then click Next.
- Name: The name of your sync. Must be slug-friendly.
- Description: An optional description for your sync.
Review configuration
Review your Railway Sync configuration, then click Create Sync.
Sync created
If enabled, your Railway Sync will begin syncing your secrets to the destination endpoint.
To create a Railway Sync, make an API request to the Create Railway Sync API endpoint.