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)
