VS Code: Difference between revisions

From UMIACS
Jump to navigation Jump to search
No edit summary
No edit summary
Line 2: Line 2:


==Cluster Usage==
==Cluster Usage==
It can be convenient when using our [[SLURM]] computing clusters to open a VS Code session on the submission node(s) that you have access to via VS Code's [https://code.visualstudio.com/docs/remote/ssh Remote - SSH extension]. Steps to set this up can be found [https://code.visualstudio.com/docs/remote/ssh#_installation here].
It can be convenient when using our [[SLURM]] computing clusters to open a connection to a VS Code server session on the submission node(s) that you have access to via VS Code's [https://code.visualstudio.com/docs/remote/ssh Remote - SSH extension]. Steps to set this up can be found [https://code.visualstudio.com/docs/remote/ssh#_installation here].


===Best Practices===
===Best Practices===
Because of the multi-tenant nature of our submission nodes, using the Remote - SSH extension to connect to a VS Code server running on a submission node can have adverse affects on other users simultaneously using the submission nodes if not used properly. The following is a list of "best practices" that we have compiled through observation of usage on submission nodes across the institute as well as through discussion with users.
* TODO

Revision as of 17:04, 15 May 2024

Visual Studio (VS) Code is a multi-platform source-code editor developed by Microsoft. It can be used with a variety of programming languages and can have its base functionality extended through use of extensions available via its marketplace.

Cluster Usage

It can be convenient when using our SLURM computing clusters to open a connection to a VS Code server session on the submission node(s) that you have access to via VS Code's Remote - SSH extension. Steps to set this up can be found here.

Best Practices

Because of the multi-tenant nature of our submission nodes, using the Remote - SSH extension to connect to a VS Code server running on a submission node can have adverse affects on other users simultaneously using the submission nodes if not used properly. The following is a list of "best practices" that we have compiled through observation of usage on submission nodes across the institute as well as through discussion with users.

  • TODO