Specifically, the PHP versions you’ll be supporting Confirm PhpStorm’s project setup What follows are opinionated defaults, so adjust as you deem necessary.
#Phpstorm setup xdebug how to
The basic idea in PhpStorm is that you tell it where to look for the xdebug session (the “server”) and then you tell it how to link the files it’s running in the VM to the files found in the repo (called “mapping”). Reference Debugging with xdebug and PhpStorm That can help catch errors and guide your StackOverflow searching.Debugging with xdebug and PhpStorm - VVV VVVĦ. Lastly, if you're still having issues with XDebug and aren't seeing any errors, try including a custom php.ini file that'll set XDebug logging up. So let's spit out the contents of that file:Ĭopy the path to the xdebug.so file and plop that into the "Debugger extension" then click the icon to refresh:įor good measure, patiently watch that entire video linked above again and don't skip steps. Once you're in the shell you'll see that the …xdebug.ini file is there after all. Neat, we're learning and demystifying stuff. Or instead of trusting me, check out their Github ssh task that calls their Lando engine, which is aliased to docker exec. Try it yourself by getting the container id for php-fpm via docker ps If you're familiar with regular Docker commands, this is essentially running docker exec: What's going on behind the scenes? I feel like I'm trusting Lando with everything and feel lost! Let's dive into the container using lando ssh Quick detour:Īre we actually ssh'ing into our container? That's debatable, but like the Lando command says, we're dropping "into a shell on a service." Feels very much like ssh'ing. Notice that upon expanding the "Configuration file" list, xdebug is not listed. If you follow this video and under "CLI Interpreters" you see "Debugger: Not installed" check this out. However, PHPStorm might not automatically detect XDebug or stop automatically detecting it. Here I'll cover an odd case that I haven't found elsewhere online.įirst off, one of the best resources for getting Lando, PHPStorm, and XDebug working is the video and content on this page. We can get it back into balance, even if it's ugly and hairy. So don't beat yourself up if these three (and more) stop playing nicely. So there's another variable to throw into the mix. This wasn't happening with earlier versions of Docker Desktop. env file was automatically picked up and parsed for environment variables. Wasn't that? Move on to eliminating the next suspect. I'll spare the lengthy philosophical discussion on "how to live your best debugger life" but certainly a chapter would be, "slowly eliminate could-be's." It "could-be" my version of PHPStorm? Use Jetbrains Toolbox and find out.
#Phpstorm setup xdebug pro
Pro tip: there's a thing called Jetbrains Toolbox which lets you have multiple versions of an app. While the folks at Jetbrains are super on it, I believe the settings can get imported incorrectly and you have to tear your hair out to get things right. For those interested in the nitty gritty, you can find the details in Github.Īt the time of this writing, some of those files were updated a couple months ago. #1 We're using the Lando Drupal 8 recipeīy the way, the docs for Lando mention the recipes and which ones are available.
Let's realize that we're dealing with a few different components that may not always play well together. Your Lando + PHPStorm + XDebug was working yesterday and now it's not.
0 kommentar(er)
