PHPSTORM XDEBUG REMOTE INSTALL
PHPSTORM XDEBUG REMOTE CODE

ConclusionР”Вespite initial impressions, Xdebug is very easy to install for use via Vagrant when one knows what has to be done. This proves our breakpoints work as intended, and Xdebug has been successfully set up. Our $a array has one less element due to the array_pop operation we performed. Clicking the Resume button once more produces a slightly different output: Also notice you can expand it to see what it contains. Clicking the Resume button moves on to the next breakpoint and produces the following output: YouРІР‚в„ўll notice in the right panel that only the superglobals are declared РІР‚вЂњ no other variables are present at this time. The left frame lists the stacktrace РІР‚вЂњ the files the request already went through РІР‚вЂњ and stops at routes.php, our file. A new tab should launch and immediately return you to PHPStorm with an output similar to this one: Then, go to Run -> Debug and run your predefined debug configuration. If you have the app open in your browser, close that tab now, otherwise PHPStorm wonРІР‚в„ўt be able to re-run it. Then, put a breakpoint next to each line of the closure that does something, like so:

PHPSTORM XDEBUG REMOTE CODE

In app/routes.php, alter the home routeРІР‚в„ўs closure so that it looks like the code below: Route :: get ( '/', function ( ) ) ThatРІР‚в„ўs all we need to configure on XdebugРІР‚в„ўs end. Under that line, add the following options: xdebug.remote_enable = onР”В¬lose the file and restart php-fpm: sudo service php5-fpm restart. HomesteadРІР‚в„ўs default xdebug.ini file (found in /etc/php5/mods-available) originally only contains the directive that tells PHP to enable it, but nothing else: zend_extension=xdebug.so To allow Xdebug to be used remotely, we need to alter the ini file and give it some parameters that are off by default. If youРІР‚в„ўre using any other Vagrant box instead and xdebug isnРІР‚в„ўt present, refer to ShameerРІР‚в„ўs post for installation instructions. If you see xdebug.ini in there, itРІР‚в„ўs loaded. Or by checking out the conf.d folders of PHP FPM and PHP CLI: ls /etc/php5/fpm/conf.d You can see this by looking at phpinfo() after booting Homestead: Homestead comes with Xdebug installed and enabled. When you get the Laravel greeting screen, youРІР‚в„ўre good to go. You can do this by executing: composer create-project laravel/laravel Laravel -prefer-dist Once itРІР‚в„ўs booted, vagrant ssh into it, and install a sample Laravel app. To prepare the environment, please install and boot Homestead. In this tutorial, weРІР‚в„ўll set up Xdebug with PHPStorm for Vagrant hosted PHP apps. If youРІР‚в„ўre completely unfamiliar with it, you would do well to first install it following the procedures below, and then refer to the post linked above for a breakdown of everything Xdebug can do for you and your apps. For a detailed walkthrough, see ShameerРІР‚в„ўs post. Xdebug is a PHP extension which allows you to debug and profile your code, view detailed and readable stack traces when errors happen, and much more. But as the applications weРІР‚в„ўre developing reside inside a virtual machine, theyРІР‚в„ўre a bit tricky to debug with Xdebug which is, by default, tuned for localhost.

No matter the platform, you can easily have a development environment up and running in no time thatРІР‚в„ўs not only stable, but also identical in every regard to the environment your colleagues, mentors or mentees use. By now, weРІР‚в„ўve all learned to love Vagrant and the development flexibility it provides.

Phpstorm xdebug remote