One possible solution here is to look at the SSH_CLIENT env variable: do various things (R/W operations) on one machine and the other machine's connection will be interrupted/closedĮxpectation: be able to work on two machines at once that share the same home directory by being able to change where VSCode Remote installsĪnother use case - many ec2 instances where the only configured user is ec2-user.try to connect to both at the same time.get two different servers that share the same home directory.
It would be great if it was possible to specify in some config file where we want VSCode to install itself on the remote machine.Įxtensions: just the Python one, but I imagine this is irrelevant if I edit a file in one instance, the other instance disconnects - I imagine they're overwriting each other and clashing somehow).
I have two different servers that share the same home directory that's network shared, so I can't connect to both instances at once without some weird things happening (e.g. By default, VSCode Remote SSH "mounts" itself at ~/.vscode-remote.
0 kommentar(er)
