-i to set IP address and port of the machine which will be receiving debugging connection from developer computer.-d to set IP address and port of the machine which will be receiving debugger connection from the web server.Run DBGp proxy by executing pydbgpproxy file with parameters:
Phpstorm ide key archive#
Extract the archive for simplicity I extract all the contents to my home directory i.e. This guide will be using 64-bit Linux and PHP Remote Debugging client v11.1.0.
Phpstorm ide key install#
Download and install DBGp proxy for remote debugging from Komodo Remote Debugging Package, specifically for your web server’s operating system. Enable Xdebug extension, then add the following Xdebug configuration to php.ini: zend_extension="" debugger settingsxdebug.remote_enable=1xdebug.remote_host=127.0.0.1xdebug.remote_port=9000įor this guide, DBGp proxy will run on the same machine as the web server and will use Xdebug’s default port, hence 127.0.0.1:9000.ģ. # PHP 7+pecl install xdebug # PHP 5.6.xpecl install xdebug-2.5.5Ģ. Setup Web ServerĪlthough this guide assumes the web server is running on Linux, the guide could also be used on non-Linux web servers with slight modifications.ġ. Mappings between the project folders and the folders on the server should be done correctly in PhpStorm first for debugging to work. In this case, you can simply run the dbgp proxy on your NAT machine, configure xdebug.remote_host setting to the IP address of your NAT machine, and configure the IDEs to connect to the proxy running at :9001. Running a DBGp proxy also allows you to avoid NAT issues where (as seen from PHP+Xdebug on the server) all connections seem to come from the same IP (because your internal network is NATted). So, with DBGp proxy you can limit who can connect to the proxy, and you may have multiple developers debugging the same web server running behind a NATted firewall. Each developer has a separate debugging session running over this proxy, which makes it possible to do multi-user debugging of the same code on the same server. All developers in the team, in turn, then connect to that proxy. When a proxy is used, the PHP Xdebug extension no longer connects to PhpStorm directly, but instead connects to the DBGp proxy server. So this guide will take the longer way which doesn’t need an IF to start (or at least fewer IFs), that is by using Xdebug’s DBGp proxy. See those IFs? Personally, I don’t like IF in programming or in life. private development server), and if it’s not running behind a NATted firewall, and if you want this guide to end here. Sure if the web server is only accessible by the developers (e.g. “Er, wait a minute… Don’t you just use xdebug.remote_connect_back which has been introduced since Xdebug 2.1?"
By Ray Naldo Multi-User Debugging in PhpStorm Using Xdebug and DBGp Proxy Photo by Philipp Katzenberger on Unsplash
0 kommentar(er)
