This read-only field shows the command that should be entered on the server side to launch the debug
server. Port and dispatcher-port numbers here are taken from the Port and Local port fields.
$COMMAND$ corresponds to the name of the script to be debugged.
Specify URL of the host where remote debugging will take place.
Specify the port number on the server side. Note that the number entered in this field, is automatically used in the
rdebug command. As you type port number, the suggested command string
Remote root folder
Specify the root directory on the server side, where the script to be debugged is located. This field
defines mapping to the local root folder.
Specify the local port number. Note that the number entered in this field, is automatically used in the
rdebug command. As you type the local port number, the suggested command string
Local root folder
Specify the local root directory containing the script in question. Type the path, or click
and find the desired root in the Select Path dialog box.
Click this button to add a new configuration to the list.
Click this button to remove the selected configuration from the list.
Click this button to create a copy of the selected configuration.
Click this button to edit the default configuration templates.
The defaults are used for newly created configurations.
Alt+Up or Alt+Down
Use these buttons to move the selected configuration or folder up and down in the list.
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.
If one or more run/debug configurations are in focus, the selected run/debug configurations
are automatically moved to the newly created folder. If only a category is in focus, an empty folder is created.
Move run/debug configurations to a folder using drag-and-drop, or the
Click this button to sort configurations in alphabetical order.
In this text box, specify the name of the current run/debug configuration. This field does not appear for the default run/debug configurations.
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.
Select this check box to make the run/debug configuration available to other team members.
The shared run/debug configurations are kept in separate xml files under .idea\runConfigurations folder,
while the local run/debug configurations are kept in
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, RubyMine 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 makes sense when the 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.
Specify which tasks must be performed before applying the run/debug configuration.
The specified tasks are performed in the order they appear in the list.
Click this icon to add a task to the list. Select the task to be added:
Run External tool.
Select this option to run an application which is external to RubyMine.
In the dialog that opens, select the application or applications that should be run.
If the necessary application is not defined in RubyMine yet, add its definition.
For more information, see Configuring Third-Party Tools and External Tools.
Run Another Configuration.
Select this option to have another run/debug configuration executed.
In the dialog that opens, select the configuration to run.
This option is available only if you have already at least one run/debug configuration in the current project.
Run File Watchers.
Select this option to have RubyMine apply all the currently active file watchers,
see Using File Watchers for details.
Run Grunt task. Select this option to run a Grunt task.
In the Grunt task dialog box that opens, specify the Gruntfile.js where the required task is defined,
select the task to execute,
and specify the arguments to pass to the Grunt tool.
Specify the location of the Node.js interpreter, the parameters to pass to it, and the path to the grunt-cli package.
Run Gulp task. Select this option to run a Grunt task.
In the Gulp task dialog box that opens, specify the Gulpfile.js where the required task is defined,
select the task to execute,
and specify the arguments to pass to the Gulp tool.
Specify the location of the Node.js interpreter, the parameters to pass to it, and the path to the gulp package.
Run npm Script. Select this check box to execute an npm script.
In the NPM Script dialog box that opens, specify the package.json file where the required script is defined,
select the script to execute, choose the command to apply to it, and specify the arguments to execute the script with.
Specify the location of the Node.js interpreter and the parameters to pass to it.
Compile TypeScript. Select this option to run the built-in TypeScript compiler
and thus make sure that
In the TypeScript Compile Settings dialog that opens, select or clear the Check errors check box
to configure the behaviour of the compiler in case any errors are detected:
If the Check errors check box is selected, the compiler will show all the errors
and the run configuration will not start.
If the Check errors check box is cleared, the compiler will show all the detected errors
but the run configuration still will be launched.
Generate CoffeeScript Source Maps.
Select this option to have the source maps for your CoffeeScript sources generated.
In the dialog that opens, specify where your CoffeeScript source files are located.
For more information, see CoffeeScript Support.