During our recent webinar, we shared over 40 GoLand tips & tricks that you can use to boost your productivity with the IDE. Here's the summary of the presentation and all the tips shown: 00:00:18 - Organize projects in IDE 00:01:13 - Hide/Show Editor tabs 00:01:44 - Using the Zen Mode 00:02:09 - Show/hide the Project View Tool Window 00:02:24 - Use the Navigation Bar 00:03:04 - Import a package without typing its name 00:03:43 - Smart Type Completion 00:04:34 - Postfix Completion 00:05:43 - Method-like Completion (more…)

Windows Subsystem for Linux, or WSL as it's commonly known, allows Windows 10 to run Linux inside Windows. We are going to have a look at WSL 1 since, as of the publishing of this article, WSL 2 is not officially released yet. After installing WSL 1, and enabling your preferred Linux distribution on it, you can set up Go as you would on a normal Linux installation. You should also install Go for Windows since the IDE will still run on the Windows side of things. With these two Go installations in place, some additional configuration is needed. Make sure to point the GOPATH both in Window

This is the last part of our series on running a Go service using Docker, Docker Compose, or Kubernetes. In this part, we'll focus exclusively on running and debugging when using Kubernetes clusters. While we won't cover how to install and configure a Kubernetes cluster, a variety of tools, such as kubeadm, minikube, and microk8s, can all be used to achieve this. If you are on Windows, then Docker Desktop for Windows comes with built-in Kubernetes support. If you instead plan to use a platform that is based on ARM chips, like the Raspberry Pi 4, then you can use something like k3s to get st

Today we’ll be continuing our series on how to use Docker to run and debug Go applications. In this post, we'll use Docker Compose to run and debug our application. For this article, we’ll be using the source code here and we’ll switch to the compose branch before we start. Running Go applications using Docker Compose Let's start with running the application using Docker Compose. (more…)

In the previous article of this series, we discussed how to get started using Docker to run our Go applications. Today, we’ll take a look at how to debug a Go application that runs inside a container. Creating the Dockerfile for debugging Using the same repository that we used in the last article, we can switch our branch to the debug branch. (more…)

Today we start a miniseries of articles about the support inside GoLand for Docker, Docker Compose, and Kubernetes and how it can help us write (micro-)services in Go. We’ll look at how to configure the project in the IDE, how to use either Docker or Kubernetes to run or debug our project, and how to connect the project to our database of choice, PostgreSQL. Let's start with a presentation of the normal Docker workflow, then we’ll build our container and run it. (more…)

Hello again. This is the third, and final, article from our series on Go Modules. In this article, we'll cover how to version our project and manage the migration to a new major version. In case you missed the previous posts, here's a list of articles from the series: Starting with a new Go Module from scratch Creating a new project Adding dependencies to the project Running and debugging the application Dependencies and how to use them Changing the version of a dependency Using the vendoring mode Tidying up the modules in a project Visualizing the dependencies o

In this second article from our series on Go Modules, we'll cover how to manage project dependencies:. This series of articles is broken down into the following sections: Starting with a new Go Module from scratch Creating a new project Adding dependencies to the project Running and debugging the application Dependencies and how to use them Changing the version of a dependency Using the vendoring mode Tidying up the modules in a project Visualizing the dependencies of a project Versioning and migrating to a new major version Non-major version upgrading

Test-Driven Development, or TDD as it is commonly referred to, is the development process in which tests are written first, then the code to support them is created, and, when every test passes, code is refactored. Let's have a look at how the unique features of GoLand allow us to be proficient with this workflow. The general TDD workflow looks like this: write tests run tests to see that they fail write the code and make it pass the tests refactor the code (more…)

Let's take a look at what GoLand 2020.1 brings in terms of editing features to help us save time when we have to edit our Go code. We can start with some of the more obvious things, like parameter names. When implementing an interface, parameter names are suggested automatically: But you can also get suggestions when just typing function/method parameters: But this is not just about the big, obvious, things. Sometimes, it's also the little things that make a difference to our quality of life, and GoLand tries to address these as well. (more…)

Goroutines are an essential part of most programs written in Go. But using lots of goroutines makes a program harder to debug. Or does it? In this blog post, we'll take a look at labeling goroutines with custom data, one of the latest features in GoLand 2020.1, which is now in EAP. Usage from the IDE Usage from the command line Performance implications Using a custom library to enable debugging labeling (more…)

Development for Go Modules continues in Go 1.13 and the support GoLand has for them too. Today, we'll have a look at how to transform our development model to use them without hassle. This series of articles is broken down into the following sections: Starting with a new Go Module from scratch Creating a new project Adding dependencies to the project Running and debugging the application Dependencies and how to use them Changing the version of a dependency Using the vendoring mode Tidying up the modules in a project Visualising the dependencies of a project