& echo "deb focal main" > /etc/apt//ppa_ondrej_php.list \ & apt-key adv -homedir ~/.gnupg -keyserver hkp://:80 -recv-keys C300EE8C \ & apt-key adv -homedir ~/.gnupg -keyserver hkp://:80 -recv-keys E5267A6C \
Phpstorm debug install#
& apt-get install -y gnupg gosu curl ca-certificates zip unzip git supervisor sqlite3 libcap2-bin \ RUN ln -snf /usr/share/zoneinfo/$TZ /etc/localtime & echo $TZ > /etc/timezone vendor/laravel/sail/runtimes/8.0Īnd in the vendor/laravel/sail/runtimes/8.0 folder there is a Dockerfile FROM ubuntu:20.04 In the root of the project there is a docker-compose.yml (this is the default) # For more information: Ĭontext. Now i want to use Xdebug and have absolutely no idea what to do.
Phpstorm debug windows#
Ive started the Laravel 8.x tutorial installation for Windows using Docker and Laravel's sail. Nevertheless, there is more to it, you can have Drush, PHP Unit and more integrations with PHPStorm.So, after hours of Googling no right answer is found. Up to this point, you should have a functional PHPStorm + Xdebug configuration.
Refresh your browser and the debugger will show up with the index.php variables. Now, create some breakpoints and start listening for Xdebug connections. $ cat /usr/local/etc/php/conf.d/docker-php-ext-xdebug.ini NOTE: You will have to tell to PHPStorm the path of the Xdebug.so file, you can get that by running these commands: $ lando ssh On PHP language level, we tell PHPStorm that we will be using PHP 7.4 You can get there by clicking on: configuration -> Languages and Frameworks -> PHP
Phpstorm debug series#
Let's breakdown the PHPStorm configuration is a series of steps: You should uncheck all the breakpoints selected per default and only leave the ones you have marked in your code.įor some reason, the default breakpoints do not work with Drupal. NOTE: On the Breakpoint section (bottom left in the image above), Everything is marked as default. You should end up seeing something like this: Go to the debugger section on VSCode and run the option which says: Listen for XDebug.įinally, go to your Lando site and refresh your browser. This is a Gist for the launch.json file esnaremaussa/launch.jsonįor testing purposes, you can go to the index.php file and add $test = 1 and add that line as a breakpoint in VSCode. Note: in the port section, make sure is the same port added in the php.ini file. vscode in the root of your application and create the launch.json file with the following code: This plugin can be found here: PHP Debug.Ĭreate the folder. Make sure have installed the PHP Debug plugin. Up to this point, you should be able to run lando start and have a Drupal 9 site up and running with Xdebug listening on port 9000.įor the second part, we will be configuring the most popular IDEs among PHP developers, VSCode and PHPStorm.Ĭonfiguring VSCode with Xdebug is very simple, all you have to do is following these steps: Trust me, changing the port when experiencing problems with Xdebug may just fix all your problems and save you a lot of time wandering around. Right now, as configured above, the xdebug.log file will be located at the root of the application. The name can be anything and be located anywhere within your working directory. Very handy when things don't work as expected. The xdebug.remote_log flag is used for defining the location of the Xdebug logs.
Nevertheless, if you run into issues with Xdebug, don't' hesitate to change the port to 9001 (or anything, really) and rebuild lando. Xdebug will be listening on port 9000 per default. Nevertheless, these two configuration items are very important, especially when experiencing problems with Xdebug:
This is a very generic configuration for Xdebug and everything should work out of the box after running lando start. This is a Gist for the php.ini file esnaremaussa/php.ini Enter fullscreen mode Exit fullscreen mode
0 kommentar(er)
