User Tools

Site Tools


linux:vscode

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
linux:vscode [2023/12/11 14:24] – [Some common pitfalls:] jansenlinux:vscode [2025/01/07 08:36] (current) – [Some common pitfalls:] jansen
Line 29: Line 29:
   * In the context of vscode, setting up a Proxy is NOT identical to logging in on the gateway, then loggin in to your target; if you configure vscode to go to the gateway only, vscode's file browser will be running on the gateway, and vscodes internal server code will be running there too. And since most ssh gateways are just gateways, and not powerful compute nodes, this will be very limiting. So do setup that proxy config!!   * In the context of vscode, setting up a Proxy is NOT identical to logging in on the gateway, then loggin in to your target; if you configure vscode to go to the gateway only, vscode's file browser will be running on the gateway, and vscodes internal server code will be running there too. And since most ssh gateways are just gateways, and not powerful compute nodes, this will be very limiting. So do setup that proxy config!!
   * vscode will automatically install some server code on the target to receive and handle your connections. This is conveniently done without any user interaction, but inconveniently, this code ends up in ''$HOME/.vscode-server'' and space in the home disk is limited. If this fails, check your quota, move things around, get rid of the incomplete vscode directory and try again.   * vscode will automatically install some server code on the target to receive and handle your connections. This is conveniently done without any user interaction, but inconveniently, this code ends up in ''$HOME/.vscode-server'' and space in the home disk is limited. If this fails, check your quota, move things around, get rid of the incomplete vscode directory and try again.
-  * What usually works (NOT FULLY TESTED YET): first log in to your target server, create a directory .vscode-server on a local disk of that system, and make a symbolic link to that location in your home directory, e.g.+  * What usually works: first log in to your target server, create a directory .vscode-server on a local disk of that system, and make a symbolic link to that location in your home directory, e.g.
   <code>  mkdir /data1/username/.vscode-server   <code>  mkdir /data1/username/.vscode-server
   ln -s /data1/username/.vscode-server $HOME </code>   ln -s /data1/username/.vscode-server $HOME </code>
linux/vscode.1702304671.txt.gz · Last modified: by jansen