Can I create an environment that isn't deployed?
typedrat
FREEOP

a year ago

Is there a way on Railway to have an environment that doesn't get deployed, but is just used as a template for ephemeral PR deployments? One of the components of my tech stack is a little complicated in that it can be run either as two separate containers where one of the containers can be scaled out or as one container with the restriction that it supports only one instance. I'd rather keep things simpler and lighter for development and only run the single-node version for PR branches, but I don't want to have to have an entire bonus deployment that won't be used just to serve as a template for the PR deployments.

Solved

7 Replies

typedrat
FREEOP

a year ago

N/A


a year ago

Hello,

I thnk you are looking for the base Environment setting.


typedrat
FREEOP

a year ago

I know, my question is how I can have a base environment without that environment actually getting deployed itself?


a year ago

The base environment is only going to see a deploy if you merge into the GitHub branch you have connected to the services.


typedrat
FREEOP

a year ago

most of the services are docker containers, though -- won't those get deployed all the time because they exist on Docker Hub?


a year ago

For services deployed from images, we do not auto deploy them in the base environment as we have no mechanism to detect when a new image was released.


a year ago

!s


Status changed to Solved brody about 1 year ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...