Everything You Need to Know about SSH


Recently, I’ve been getting more and more into remote development. I’ve written a blog post about setting up SSH for VSCode Remote Development. One thing I’ve learned is that SSH is not very important in my setup.

The reason why is that, once you can connect to a server over SSH, you have access to the entire Linux operating system. The processes that I need to run remotely are usually regular command-line utilities. They just run on a different machine than where the editor runs.

If you have an SSH connection set up to the remote machine, then you can use it with any tool that understands the SSH protocol. This means that many of the plugins which claim to offer some kind of “integration” with things like Git or Docker are redundant. The SSH plug-in provides that integration already!

To connect to your remote Linux machine via SSH, you’ll need to have a few things in place:

A remote Linux server or virtual machine (VM) with SSH enabled.

A computer with an SSH client installed. The SSH client is a program that initiates secure connections to an SSH server.

A computer on which you’ve installed the Remote – SSH extension for Visual Studio Code.

Once you meet those requirements, you can follow the steps below to establish an SSH connection from VS Code:

Install the Remote – SSH extension. To do so:

Open Visual Studio Code and click on the Extensions icon in the Activity Bar (on the left-hand side of the editor).

In the search bar at the top of the window, type “remote-ssh” and click Install on the Remote – SSH extension.

Click Reload when prompted by Visual Studio Code after installation completes. This is necessary to complete installation of the extension.

Once you’ve installed and reloaded, you should see a new green icon in your Activity Bar (a green circle with a white dash in it). This icon represents all Remote Development extensions installed for VS Code. Clicking this icon will expand out a “Remote Explorer” sidebar where you’ll be

This article is a blog post about remote development. I have been developing remotely for years and I have worked with several different setups. This is by far the best setup I have ever had.

I will go into detail on how to set up your environment, including a full walkthrough of setting up this blog post that uses Hugo and is hosted on Github Pages.

The tooling we will use will be the following:

1. Windows 10 with WSL2

2. VSCode Remote SSH extension

3. Ubuntu 20 installed in WSL2

4. Hugo installed in Ubuntu

5. Github Pages repository hosting my blog content

This blog is about using Visual Studio Code with the Remote Development extensions for remote development. We’ll cover the basics of SSH, show you how to connect to an SSH server and explain why you might want to use SSH instead of HTTP to connect to your remote Visual Studio Code instance.

Secure copy (SCP) is a protocol based on Secure Shell (SSH) that allows you to copy files between two computers. You can also copy files from your local machine to a remote machine or vice versa.

To use SCP, you must have a Secure Shell (SSH) client installed on your local computer and your account must be configured for SSH access on the remote server.

In this blog, I am going to show you how to set up VS code remote development over SSH. You might not have heard about this feature yet, but it is pretty new and powerful. It enables you to work on a remote machine or virtual machine (VM) from your local machine.

This is great for beginners who are not familiar with linux commands.

Let’s get started!

Nowadays almost all developers use some kind of a code editor, and many developers have put in a lot of time and effort to become experts with their tool of choice. So why would anyone want to change to a new code editor?

In my case it was simple: VS Code is better than my previous editor in almost every way that matters. The biggest difference is that VS Code feels like an application written in 2019, while Sublime Text feels like an application written in 2005.

I’ve now been using VS Code as my main editor for almost two years, and I haven’t looked back since. In this article I’ll explain how I used VS Code to set up a seamless workflow across multiple development machines and how you can do the same!


Leave a Reply

Your email address will not be published.