Local debugging. In this mode, the application files remain where they are in the
IntelliJ IDEA project on you machine. IntelliJ IDEA runs them on the built-in Web server with the root URL
http://localhost:<built-in server port>/<project root>.
The built-in server port is specified on the Debugger.
A debugging session in this mode can be initiated in two ways:
- Create and launch a permanent debug configuration.
Remote debugging. In this mode, the application files are on an external web
server and you have their copies in a IntelliJ IDEA project on your computer.
No matter, whether the web server itself is running on a physically remote host or on your machine, application
files deployed on it are treated as remote.
For details, see Working with Web Servers: Copying
You can deploy the application files to a web server and launch the application yourself or debug an already running application.
A Remote debugging session can be initiated only through a permanent debug configuration that you have to define yourself manually.
|Name||In this text box, specify the name of the current run/debug configuration.|
If this check box is selected, the run/debug configurations become available to the other team members.
In case of the standard project format, the run/debug configurations will be stored in the .ipr file, which is usually shared through the version control, rather than .iws.
In case of the directory-based project format, the shared run/debug configurations are kept in separate xml files under .idea\runConfigurations folder, while the local run/debug configurations are kept in the .idea\workspace.xml.
This field does not appear for the default run/debug configurations.
|Remote URLs of local files||
IntelliJ IDEA displays this area only when you create a permanent debug configuration manually. For
automatically generated temporary configurations the area is not shown.
In this area, map the local files to be involved in debugging to the URL addresses of their copies on the server.
These mappings are required only if the local folder structure under the project root differs from the folder structure on the server. If the structures are identical, IntelliJ IDEA itself "retrieves" the paths to local files by parsing the URL addresses of their copies on the server
|Alt+InsertAlt+InsertAlt+InsertAlt+InsertAlt+InsertAlt+InsertCtrl+N or Alt+InsertAlt+InsertAlt+InsertCommand N or Control EnterControl N or Control EnterCommand N or Control Enter||Click this button to add new configuration to the list.|
|Alt+DeleteAlt+DeleteAlt+DeleteAlt+DeleteAlt+DeleteAlt+DeleteAlt+DeleteAlt+DeleteAlt+DeleteCommand Delete or Command BackspaceCommand DeleteCommand Delete or Command Backspace||Click this button to remove the selected configuration from the list.|
|Ctrl+DCtrl+DCtrl+DCtrl+DMeta+DCtrl+DCtrl+DCtrl+D, Ctrl+Shift+Down or Ctrl+Shift+UpCtrl+DCommand DCommand DCommand D||Click this button to create a copy of the selected configuration.|
|Edit defaults||Click this button to edit the default configuration templates. The defaults are used for the newly created configurations.|
|or||Alt+UpAlt+UpAlt+UpAlt+UpAlt+Up or Ctrl+Alt+AAlt+UpAlt+UpCtrl+Alt+UpCtrl+Shift+UpControl UpControl UpControl Alt Up or Alt+DownAlt+DownAlt+DownAlt+DownAlt+Down or Ctrl+Alt+EAlt+DownAlt+DownCtrl+Alt+DownCtrl+Shift+DownControl DownControl DownControl Alt Down||Use these buttons to move the selected configuration or group of configurations (folder) up and down in the
The order of configurations or folders in the list defines the order, in which configurations appear in the Run/Debug drop-down list on the main toolbar.
|Use this button to create a new
If one or more run/debug configurations have the focus, then the selected run/debug configurations are automatically moved to the newly created folder. If only a category has the focus, then an empty folder is created.
Move run/debug configurations to a folder using drag-and-drop, or buttons.
|Name||In this text box, specify the name of the current run/debug configuration. This field does not appear for the default run/debug configurations.|
|Defaults||This node in the left-hand pane of the dialog box contains the default run/debug configuration settings. Select the desired configuration to change its default settings in the right-hand pane. The defaults are applied to all newly created run/debug configurations.|
|Temporary configurations limit||Specify here the maximum number of temporary configurations to be stored and shown in the Select Run/Debug Configuration drop-down list.|
Select this check box to make the run/debug configuration available to other team members.
If the directory-based project format is used, the settings for a run/debug configuration are stored in a separate xml file in the .idea\runConfigurations folder if the run/debug configuration is shared and in the .idea\workspace.xml file otherwise.
If the file-based format is used, the settings are stored in the .ipr file for shared configurations or in the .iws file for the ones that are not shared.
This check box is not available when editing the run/debug configuration defaults.
|Single instance only||If this check box is selected, this run/debug configuration cannot be launched more than once.
Every time a new run/debug configuration is launched, IntelliJ IDEA checks the presence of the other instances of the same run/debug configuration, and displays a confirmation dialog box. If you click OK in the confirmation dialog box, the first instance of the runner will be stopped, and the next one will take its place.
This make sense, when usage of certain resources can cause conflicts, or when launching two run/debug configurations of the same type consumes too much of the CPU and memory resources.
If this check box is not selected, it is possible to launch as many instances of the runner as required. So doing, each runner will start in its own tab of the Run tool window.
|Before launch||Specify which tasks should be carried out before starting the run/debug configuration.
The specified tasks are performed in the order that they appear in the list.