Run/Debug Configuration: PHP Web Page
This feature is only supported in the Ultimate edition.
Use this dialog box to configure running and debugging of PHP applications on a remote server. According to the settings of this configuration, IntelliJ IDEA fully controls the debugging process: it launches the application, opens the browser, and activates the debugging engine. A PHP Web Page debug configuration tells IntelliJ IDEA the URL address to access the starting page of the application, the browser to open the starting page in, and the debug server configuration to use. For details, see Debugging with a PHP Web Page Debug Configuration.
Click here for the description of the options that are common for all run/debug configurations.
The dialog box consists of the following areas:
|Server||Use this drop-down list to specify the Web server configuration to use. The list shows all the configurations that are currently available in IntelliJ IDEA.|
|Click this button to open the Servers page and view the details of the selected configuration there.|
|Start URL||In this area, compose the URL address to access the application through. In the Start URL text box, specify the local file that implements the starting page of the application. Type the path to the desired file relative to the folder that is mapped to the root folder of the target host. IntelliJ IDEA concatenates the host root URL with the specified relative path and shows the URL address of the application starting page in the read-only field below.|
|Browser||From this drop-down list, select the Web browser to open the application in.|
|Debug||Use the controls in this area to configure behaviour of the debugging tool. |
|Alt+Insert||Click this button to add a new configuration to the list.|
|Alt+Delete||Click this button to remove the selected configuration from the list.|
|Ctrl+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 newly created configurations.|
|or||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.
|Move into new folder / Create new folder||Use this button to create a new folder. |
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 buttons.
|Sort configurations||Click this button to sort configurations in alphabetical order.|
|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.|
|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
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 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.
|Before launch||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. |