![]() The icon should become green and now your requests will be directed to the php-fpm instance with Xdebug enabled. To start debugging, make sure you have the Xdebug helper extension enabled in your browser:Īfter installation, go to the URL of the application you want to debug and click the Xdebug helper icon and click Debug. Now your debug environment is ready to go. data/web/apps//releases/3įinally click the ‘Start Listening for PHP Debug Connections’ button. Hint: if you’re making use of a multi deployment structure (like with Hypernode Deploy) and want to know what the absolute path for your current directory is, you can use realpath to find out: realpath apps//current Here you can fill in the absolute path of the application on the remote server, for example: Click the + button to add a server and fill Name and Host with the full domain name of the site you want to debug (for example Then check the box Use path mappings and click on the right column next to your project root. Then you open up your PhpStorm project and go to your File -> Settings -> PHP -> Servers. To enable remote debugging, you first have to enable the Xdebug setting: hypernode-systemctl settings php_xdebug_enabled True -blockĪfter that, you need to open a reverse SSH tunnel so that Xdebug on the Hypernode can communicate with PhpStorm on your local machine: $ ssh -R 9003:localhost:9003 -N Requests containing the Xdebug cookie from the Xdebug helper extension, will be routed to the Xdebug php-fpm instance. How does this work? When you enable the php_xdebug_enabled setting, we spin up a separate php-fpm instance which has Xdebug enabled. ![]() With remote debugging, one can connect to a Hypernode and start debugging while the application doesn’t take a performance hit! With this release, we are excited to announce a cool new feature on the Hypernode platform: remote debugging. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |