Computer Documentation Wiki

User Tools

Site Tools

Trace: • software_categories
linux:vscode

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
linux:vscode [2023/10/12 14:56] – [Special case: remote jupyter notebooks] jansenlinux:vscode [2025/01/07 08:36] (current) – [Some common pitfalls:] jansen
Line 22: Line 22:
 The page also has information about setting up a local ssh client, if you don't have one yet (Windows; putty is not supported, you need the commandline ssh client here, which is already present on Linux and Mac OS) The page also has information about setting up a local ssh client, if you don't have one yet (Windows; putty is not supported, you need the commandline ssh client here, which is already present on Linux and Mac OS)
  
-Next, set up [[:ssh|key-based ssh]], so you don't have to type a password a couple of times when you open your remote vscode. Some functionality will not even work with password-based logins anyway. Take care of the secrecy of your **private** key. It's called private for a very obvious and very impoirtant reason. If you loose that key or if others get their hand on it, your account is compromised and you should immediately contact the helpdesk for removing the key and resetting all login related settings.+Next, set up [[:ssh|key-based ssh]], so you don't have to type a password a couple of times when you open your remote vscode. Some functionality will not even work with password-based logins anyway. Take care of the secrecy of your **private** key. It's called private for a very obvious and very important reason. If you loose that key or if others get their hand on it, your account is compromised and you should immediately contact the helpdesk for removing the key and resetting all login related settings.
  
 The vscode documentation has some more [[https://code.visualstudio.com/docs/remote/troubleshooting|tips and tricks]] that may come in handy. The vscode documentation has some more [[https://code.visualstudio.com/docs/remote/troubleshooting|tips and tricks]] that may come in handy.
Line 28: Line 28:
   * Setup ssh to go directly to your target host. Sterrewacht desktops are directly reachable over the internet, no setup needed. But if you want to run on a Sterrewacht compute node, the ALICE cluster or a Institute Lorentz machine, you will need a proxy setup to go through the appropriate gateway. See [[ssh:tipsandtricks|SSH tips and tricks]], especially example 3 at the bottom.    * Setup ssh to go directly to your target host. Sterrewacht desktops are directly reachable over the internet, no setup needed. But if you want to run on a Sterrewacht compute node, the ALICE cluster or a Institute Lorentz machine, you will need a proxy setup to go through the appropriate gateway. See [[ssh:tipsandtricks|SSH tips and tricks]], especially example 3 at the bottom. 
   * 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 teh 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.1697122581.txt.gz · Last modified: by jansen

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki