Back
App Hosting

Deploy Code-Server (browser VS Code)

Spin up Code-Server on Victus App Hosting to get a full Visual Studio Code editor and integrated terminal in your browser, then reach it over your allocated port or a custom domain.

code-servervs codeideeditorapp hosting

Code-Server is VS Code running on the server and streamed to your browser — you get the familiar editor, extensions and an integrated terminal without installing anything locally. On Victus it is provisioned as an App Hosting server in the control panel at control.victuscloud.com, so you manage it with the same Console / Files / Startup / Network tabs as any other panel server.

Create the Code-Server instance

  1. 1Log in to control.victuscloud.com (or order an App Hosting plan first from billing.victuscloud.com).
  2. 2Create a new App Hosting server and choose the Code-Server egg/template.
  3. 3Wait for the install to finish — the Console tab shows the setup progress and prints "running" when it is ready.
  4. 4Open the Network tab and note the allocated IP and port; this is where Code-Server is served.

Get your access password

Code-Server protects the editor with a single password. On first boot it is either generated for you or read from the PASSWORD startup variable. Check the Startup tab for the password variable, or look at the Console log where the password is printed on launch.

Set your own password

Open the Startup tab and edit the PASSWORD variable to a strong value of your own, then Restart from the Console. Changes to startup variables only take effect after a restart.

Open the editor

  1. 1Browse to http://YOUR_IP:YOUR_PORT using the values from the Network tab.
  2. 2Enter the password when prompted.
  3. 3Open the integrated terminal (Terminal > New Terminal) to run git, npm, python, etc. inside your server.
  4. 4Install extensions from the Extensions view exactly as you would in desktop VS Code.

Always put it behind HTTPS

You are typing a password and editing source over the connection, so do not leave Code-Server on plain http for long. Point a subdomain at it and enable SSL — see "Point a custom domain/subdomain" and "Enable SSL/HTTPS".

Page will not load?

Confirm the server shows "running" in Console, that you are using the exact port from the Network tab, and that no other process grabbed that port. If it crash-loops on boot, check the Console log for a bad PASSWORD or config value.