|
| 1 | +# VS Code Tunnel |
| 2 | + |
| 3 | +Please keep in mind, that this is not a `VS Code` manual, |
| 4 | +it is only our recommendation how to connect to the {{ hpcinfra }} using the `VS Code` tunnel. |
| 5 | + |
| 6 | +For `VS Code` documentation, see <https://code.visualstudio.com/docs> |
| 7 | + |
| 8 | +We only support `VS Code` tunnel access via the `VS Code` application (installed locally). |
| 9 | +To connect to the `VS Code` tunnel using the URL via a web browser is not supported, |
| 10 | +since web access might not work from all browser or operational system. |
| 11 | +The only confirmed way to connect via a browser is using Windows 11 and Edge. |
| 12 | + |
| 13 | +## Prerequisites |
| 14 | + |
| 15 | +We do recommend to install the [remote development](https://code.visualstudio.com/docs/remote/remote-overview) |
| 16 | +extension pack for the `VS Code` App. |
| 17 | + |
| 18 | + |
| 19 | +## Connection |
| 20 | + |
| 21 | +In the [web portal](./web_portal.md), under the "Interactive Apps" choose `VS Code` Tunnel, |
| 22 | +select the parameters and launch your job by clicking ++"Launch"++ |
| 23 | +When your job has started, connect by clicking ++"Connect"++ |
| 24 | + |
| 25 | +In the new browser tab or window, for the question |
| 26 | +`How would you like to log in to Visual Studio Code?` choose `Microsoft Account` |
| 27 | +(using the arrow keys on your keyboard, then hit ++"Enter"++). |
| 28 | +Then follow the instruction to authenticate yourself. |
| 29 | + |
| 30 | +!!! Warning |
| 31 | + |
| 32 | + If you are an UGent user, and you get an error message something like "You do not have access to this" |
| 33 | + during the Microsoft Authentication, then you might have to |
| 34 | + [whitelist yourself](https://dictselfservice.ugent.be/index.php?page=requestform&form=deviceCodeAuth) |
| 35 | + You can use as motivation "Needed for `VS Code` tunnel for HPC" (You have to do it only once.) |
| 36 | + |
| 37 | + Please be aware, that it might take up to half an hour until the whitelisting become effective. |
| 38 | + |
| 39 | + |
| 40 | +If you are not connected automatically to the tunnel, please select "connect to..." and then |
| 41 | +"Connect to Tunnel" using Microsoft Account and select the tunnel named `vsc-<your vsc account>-<cluster>`. |
| 42 | +Please note that right now you can only have one tunnel per cluster. |
| 43 | + |
| 44 | +If you are asked to update `VS Code` CLI on your remote server, choose ++"Not Now"++. |
| 45 | +You do not have permission to update the CLI, as it is centrally installed. |
| 46 | +This means that your `VS Code` App is newer than the CLI on our systems. |
| 47 | +We update the centrally installed CLI time to time, |
| 48 | +but the upgrade rate of the App/CLI is very high, |
| 49 | +so it is hard for us to follow it tightly. |
| 50 | +If you suspect that the too old version of CLI might cause problem, please send us a |
| 51 | +[software installation request](https://www.ugent.be/hpc/en/support/software-installation-request) |
| 52 | +for `code-cli`. |
| 53 | + |
| 54 | +Please do not use `VS Code` to ssh to the login nodes, |
| 55 | +but always use a `VS Code` Tunnel connection, |
| 56 | +preferably using the [interactive and debug cluster](./interactive_debug.md) |
| 57 | + |
0 commit comments