Unlinkable Environments
ss-wit
FREEOP

2 years ago

Currently, my workflow involves having separate "dev" and "prod" environments on railway, and I connect to dev to for local development. This work great!

A nice-to-have feature would be "locking" my prod environment such that it can't be used via the CLI like this. As I onboard new devs to my project I'm encouraging them to use this workflow, but it'd be great for peace-of-mind to be able to know no accidental selections of the wrong environment are possible.

1 Replies

brody
EMPLOYEE

2 years ago

This is an awesome idea, and building off this I think it would be beneficial to even lock out linking to services so you don't accidentally up into a database.


Loading...