How to Deploy VS Code with Marketplace Apps
Traducciones al EspañolEstamos traduciendo nuestros guías y tutoriales al Español. Es posible que usted esté viendo una traducción generada automáticamente. Estamos trabajando con traductores profesionales para verificar las traducciones de nuestro sitio web. Este proyecto es un trabajo en curso.
Run VS Code Server in the browser with the VS Code Marketplace App. Code Server uses the open source code from Microsoft’s VS Code to provide a web interface for VS Code.
Deploy VS Code with Marketplace Apps
Linode’s App Marketplace allows you to easily deploy software on a Linode using the Linode Cloud Manager. To access Linode’s App Marketplace:
Log in to your Linode Cloud Manager account.
From the Linode dashboard, click on the Marketplace button in the left-hand navigation menu.
The Linode creation page appears, with the Marketplace tab pre-selected.
Under the Select App section, select the app you would like to deploy:
Once you have selected the app, proceed to the app’s Options section and provide values for the required fields.
VS Code Options
The VS Code Marketplace app has the following required configuration fields.
|The password to login to the VS Code Web UI||This is the password you use to log into the VS Code web interface. The password must meet the complexity strength validation requirements for a strong password. Required|
|Your email address||This email address is used for VS Code configuration and is added to the SOA record for the domain if you add one. This field is also used to create DNS records, and is required to create an SSL certificate.|
VS Code Advanced Options
The VS Code Marketplace form includes advanced fields to setup the limited user account and DNS records of the VS Code server. These are optional configurations and are not required for installation.
|The version of VS Code Server you’d like installed||This is the version of VS Code Server that is installed during setup. The default at the time that this guide was written is 3.10.2. This field is filled in and it is recommended that you use this value. If you do not fill in this field, the latest version is used.|
|The limited sudo user to be created for the Linode||This is the limited user account to be created for the Linode. This account has sudo user privileges.|
|The password for the limited sudo user||Set a password for the limited sudo user. The password must meet the complexity strength validation requirements for a strong password. This password can be used to perform any action on the server, similar to root, so make it long, complex, and unique.|
|The SSH Public Key that will be used to access the Linode||If you wish to access SSH via Public Key (recommended) rather than by password, enter the public key here.|
|Disable root access over SSH?||Select |
|Your Linode API Token||Your Linode |
|Domain||The domain name where you want to host your VS Code server. The installer creates a DNS record for this domain during setup if you provide this field along with your |
|Subdomain||The subdomain you want the installer to create a DNS record for during setup. The subdomain should only be provided if you also provide a |
|Would you like to use a free Let’s Encrypt SSL certificate?||Select |
After providing the app-specific options, provide configurations for the Linode server:
|Select an Image||Debian 10 is currently the only image supported by the VS Code Marketplace App, and it is pre-selected in the Linode creation page. Required|
|Region||The region where you want the Linode to reside. In general, it is best to choose a location that is closest to you. For more information on choosing a DC, review the How to Choose a Data Center guide. You can also generate MTR reports for a deeper look at the network routes between you and each of the data centers. Required.|
|Linode Plan||The Linode’s hardware resources. The minimum memory recommendation is 1 GB with 2 cores. You can always resize your Linode to a different plan later if you feel you need to increase or decrease the system resources. Required|
|Linode Label||The name for the Linode, which must be unique between all of the Linodes on your account. This name is how you identify the server in the Cloud Manager’s Dashboard. Required.|
|Add Tags||A tag to help organize and group the Linode resources. Tags can be applied to Linodes, Block Storage Volumes, NodeBalancers, and Domains.|
|Root Password||The primary administrative password for the Linode instance. This password must be provided when you log in to the Linode via SSH. The password must meet the complexity strength validation requirements for a strong password. The root password can be used to perform any action on the server, so make it long, complex, and unique. Required|
When you’ve provided all required Linode Options, click on the Create button. The VS Code app completes the installation anywhere between 2-5 minutes after the Linode has finished provisioning.
Getting Started after Deployment
VS Code is now installed and ready to use.
Before you go to the app, if you filled out the optional VS Code configuration fields for domain:
VS Code is accessed via the domain name if you entered one, or by the rDNS name if you did not. For example,
http://li1234-555.members.linode.com, replacing the domain name or rDNS name with values for the server.
At the login screen, login using the password you entered during installation.
After logging in, the VS Code Welcome screen appears in the browser and ready to code.
The VS Code Marketplace App installs the following software on the Linode:
|Code Server||Code Server which hosts the open source web interface of VS Code.|
|NGINX||An open source web server.|
|ufw||ufw is the uncomplicated firewall, a frontend for iptables.|
NoteCurrently, Linode does not manage software and systems updates for Marketplace Apps. It is up to the user to perform routine maintenance on software deployed in this fashion.
You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.
This page was originally published on