Use this dialog to configure running and debugging of single PHP files locally using a PHP console.
Configuration areaIn this area, specify the script to run or debug and the parameters to process it with, if applicable.
Item
Description
File
In this field, specify the location of the file to run or debug. Type the path to the file manually or click Browse and select the desired location in the Choose PHP File dialog that opens.
Arguments
In this field, type the list of arguments to be passed to the PHP script, same way as if you were entering these parameters in the command line.
If necessary, click and type the desired switches in the Arguments dialog. Type each argument on a new line. As you type, they appear in the Arguments field with spaces as separators.
To use one of the built-in IDE macros as a variable, click and select the macro from the list that opens.
Command Line areaIn this area, customize the behavior of the current PHP interpreter by specifying the options and arguments to be passed to the PHP executable file.
Item
Description
Interpreter
The list contains all the currently configured local and remote PHP interpreters. Choose one of the configured PHP interpreters from the list, or click and define a new interpreter as described in Configure local PHP interpreters and Configure remote PHP interpreters.
Interpreter options
In this field, specify the options to be passed to the PHP executable file. They override the default behavior of the PHP interpreter or ensure that additional activities are performed.
If necessary, click and type the desired options in the Command Line Options dialog. Type each option on a new line. When you close the dialog, they are all displayed in the Command line options field with spaces as separators.
Custom working directory
In this field, specify the location of the files that are outside the folder with the script and are referenced in your script through relative paths. Type the path manually or click the Browse button and select the desired folder in the dialog that opens.
This setting does not block the script execution because the script location is always specified through a full path.
Environment variables
In this field, specify the environment variables to be passed to the built-in server. You can add the name-value pairs of environment variables manually by clicking , or click and browse to the .env file on your computer.
For more information, refer to Environment Variables in Apache.
Docker Compose areaThis area only appears if you select a Docker Compose-based remote interpreter in the Interpreter field. Here, you can add some Docker Compose commands with options to the run configuration.
Item
Description
Commands and options
You can use the following commands of the Docker Compose Command-Line Interface:
Commands
Supported options
up: Builds, creates, starts, and attaches to containers for a service.
--abort-on-container-exit
--build
--exit-code-from SERVICE
--scale SERVICE=NUM...
--timeout TIMEOUT
run: Runs a one-time command against a service.
--entrypoint CMD
-l, --label KEY=VAL
--name NAME
-p, --publish=[]
--rm
--service-ports
--use-aliases
-u, --user=""
-v, --volume=[]
exec: Runs arbitrary commands in your services.
--index=index
--privileged
-u, --user USER
Command preview
Use this field to preview the complete command string.
For example, the up --build exec --user jetbrains combination in the Commands and options field produces the following output in the preview:
Use the controls in this area to configure behaviour of the debugging tool.
Item
Description
Break at the first line
Select this checkbox to have the debugging tool stop at the first line of the source code.
Common settingsWhen you edit a run configuration (but not a run configuration template), you can specify the following options:
Item
Description
Name
Specify a name for the run configuration to quickly identify it among others when editing or running.
Allow multiple instances
Allow running multiple instances of this run configuration in parallel.
By default, it is disabled, and when you start this configuration while another instance is still running, PhpStorm suggests stopping the running instance and starting another one. This is helpful when a run configuration consumes a lot of resources and there is no good reason to run multiple instances.
Store as project file
Save the file with the run configuration settings to share it with other team members. The default location is .idea/runConfigurations. However, if you do not want to share the .idea directory, you can save the configuration to any other directory within the project.
By default, it is disabled, and PhpStorm stores run configuration settings in .idea/workspace.xml.
ToolbarThe 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.
Item
Shortcut
Description
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.
The button is displayed only when you select a temporary configuration. Click this button to save a temporary configuration as permanent.
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 or and buttons.
To remove grouping, select a folder and click .
Click this button to sort configurations in the alphabetical order.
Before launchIn this area, you can specify tasks to be performed before starting the selected run/debug configuration. The tasks are performed in the order they appear in the list.
Item
Shortcut
Description
Alt+Insert
Click this icon to add one of the following available tasks:
Launch Web Browser: select this option to have a browser started. In the dialog that opens, select the type of the browser and provide the start URL. Also, specify if you want the browser to be launched with the JavaScript debugger.
Run External tool: select to run an external application. In the dialog that opens, select one or multiple applications you want to run. If it is not defined in PhpStorm yet, add its definition. For more information, refer to External tools and External Tools.
Run Another Configuration: select to execute another run/debug configuration and wait until it finishes before starting the current configuration. If you want to run several configurations in parallel, use a compound run/debug configuration.
Run File Watchers: select this option to have PhpStorm apply all the currently active File Watchers.
Run Remote External Tool: adds a remote SSH external tool.
Run Grunt task: select this option to run a Grunt task.
In the Grunt task dialog that opens, specify the Gruntfile.js where the required task is defined, select the task to execute, and specify the arguments to pass to the Grunt tool.
Specify the location of the Node.js interpreter, the parameters to pass to it, and the path to the grunt-cli package.
Run gulp task: select this option to run a Gulp task.
In the Gulp task dialog that opens, specify the Gulpfile.js where the required task is defined, select the task to execute, and specify the arguments to pass to the Gulp tool.
Specify the location of the Node.js interpreter, the parameters to pass to it, and the path to the gulp package.
Run npm script: select this option to execute an npm script.
In the NPM Script dialog that opens, specify the npm run/debug configuration settings.
Compile TypeScript: select to run the built-in TypeScript compiler and thus make sure that all the changes you made to your TypeScript code are reflected in the generated JavaScript files. In the TypeScript Compile Settings dialog that opens, select or clear the Check errors checkbox to configure the behaviour of the compiler in case any errors are detected:
If the Check errors checkbox is selected, the compiler will show all the errors and the run configuration will not start.
If the Check errors checkbox is cleared, the compiler will show all the detected errors but the run configuration still will be launched.
Generate CoffeeScript Source Maps: select this option to generate the source maps for your CoffeeScript sources. In the dialog that opens, specify where your CoffeeScript source files are located.
Upload files to Remote Host: select this option to have the application files automatically uploaded to the server according to the default server access configuration.
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
By default this checkbox is selected and the Run or the Debug tool window opens when you start the run/debug configuration.
Otherwise, if the checkbox is cleared, the tool window is hidden. However, when the configuration is running, you can open the corresponding tool window for it yourself by pressing Alt+4 or Alt+5.
28 June 2024
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4