Paths referenced below might differ slightly if your Homebrew installation is located in /opt/homebrew. Note: If you are on an Apple Silicon-based Mac and you installed Homebrew without Rosetta, the Homebrew binaries can be found in /opt/homebrew/bin, as opposed to being located in /usr/local/bin.
Let’s make sure php and pecl are installed and linked correctly.Īssuming you use Homebrew, your terminal output will be: $ which php /usr/local/bin/php $ which pecl /usr/local/bin/pecl Setting up Xdebugīefore we begin, I assume you have Laravel Valet installed. If you’re looking to set up a different environment (or would like to see a video), take a look here. Xdebug 3.0 has now been released, and some changes have been made to this guide to reflect this change. This is both for myself for future reference, and for anyone who stumbles upon this post and finds it helpful.
#Phpstorm setup xdebug code
However, it’s quite worth it when you see how easy it is to debug your code with it.After watching a stream where Matt Stauffer and Derick Rethans (the creator of Xdebug) discussed setting up Xdebug with Visual Studio Code, I decided it might be helpful to write a post on setting up Xdebug with PhpStorm, specifically if you’re running Laravel Valet. Although simple with instructions, installing and configuring Xdebug on your own can be a pain. Here we can see that our code stoped executing on the breakpoint and that we have an option to inspect the variables we have. Let’s put a breakpoint somewhere in our code to see if it actually works. Hit apply and now we are ready to test our code. Then under DBGp Proxy as ide key set PHPSTORM and port to 9001 to match the settings we added in php.ini. Now open settings (File -> Settings) and change the Xdebug settings as follows.
Here we specify the 127.0.0.1 domain and 8000 port on which Laravel serves. In the top right corner click on add configuration.Ĭlick on the plus icon and select PHP Web Page.Įnter the name and click on the button with three dots. Now we need to restart apache service in order for it to use new configuration. Zend_extension = C:\xampp\php\ext\php_xdebug-2.7.
#Phpstorm setup xdebug update
Update C:\xampp\php\php.ini and change the line zend_extension = C:\xampp\php\ext\php_xdebug-2.7.Īfter I copied xdebug dll to its proper place I added the following configuration to the php.ini file at the same location as instructed in the third step above.Move the downloaded file to C:\xampp\php\ext.When it finishes it will give you an appropriate version of xdebug to download and provide you with the instructions of where to put it. Once you get the output copy it into the text area on the website and click analyze. I will use php -i from the command line terminal. You can choose whichever option is easier for you. What we have to is to paste either the output of phpinfo() or php -i from the terminal. We will use official xdebug tailored installation on this website.
#Phpstorm setup xdebug how to
This article will cover how to configure xdebug with xampp on Windows. Xdebug will help us discover the source of the problems in our code and give us a better insight on what is happening. No one should ever underestimate the importance of a fully set up development environment and none is complete unless you have proper error debugging tools in place.
0 kommentar(er)
