This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
linux:vscode [2023/12/11 14:24] – [Some common pitfalls:] jansen | linux: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' | * 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' | ||
* vscode will automatically install some server code on the target to receive and handle your connections. This is conveniently done without any user interaction, | * vscode will automatically install some server code on the target to receive and handle your connections. This is conveniently done without any user interaction, | ||
- | * 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. |
< | < | ||
ln -s / | ln -s / |