4 ms·

devcontainers has nothing to do with cloud per say. It’s an open spec you can run fully locally.

mbreese 3y ago
Right, which I do locally. But, I used to use vscode’s server version directly on my remote server. Microsoft has recently made this impossible to do with their branded version of VSCode, instead opting to force people to make tunnels from potentially secured servers to vscode.dev. I was more curious is the parent had figured out a way around this. The server module from Openvscode and coder.com still both work for remote access, but you don’t get to use the Microsoft marketplace from those versions. And now that I’m thinking about it more, I’m not sure if you can even use the devcontainer function from the server vscode (or vscode.dev) in the first place.
- explaininjs 3y ago
  Hm okay. There’s always the Remote-SSH extension. Not web-enabled, but I’ve never really seen a compelling web use case anyways.
  - mbreese 3y ago
    The main use-case I have is running a remote vscode session on an HPC cluster. The cluster (and data) are secured, so making a tunnel connection to an outside server (vscode.dev) is not allowed. The data files are also very large. Remote-SSH works, but it is slow with larger/many files. One of the workflows I have is to start a remote R session and load a bunch of datafiles into that environment. The vscode R integration is pretty good, and I'm happy to use it over Rstudio. But, because of this, I want to have this session running on the remote servers -- hence the remote web access. I used to be able to start the vscode web server on the cluster and use SSH tunneling to connect directly to that instance of vscode (through ssl or with other cluster-side proxies as required). It's not a standard use-case, so I see why they are deprecating it. It's using vscode more as a notebook instead of a traditional IDE.

Right, which I do locally. But, I used to use vscode’s server version directly on my remote server. Microsoft has recently made this impossible to do with their branded version of VSCode, instead opting to force people to make tunnels from potentially secured servers to vscode.dev. I was more curious is the parent had figured out a way around this. The server module from Openvscode and coder.com still both work for remote access, but you don’t get to use the Microsoft marketplace from those versions. And now that I’m thinking about it more, I’m not sure if you can even use the devcontainer function from the server vscode (or vscode.dev) in the first place.

explaininjs 3y ago
Hm okay. There’s always the Remote-SSH extension. Not web-enabled, but I’ve never really seen a compelling web use case anyways.
- mbreese 3y ago
  The main use-case I have is running a remote vscode session on an HPC cluster. The cluster (and data) are secured, so making a tunnel connection to an outside server (vscode.dev) is not allowed. The data files are also very large. Remote-SSH works, but it is slow with larger/many files. One of the workflows I have is to start a remote R session and load a bunch of datafiles into that environment. The vscode R integration is pretty good, and I'm happy to use it over Rstudio. But, because of this, I want to have this session running on the remote servers -- hence the remote web access. I used to be able to start the vscode web server on the cluster and use SSH tunneling to connect directly to that instance of vscode (through ssl or with other cluster-side proxies as required). It's not a standard use-case, so I see why they are deprecating it. It's using vscode more as a notebook instead of a traditional IDE.