In case you haven’t heard, I’m planning to do some livestreams in the near future which are focused on live development / building in the cloud. I’m working on a few ideas, but if you have any suggestions - please throw them my way! To prepare for this, I’ve recently spent some time making sure my local development environment is in order. Windows Terminal and Windows Subsystem for Linux are a couple of the key tools in my local development environment. Windows Subsystem for Linux is the focus for this post.
For some time now, I’ve been using Windows Terminal as my local terminal for interacting with my command-line tools for quite some time now. Whenever I’m demonstrating Kubernetes concepts or working with the Azure CLI, I’ll likely have had the Windows Terminal open at some point. I always get questioned about which terminal that is, and how people can get access to it. I recently put together a Cloud Drop on How Windows Terminal can make YOU productive with Azure, so I figured it’s time to also write up a blog post on the same! Whether you’re a Developer, DevOps Engineer, Infrastructure Operations or Data Scientist, you’ve probably had to interact with a command-line terminal / shell at some point, so I hope this will be useful for you!
Windows Terminal is a modern application that allows you to use your command-line of choice, whether that is the Windows Command Prompt, PowerShell, PowerShell Core, Windows Subsystem for Linux or the Azure Cloud Shell. This Cloud Drop shows you how to install Windows Terminal, and some tips/tricks in making you productive in Azure!
Hopefully by now you’ve had a chance to read part 1 of this series, which explains why you may be interested in using GPG keys to sign your commits. Congratulations on getting to the second part! In part two, we’re going to focus on how I worked through setting up GPG in my Windows environment, and generating a set of keys for use. There were some challenges/hurdles along the way, and we’ll talk through those too!