remote development

Today, I'm happy to introduce our latest feature to you to use Windows Subsystem for Linux version 2 (WSL 2, or simply WSL) to run or test Go applications seamlessly. This feature is called Run Targets and supports WSL 2, Docker, and SSH remotes. If you'd like to learn more about these, the overview article of this feature, explaining it in more detail, should come in handy. In this article, I'll focus on the WSL 2 side of this feature. If you wish to use other targets, you can check the article covering the Docker target. If you'd prefer a video version of this article, then please head t

Up until now, when you wanted to test or run your shiny new code, you had only the local machine to do so. Many of our users have told us that they'd prefer to use Docker to run their code since that's where they will ultimately test, build, and deploy the code with their CI/CD pipeline. Today I'm happy to introduce to you our latest feature that allows you to seamlessly use Docker containers for your workflows from the comfort of your IDE. We call this feature "Run targets", and it doesn't extend to Docker support only. We currently support Docker, WSL 2, and SSH remotes. You may

Previously, when you were using GoLand, you could test and run your code only on the same machine you had the IDE installed on. You could use the FTP/SFTP Connectivity (ex. Remote Hosts Access) plugin and the Settings/Preferences | Tools | External Tools feature or the built-in Docker plugin to achieve some sort of workflow. However, this was not convenient to use and did not have the integration level that our users expect when using our tools. That is why our team embarked on a journey to provide a better experience for these kinds of workflows. And that's how the Run targets feature came