Local debugging. In this mode, the application files remain where they are in the WebStorm project on you machine. WebStorm runs them on the built-in Web server with the root URL
http://localhost:<built-in server port>/<project root>.
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 WebStorm 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 Files.
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.
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||
WebStorm 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, WebStorm itself "retrieves" the paths to local files by parsing the URL addresses of their copies on the server
|Alt+InsertAlt+InsertAlt+InsertAlt+InsertAlt+InsertAlt+InsertAlt+Insert or Ctrl+NAlt+InsertCommand N or Control EnterControl N or Control EnterCommand N or Control Enter||Click this button to add new configuration to the list.|
|DeleteDeleteDeleteDeleteDelete or Ctrl+DDeleteDeleteDeleteDelete, Backspace or Command BackspaceDelete, Backspace or Command BackspaceDelete, Backspace or Command Backspace||Click this button to remove the selected configuration from the list.|
|Ctrl+DCtrl+DCtrl+DCtrl+DMeta+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.|
UpUpUpUpUp or Ctrl+PUpUpUpUp or Control PUpUp or Control P
DownDownDownDownDown or Ctrl+NDownDownDownDown or Control NDownDown or Control N
|Use these buttons to move the selected configuration up and down in the list. The order of configurations in the list defines the order, in which configurations appear in the Run/Debug drop-down list on the main toolbar.|
|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.|
|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.