CodeServer Session
This page allows you to start an interactive CodeServer session, providing a Visual Studio Code development environment accessible directly through your web browser, running as a job on the HPC cluster.
Launching CodeServer
Section titled “Launching CodeServer”The main tab allows you to configure and start the CodeServer job.
1. Apptainer Container Settings
Section titled “1. Apptainer Container Settings”These settings define the container environment for CodeServer:
- Container Path (Prefix: code-server): Specifies the path to the Apptainer image containing the pre-configured CodeServer environment (e.g.,
/home/Containers/code-server_latest.sif). This path is typically managed by system administrators. - New Environment Variable: Add any necessary environment variables required for your development environment within the container.
2. Start CodeServer
Section titled “2. Start CodeServer”- Start CodeServer Button: Clicking this button submits a request to the Slurm scheduler to launch the CodeServer instance within the specified container.
3. Connecting to Your Session
Section titled “3. Connecting to Your Session”Once the job is submitted and starts running, the interface will update to show connection options:
- Copy Password: Copies the temporary password for this CodeServer session to your clipboard. You will need this password to log in.
- Connect: Opens the CodeServer login page in a new browser tab.
- Stop CodeServer: Terminates the running CodeServer job.
Click Connect. You will be presented with the CodeServer login screen:
- Paste the password you copied using the Copy Password button into the password field.
- Click SUBMIT.
4. Using CodeServer
Section titled “4. Using CodeServer”After successful login, you will be presented with the familiar Visual Studio Code interface running in your browser, connected to the resources allocated by your Slurm job.
You can use the integrated terminal, file explorer, editor, and extensions as you normally would in VS Code, operating within the container environment on the HPC cluster.
(Note: Job scheduler options like partition, node count, CPU/GPU resources might be configured under the separate “Setting” tab for this job type, or they might use predefined defaults.)