Ability to create more environments

Currently ReTool has pre-defined “production” and “stage” environments.
It would be great to be able to create more custom environments.
If you consider this feature valuable in 2nd iteration it would be also great to be able to switch between them from the code/url param.
Our use case:
Currently we use a single on-premise ReTool instance in one of our clusters. We would like to expand it and make ReTool to be available on all clusters. One option would be to just run instance per cluster, enable read-only git sync and put additional load balancer in front of it. And we would like to avoid that.
Having such custom environments where every environment would correspond to specific cluster would solve our issue and make whole configuration and maintenance much easier.

1 Like

Hello, what’s the status of this feature request?

Not quite sure what happened but while migrating to new forum engine some messages in this topic were gone. Luckily I’ve got a mail with the copy of it:

1 Like

Multiple environments would help for us as well. Our setup is much simpler than OP, we have prod, QA & dev environments. Additionally in dev, we would love to switch between different databases that different developers run.

1 Like

We have the same use case - developers wanting to test changes against local DBs/envs.