#Phpstorm docker xdebug install#
#Phpstorm docker xdebug generator#
#Phpstorm docker xdebug code#

Zend_extension has always been the PHP ini file parameter name for adding in extensions – it hooks the pecl extension (or extensions installed with other tools like PEAR) installed to the runtime, so things like zip, redis, curl and the like use the same parameter to enable them. Remember me mentioning “bookmarklets” in the browser earlier? You have to use an extension to keep a server connection alive with your Xdebug session – for example, for Firefox: Xdebug.remote_enable and tostart are more interesting.

#Phpstorm docker xdebug code#

Phpstorm xdebug code#Įnable remote triggering of the Xdebug server and set autostart to true when either a breakpoint is hit in the code or you’ve set the break to be at the entry point to your application’s code and: bingo. Do I wish I’d have known about this years ago? For sure. Xdebug.remote_port has an interesting quirk in that if you don’t set the parameter, it defaults to port 9000.

I guess it’s an interesting aspect that shows Xdebug’s history in that it was probably chosen as a default port before the CGI adopted replacement php-fpm used port 9000. So, it’s important to set the remote port to 9001 (or whichever free port you wish) to stop clashes. Xdebug.remote_host is the point at which our Docker configuration starts making the process perhaps a little convoluted. In our case, we develop as a company with Macs, so it’s handy that Docker has a reserved handle ( ) to route into the correct IP. Windows does the same at the time of writing, but Linux distributions might need a bit of research to get the correct address in here to connect into Docker. When this setting is set to 1, Xdebug will always attempt to start a remote debugging session and try to connect to a client, even if the GET/POST/COOKIE variable was not present.So, using docker-compose, we now inject the local ini file into the php container’s conf.d directory. Normally you need to use a specific HTTP GET/POST variable to start remote debugging (see Step Debugging). The solution to let it work everytime was to add following: xdebug.remote_autostart=1

#Phpstorm docker xdebug generator#

That was because the special cookie still was set in the normal browser store (cookie that was stored either from the Browser extension that I have already uninstalled, or from trying out the JetBrains Bookmarklets generator before writing the question). To be sure i tried to open it also in a private browser session and it wasn't working anymore. Actually I had already tried to restart the Docker Desktop App before writing the question, maybe at that point my configurations were at a wrong state.īut at the end the solution was: Restarting the PC. :/usr/local/etc/php/php.iniĪfter booting up my machine to investigate further with the comments of and without changing anything, opening localhost:8080 suddenly let the debugging work by stoping at the breakpoint that i have set. I ended up at least to have separate containers, one as dev container with enabled Xdebug.

#Phpstorm docker xdebug install#

For the debugger session I have also tried to install a browser extension that sets a cookie. I think the problem is either something with the ports that I don't understand, or it is something with the debugger session not being started or recognized. Troubleshooting common PHP debugging issues.Xdebug & Zend Debugger bookmarklets generator for PhpStorm.Zero-configuration Web Application Debugging with Xdebug and PhpStorm.

Setting up Xdebug with Docker Compose and WordPress image.

I've tried many things trying to let work Xdebug in a Docker container.