Working with Run/Debug Configurations
To run or debug your code in GoLand, you can use numerous run/debug configurations. Each run/debug configuration represents a named set of run/debug startup properties. When you perform run, debug, or test operations with GoLand, you always start a process based on one of the existing configurations using its parameters.
GoLand comes with a number of run/debug configuration types for the various running, debugging and testing issues. You can create your own run/debug configurations of specific types.
Each run/debug configuration type has its own default settings. Whenever a new run/debug configuration of the respective type is created, it is based on these default settings.
Temporary run/debug configurations
A temporary run/debug configuration is automatically created every time you chooseor for an item without a permanent configuration. To save a temporary configuration as permanent, do one of the following:
Select it in the Run/Debug Configurations Dialog and click on the toolbar.
Select it in the run/debug configuration selector and then click Save '[configuration name]' configuration.
Temporary configurations are marked with semi-transparent icons and are managed the same way as the permanent configurations.
By default, 5 temporary run/debug configurations are allowed per project, so when you create the sixth configuration the one created first is removed, and so on. To change this limit, use the corresponding field in the Templates page of the Run/Debug Configurations Dialog.
Permanent run/debug configurationsA permanent run/debug configuration is explicitly created for a particular class or method. If there is no permanent configuration for an item, GoLand automatically creates a temporary configuration for it, when you choose or from the context menu of this class or method.
Run/debug configuration templates
The templates with default run/debug configuration settings are listed in the Run/Debug Configurations dialog under the Templates node. They denote the settings that are used when new run/debug configurations are created.
You can set the default settings for a specific configuration type that will become applicable to any run/debug configuration of this type created later. Changing defaults does not affect the existing run/debug configurations.
The process of editing per-type default configuration settings is described in Changing Run/Debug Configuration Templates. The process of creating or editing custom run/debug configurations is described in Creating and Editing Run/Debug Configurations.