Part of Railway's value is allowing you to get sane defaults on delivering change to your customers. Many users have told us that they really enjoy being able to open a PR and get a test env. setup to make requests against with no config involved. (Really just flipping a switch on a setting.)

We're collecting comments and feedback for PR Environments. This is to make it easier to manage things like variable lifecycle when connected to multiple services with multiple environments. And… any blindspots you may be facing!

Proposed Solution(s)

• Environments store configuration such as services and plugins

• Events are like commits

• Optionally environments could remember from which base environment they were created

• Base environment can be changed like in a GitHub PR

• PR environments would basically work by forking the base environment and merging any changes back to the base environment when the PR is merged

• Optionally the concept of a changeset/patch, which which would be a collection of events that is not tied to any environment history. This would allow to have some type of environment configuration that is not an active environment taking resources

Let us know what you think is missing from the experience below!