Run/Debug Configuration: PHP Built-in Web Server
Use this dialog box to configure running PHP applications on a local PHP built-in web server. Note that this configuration is not intended for starting a debugging session. To debug an application running on the built-in server, start the application through this configuration and then connect to the running application as described in Zero-Configuration Debugging.
The dialog box consists of the following areas:
Server Configuration area
In this area, configure the access to the built-in Web server.
In this text box, type the name of the host the PHP built-in web server runs on. By default, host is set to
Use this spin box to specify the port on which the PHP built-in web server runs. By default this port is set to port
| In this text box, type the full path to the folder that will be considered server document root. This can be either the project root or any other folder under it. All the folders under the document root will be recursively submitted to the PHP interpreter. |
The server document root folder will be accessed through HTTP at the above specified host:port. URL addresses for other pages of your applications will be composed based on this mapping.
Type the path manually or click Browse and choose the relevant folder in the dialog box that opens.
Use router script
| Select this checkbox to have a PHP router script executed at every HTTP request start-up. The script is run for each HTTP request. If this script returns |
In the text box, specify the location of the script to run. Type the path manually or click Browse and choose the file in the dialog box that opens.
Command Line area
In this area, customize the behavior of the current PHP interpreter by specifying the options and arguments to be passed to the PHP executable file.
| In this text box, specify the options to be passed to the PHP executable file. They override the default behavior of the PHP interpreter and/or ensure that additional activities are performed. |
If necessary, click and type the desired options in the Command Line Options dialog box. Type each option on a new line. When you close the dialog box, they are all displayed in the Command line options text box with spaces as separators.
Custom working directory
In this text box, specify the location of the files that are outside the folder with your sources and are referenced through relative paths. Type the path manually or click Browse and select the desired folder in the dialog that opens.
In this field, specify the environment variables be passed to the built-in server. See Environment Variables in Apache for details.
When you edit a run configuration (but not a run configuration template), you can specify the following options for it:
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).
Select this checkbox 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 the .idea\workspace.xml.
Allow running in parallel
When disabled, every time a new run/debug configuration is launched, PhpStorm 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 checkbox is selected, it is possible to launch as many instances of the run/debug configuration as required. So doing, each runner will start in its own tab of the Run Tool Window or Debug Tool Window.
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.
Create a run/debug configuration.
Delete the selected run/debug configuration. Note that you cannot delete default configurations.
Create a copy of the selected run/debug configuration. Note that you create copies of default configurations.
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, click , and specify the folder name. 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 .
Click this button to sort configurations in the alphabetical order.
Under the Templates node in the tree view of run configurations, you can select a run configuration template and edit its default settings. This will not affect the configurations that are already created, but will be used as defaults when creating new configurations of the corresponding type.
When you select the Templates node itself, you will be able to adjust general settings that apply to 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 — a tool window that helps you execute and manage multiple run/debug configurations.
Note that the dashboard will only display the 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 option is selected for a particular run/debug configuration. |
Temporary configurations limit
Specify 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 must be be performed before starting the selected run/debug configuration. The tasks are performed in the order they appear in the list.
Click this icon to add one of the following available tasks:
Click this icon to remove the selected task from the list.
Click this icon to edit the selected task. Make the necessary changes in the dialog that opens.
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.