Difference between revisions of "How to Setup Visual Studio Code for the ifarm"
From GlueXWiki
m |
m (→Setup) |
||
Line 10: | Line 10: | ||
** See the guide under '''Software''' on the [https://halldweb.jlab.org/wiki/index.php/Getting_Started_At_GlueX#Software Getting Started at GlueX page] | ** See the guide under '''Software''' on the [https://halldweb.jlab.org/wiki/index.php/Getting_Started_At_GlueX#Software Getting Started at GlueX page] | ||
** Or see the '''Prerequisites''' section in this [https://jlab.servicenowservices.com/kb?id=kb_article_view&sysparm_article=KB0015066 servicenow article] | ** Or see the '''Prerequisites''' section in this [https://jlab.servicenowservices.com/kb?id=kb_article_view&sysparm_article=KB0015066 servicenow article] | ||
− | * Downloaded [https://code.visualstudio.com/download VS Code] | + | * Downloaded [https://code.visualstudio.com/download VS Code] for your OS |
Revision as of 13:28, 22 March 2024
Table of contents
Contents
Welcome! Have you ever wanted to edit code with smart code completion, integrated Git, syntax highlighting, intuitive debuggers, and so much more, all wrapped into one? Well look no further than Visual Studio (VS) Code! By the end of this guide you will be able to connect to the ifarm and have all these powerful tools right at your fingertips. If you run into any problems (especially if you have Windows machine, as this guide has only been tested for Apple devices) then please message me (Kevin Scheuer) over Slack and let me know!
Setup
Before beginning, please ensure you have the following:
- MobilePass installed and setup, and a working JLab Computing account
- See the guide under Software on the Getting Started at GlueX page
- Or see the Prerequisites section in this servicenow article
- Downloaded VS Code for your OS
The .ssh/config file
- Your first step for getting onto the ifarm will be creating a ssh config file, which dictates how your device, or “local machine”, will connect to the remote JLab server
- Open VS Code and navigate to the Extensions tab on the left hand sidebar. Copy and paste
ms-vscode-remote.remote-ssh
into the search bar, and install the package.- If you can’t see the sidebar, try in the menu View > Appearance > Primary Side Bar
- In the menu bar go to View > Command Palette. Search and select
Remote-SSH: Open SSH Configuration File
- Your default file is likely at
/Users/YOUR_USERNAME/.ssh/config
. Select this file.- If not yet created, no worries. Open VS Code's integrated terminal with Terminal > New Terminal or View > Terminal and navigate to the
.ssh
folder. Runtouch config
to create a blank file. Open the file as instructed.
- If not yet created, no worries. Open VS Code's integrated terminal with Terminal > New Terminal or View > Terminal and navigate to the
- If settings already exist in this file they can be kept, so long as they are not ifarm related. We will be using a slightly modified version from the JLab recommended config file. Download the custom config file and copy/paste its contents into the .ssh/config file open in the editor
- At the very bottom edit
User YOUR_USERNAME_HERE
and replace with your JLab CUE username - Notice there is a dot next to the file name. This indicates edits have been made and need to be saved. Save the changes with File > Save and close the file by pressing the X next to the file name
- Open the command palette again and search/select
Preferences: Open User Settings
- Search
Remote.SSH: Remote Server Listen on Socket
and ensure this option is selected. - While we’re here, lets also change the default
.vscode-server
location. It will typically be placed in/home/YOUR_USERNAME/
, but we don’t want this since it quickly takes up too much space. Its highly recommended to put this in a more spacious location like a user’s directory on the work disk. SearchRemote.SSH: Server Install Path
in your user settings, and set key toifarm
and Value to be your directory- For example, mine is
/w/halld-scshelf2101/kscheuer/
- For example, mine is
- Lastly, ssh needs a specific directory to be setup to work properly. Open a terminal and navigate to
/Users/YOUR_USERNAME/.ssh/
(or wherever your config file is) and performmkdir cm
Connecting
- Before we go about connecting with VS Code, let's test the config file and ensure the connection can be established. Open a terminal via Terminal > New Terminal or View > Terminal and simply run
ssh ifarm
. Note that even though the terminal is "integrated" as part of VS Code, for the most part it functions just like any terminal window - You should be prompted to enter a password, which will be your personal PIN + your current MobilePass code. Click enter and another prompt will appear. This time enter your JLab CUE password.
- You should be taken to your home directory on an ifarm node. We now know the connection can be made. Type
exit
and click enter to close the session- If you get the JEFFERSON LAB prompt but the connection is hanging, it may be that the ifarm node its routing you to is having issues. There are 3 nodes 1801, 1802, and 1901. Retry from step 1 but do
ssh ifarmXXXX
replacing the X’s with one of the three node numbers
- If you get the JEFFERSON LAB prompt but the connection is hanging, it may be that the ifarm node its routing you to is having issues. There are 3 nodes 1801, 1802, and 1901. Retry from step 1 but do
- From the Command Palette run
Remote-SSH: Connect to Host
. Select the option ifarm- If you’d prefer a new window to not be opened, execute
Remote-SHH: Connect Current Window to Host
- If you’d prefer a new window to not be opened, execute
- It may ask what type of system this is, select Linux. Similar to the connection we did in the terminal, you will be prompted for 2 consecutive passcode inputs. The first will be the PIN+MobilePass, and the second your CUE password
- A popup may appear saying something like "the current operating system is not supported". Essentially, support for the ifarm's current operating system will drop by January 2025, but we will be updated by then so there's no need to worry about this
- VS Code will configure the connection, and if successful there should be a green status bar in the lower left corner. You can even open a terminal and see what node you are on, and verify that you are in your home directory
- Congratulations, you are now connected and ready to code! You can exit at any time by clicking on that green status bar and selecting Close Remote Connection.