How To Set Up the Remote Development Environment for the Vscode


There are many advantages to editing code remotely. For one, you don’t have to worry about setting up and maintaining the development environment on your local machine. Other benefits include being able to work from anywhere and collaborate with other developers more easily.

Vscode has a Remote Development Extension Pack that allows you to work on remote projects, such as:

– Projects running in Docker containers

– Projects hosted on remote file systems

– Projects hosted on virtual machines

– Projects running inside WSL (Windows Subsystem for Linux)

– Projects hosted on remote machines over SSH connections

In this tutorial, we will be setting up the Remote Development Environment for Vscode by connecting a remote SSH host. Let’s start by installing the Remote Development Extension Pack:

Remote development over SSH reduces the attack surface of the remote host while simultaneously increasing the usability of tools such as ssh-agent.

The following tutorial will walk you through setting up a remote development environment for Vscode. The setup described here is only one of many possible configurations.

If you would like to have other readers share their setup, please send us a pull request or open an issue and we will incorporate your changes.

Visual Studio Code is the best editor for programming and has a huge community of developers who are always developing new plugins and extensions.

I’ve been using Vscode for a year now, and I am completely in love with this editor.

In this article, I am going to show you how you can use Vscode on a remote server to develop your software. The biggest benefit of this is that you don’t need to buy any other software or tools like SSH client and terminal. You can develop straight from your editor.

In the first part of this guide, we will be setting up our server to host our website and know how to access it via SSH.

In the second part of this guide, we will be setting up VS Code so that we can edit files remotely from out laptop.

A few months ago, Microsoft announced the Remote Development extension for VSCode. The extension is a set of three extensions that enable you to develop inside a dev container without having to install all the dependencies locally.

The benefit of this is that you can use any OS to develop your application and ensure it will run in the same way on a remote machine. The Remote Development extension has been available since May 2019, but it became stable in December. You can read more about it on the official announcement blog post.

In this article, we’ll learn how to set up the dev container for our projects and what kind of problems we might encounter while doing so.

The extension is split into three parts:

Remote – SSH: Connect to any location by opening folders on a remote machine/VM using SSH.

Remote – Containers: Connect to a container or remote machine and use VS Code with its full feature set as if you were sitting right there!

Remote – WSL: Connect to WSL or a remote machine with SSH terminals, file copy, and sync.

First, install the Remote – SSH extension in Vscode.

Go to File -> Preferences -> Settings and search for “remote”. If you want to configure the Remote – SSH extension manually, scroll down to the Remote section in the tree on the left and click on SSH.

Click on Credentials and then select Store Credentials in Keychain. Select your ssh key, if you have more than one. If not, create a new ssh key using your terminal.

Click on the + button in ssh: Connected Hosts and add a new hostname.

You can either use an existing hostname or add a new one. Add your username (e.g., tux) and IP address (e.g., 193.168.10.10). Click on Open in New Window to open a new connection to your remote server in Vscode.

In the terminal window of Vscode, you will be asked whether you want to trust this server or not:

The authenticity of host ‘193.168.10.10 (193.168.10.10)’ can’t be established.

ECDSA key fingerprint is SHA256:+jMkJc2Q9a1n7mhu


Leave a Reply

Your email address will not be published.