With other (non-Retool) apps we make, we are used to being able to point people at a staging URL. The running app has its own code, data and config.
So far we haven't been able to reproduce this in Retool.
The "environment" concept that Retool has is not sufficient in itself. (Using multiple environments)
That definition of an environment is pretty much just environment variables -- the data connections etc.
In addition there's the Retool concept of versions/releases, with different code versions. (Releases and history)
But these Retool concepts of "environment" and "version" are disconnected.
So it's on our users to make sure they're in the right environment + version as they do their work. This is super error-prone.
Is there any way to point users at different self-contained versions of a given Retool app? I.e., such that they access -- all at once, no dropdowns etc -- staging versions of the code, data and config?