Run/Debug Configuration: Ruby Remote Debug
Use this dialog box to define configuration for remote debugging of the Ruby scripts.
In this section:
Before you start working with Ruby, make sure that Ruby plugin is installed and enabled.
Also make sure that the following prerequisites are met:
- Ruby SDK is downloaded and installed on your machine.
- The required framework SDKs are downloaded and installed on your machine.
Refer to their respective download and installation pages for details:
Information and settings
|Name||In this text box, specify the name of the current run/debug configuration.|
|Server command||Use the following command on the server side to enable remote debug: |
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.
|Remote host||Specify URL of the host where remote debugging will take place.|
|Remote port||Specify the port number on the server side. Note that the number entered in this field, is automatically used in the |
|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.|
|Local port||Specify the local port number. Note that the number entered in this field, is automatically used in the |
|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.|
When you edit a run configuration (but not a run configuration template), you can specify the following options for it:
|Name||In this text box, specify the name for the run/debug configuration. The name will help you identify the created configuration when you choose to edit it later, or when you invoke it, for example. from the Run popup (Shift+Alt+F10).|
|Share|| 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
If the file-based format is used, the settings are stored in the
|Single instance only|
The tree view of run/debug configurations has a toolbar that helps you manage configurations available in your project as well as adjust default configurations templates.
|Alt+Insert||Create a run/debug configuration.|
|Alt+Delete||Delete the selected run/debug configuration. Note that you cannot delete default configurations.|
|Ctrl+D||Create a copy of the selected run/debug configuration. Note that you create copies of default configurations.|
|Edit Templates||View and edit the default template for the selected run/debug configuration. The templates are used for newly created configurations.|
Move the selected run/debug configuration up and down in the list.
The order of configurations in the list defines the order, in which the configurations appear when you choose a run/debug configuration.
Default templates of run/debug configurations are always sorted alphabetically.
|Move into new folder / Create new folder|| |
You can group run/debug configurations by placing them into folders.
To create a folder, select the configurations within a category to be grouped, click , and specify the name for the folder. If only a category is in focus, an empty folder is created.
Then, to move a configuration into a folder, between the folders or out of a folder, use drag-and-drop or and buttons.
To remove grouping, select a folder and click .
|Sort configurations||Click this button to sort configurations in alphabetical order.|
When you select Templates in the tree view of the run configurations, you can adjust some settings that apply for all run debug configurations.
|Configurations available in Run Dashboard|| |
In this section you can create a list of run configurations available in the Run Dashboard — tool window that helps you execute and manage multiple run/debug configurations.
Note that the dashboard will only display those configuration types for which you have created one ore more configurations.
|Confirm rerun with process termination||The behavior of this checkbox depends on whether the Single instance only checkbox is selected for a particular run/debug configuration. |
|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.|
Before Launch options
In this area you can specify tasks that should be carried out before starting the selected run/debug configuration. The specified tasks are performed in the order they appear in the list.
|Alt+Insert|| Click this icon to add one of the following available tasks: |
|Alt+Delete||Click this icon to remove the selected task from the list.|
|Enter||Click this icon to edit the selected task. Make the necessary changes in the dialog that opens.|
|/||Alt+Up/Alt+Down||Click these icons to move the selected task one line up or down in the list. (The tasks are performed in the order that they appear in the list.)|
|Show this page||Select this checkbox to show the run/debug configuration settings prior to actually starting the run/debug configuration.|
|Activate tool window|| |
Otherwise, the tool window isn't shown. However, when the configuration is running, you can open the corresponding tool window for it yourself by pressing Alt+4 or Alt+5.