You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm thinking specifically in the context of a database where you may only have exposed it to the internal network, but want to connect to it to debug or view data.
This command could do something like spin up a temporary container for the duration of the command which allows traffic from the user's machine and acts as a tunnel through to the db.
The text was updated successfully, but these errors were encountered:
The user could add an SSH host to their own (development) Compose file, perhaps even in a Compose debug profile, so it's not deployed normally. Least we can do is document this?
Something like this would be really helpful:
I'm thinking specifically in the context of a database where you may only have exposed it to the internal network, but want to connect to it to debug or view data.
This command could do something like spin up a temporary container for the duration of the command which allows traffic from the user's machine and acts as a tunnel through to the db.
The text was updated successfully, but these errors were encountered: