for Windows and Linux
The dialog opens when you click next to the CLI Interpreter list in the Development environment section of the PHP page.
Use this dialog to configure PHP engines as interpreters, see Configuring Local PHP Interpreters and Configuring Remote PHP Interpreters. In this dialog, you can add new interpreters and edit or remove the existing ones.
The dialog consists of two panes. The left-hand pane lists all the configured PHP interpreters, both local and remote ones, and contains a toolbar for adding, removing, and copying PHP interpreter configurations. The contents of the right-hand pane depend on the type of the interpreter currently selected in the left-hand pane. Use the controls in this pane to edit the settings of the selected interpreter and even choose its type, if necessary.
The left-hand pane lists all the configured PHP interpreters, both local and remote ones, and contains a toolbar for adding, removing, and copying PHP interpreter configurations.
Click this button to add a new PHP interpreter to the list. From the popup list, choose the interpreter type (Local or Remote), and configure a local interpreter in the right-hand pane or a remote interpreter in the Configure PHP Remote Interpreter Dialog dialog that opens.
Click this button to remove the selected interpreter from the list.
Click this button to create a new interpreter with the settings copied from the selected one.
The contents of the right-hand pane depend on the type of the interpreter currently selected in the left-hand pane. Use the controls in this pane to edit the settings of the selected interpreter and even choose its type, if necessary.
Remote interpreter accessible through SSH
From this list, choose one of the created SSH configurations, or click and create a new configuration as described in .
Remote interpreter on a Vagrant instance
Vagrant instance folder
In this field, choose the folder that points at the environment you are going to use. Technically, it is the folder where the VagrantFile configuration file for the desired environment is located. Based on this setting, IntelliJ IDEA detects the Vagrant host and shows it as a link in the Vagrant Host URL read-only field.
Remote interpreter in a Docker container
In this field, specify the Docker configuration to use, see Configure the Docker daemon connection settings for details. Select a configuration from the list or click and create a new configuration on the Docker page that opens.
In this field, specify the base Docker image to use. Choose one of the previously downloaded or your custom images from the list or type the image name manually, for example,
Remote interpreter running in a multi-container Docker Compose application
in this field, specify the Docker configuration to use, see Configure the Docker daemon connection settings for details. Select a configuration from the list or click and create a new configuration on the Docker page that opens.
In this field, specify the docker-compose.yml file defining the application's services.
In this field, choose the desired application's service.
In this field, define the environment variables. See Using Environment Variables for details.
|In this area, choose how the Docker container for the selected service should be managed by IntelliJ IDEA. |
Remote interpreter running through Windows Subsystem for Linux (WSL)
From this list, choose one of the installed Linux distributions to use.
In this field, type the identifier to distinguish the interpreter from others, for example,
In this field, specify the path to the PHP engine. Type the path manually or click and choose the executable file in the dialog that opens. IntelliJ IDEA detects the version of PHP and displays it in the PHP version read-only field.
IntelliJ IDEA also detects the debugging engine and the php.ini configuration file. The type of the debugging engine associated with the PHP interpreter and its version are displayed in the Debugger read-only field. If no debugger is detected or you have disabled it in php.ini file (see Configuring Xdebug for Using in the On-Demand Mode), the field shows Debugger: Not installed.
The location of php.ini is displayed in the Configuration file read-only field. To edit the php.ini in IntelliJ IDEA, click Open in Editor.
Click this button to check that the specified PHP home directory actually contains a PHP executable file. If no PHP executable is detected at the specified location, IntelliJ IDEA displays the corresponding error message.
Click this button to have IntelliJ IDEA display a separate information window with the installation details and the list of loaded extensions and configured options. Note that the additional options specified in the Configuration Options field of the CLI Interpreters dialog are not listed.
In this field, specify the location of the Xdebug extension to enable IntelliJ IDEA to activate it when necessary.
IntelliJ IDEA 2016.2 and later supports the On-Demand mode, where you can disable debugger for your global PHP installation and have it enabled automatically on demand only when you are debugging your command-line scripts or when you need code coverage reports. This lets your command line scripts (including Composer and unit tests) run much faster.
Use this field to customize the configuration settings of the installation by composing a string of configuration directives to be passed through the -d command line option and thus add new entries to the php.ini file. Click to open the Configuration Options dialog and create a list of new php.ini entries there.
Configuration options dialog
In this field, type the name of the new entry.
In this field, type the value of the new entry.
Click this button to have a new line added to the list and specify the name and value of a new entry there.
Click this button to remove the selected entry from the list.
Up / Down
|Use these buttons to move the selected entry up or down in the list. The order of entries in the list determine the order in which they are passed through the -d command line option. |
You can add as many entries as you need, just keep in mind that they will be transformed into a command line with its length limited to 256 characters.