The absolute path /app/profiler will correspond to the same local path within your site files on your computer. This is the path on the “server” – the container which your site runs in within Local by Flywheel. The second line, profiler_output_dir, is the path to the directory where the profiler snapshots will be stored. I like to use the extensions Xdebug helper for Google Chrome and Xdebug helper for Mozilla Firefox. The first line, profiler_enable_trigger, will make enable profiling only when a “trigger” is set. Instead you might want to add the following two lines: xdebug.profiler_enable_trigger = 1 xdebug.profiler_output_dir = /app/profiler

But if you set xdebug.profiler_enable=1 you will enable the Xdebug profiler for every single request that you make on the site – which is probably not what you want. Here you can see that the Xdebug profiler isn’t enabled. If you switch between multiple PHP versions for your site in Local by Flywheel, you need to edit the php.ini file for each version.Ĭlose to the end of your php.ini file, you’ll find the Xdebug section that Local by Flywheel has added for you: The default Xdebug section in php.ini Each of your sites using the “Custom” environment configuration should have a file structure like this where you’ll find your php.ini Now you need to edit your site’s php.ini.

It is not possible to enable Xdebug when not using the “Custom” environment.Ĭlick the button, and you should see a brief notification:Įnabling debugging using Xdebug in Local by Flywheel with PhpStorm is very easy, enabling profiling doesn’t take much more effort either, but the process is very different. You need to have a “Custom” environment to enable Xdebug. If the button is disabled, go back and read the beginning of this article. Now, if you navigate to the “Utilitites” menu item on one of your site configurations, you should find a new button to configure PhpStorm (and IntelliJ IDEs) for Xdebug in Local by Flywheel. One-click-configuration of phpStorm for Xdebug in Local by Flywheel

Enable it and close the preferences window. Under the “Add-ons” you’ll find the add-on “Xdebug IntelliJ integration” pre-installed. Navigate to the Local by Flywheel preferences. This is an extremely smooth process: Enable the one-click configuration for IntelliJ IDEs (PhpStorm) and Xdebug Enable Xdebug in Local by Flywheel – and configure PhpStormįirst, we have to enable Xdebug in Local by Flywheel and create the debug profile in PhpStorm. Under your site’s “Site Setup” menu item, you’ll find “Local Environment” where you can change from “Preferred” to “Custom”.

Download xdebug profiler phpstorm