Start the debugging session in the browser using the installed browser extension.ĭuring a debugging session, examine the program state: see variable values, evaluate expressions, step through the program, and so on. For details on getting started with Twig and Blade debugging, refer to Debug Twig templates and Debug Blade templates.

Line breakpoints can be set only on executable lines, but not on comments, declarations, or empty lines. Breakpoints can be set in the PHP context inside PHP, HTML, TWIG, BLADE, and files of other types. On the PhpStorm toolbar, toggle to start listening for incoming PHP debug connections, or choose Run | Start Listening for PHP Debug Connections from the main menu. If work, enable the firewall again, and add a rule to allow connection PhpStorm in your firewall.With the debugging engine installed, you can start debugging by following the zero-configuration debugging approach:Ĭhoose and install the browser extension suitable for your browser. Comment Xdebug 3 setting lines adn uncomment Xdebug 2 setting lines.

Turn Phpstorm debugging on - icon or (Run | Start Listening for PHP Debug Connections)Ĭhange Dockerfile.

Add breakpoint in src/index.php in line 6.

If you wound use xdebug 3 instead 2 install at lest PhpStorm 2020.3 version and checkĪdditionally listen on Xdebug 3 default port 9003 in settings (Settings | Languages & Frameworks | PHP | Debug) or change default listening port from 9000 to 9003.Īdd mapping in Servers setting (Settings | Languages & Frameworks | PHP | Servers): ~/.bashrc' to reload your shellĭocker-compose build -no-cache -force-rm -pull

WSL2 change Linux IP every reboot time, so you should, add global variable (WSLIP) in your Linux system. This solution works only if you use PhpStorm on WSL2 with X server! Small example project to show how to configure xdebug (2 or 3) with WSL2 and Docker.

Download xdebug docker phpstorm