magicalgre.blogg.se - Download docker compose xdebug

To get started, make sure you have Docker installed on your system, and then clone this repository. You can view the full article that inspired this repo here. Here is how to test and check everything in this setup.Forked from aschmelyun/docker-compose-laravel and added xdebugĪ pretty simplified Docker Compose workflow that sets up a LEMP network of containers for local Laravel development. When everything goes well this section is not important, but as always you may run into some problems (like I do). That's all now you should be able to run your PHP code with the debugger attached to the selected line.

This issue is discussed on the official Github repo where you may find some useful comments related to the automatic changing the root dir. You may have multiple projects with the same path on a server but different paths in the local environment. In case of Vim there is one small problem. Probably some similar option is available in any other decent debugger. Path_maps is a useful option which lets you view your remote files mapped on the local path so you can view and edit them while still working inside the debugger view. Which should be appended to the ~/.vimrc file. \ '/app/web/': '/Users/jmarceli/Work/wordpress/my_site/web/' etc/php/development.ini (path relative to the docker-compose.yml location).

But for the container which I am using it is located inside. Normally you would define the configuration inside php.ini file (e.g.

Depending on user action, debugger sends back some instructions to the Xdebug on the same port on which Xdebug connects with the debugger.

Debugger takes the control over code execution.

If The server manages to connect with the debugger (the debugger is listening on given IP and port number) it stops script execution.

Based on that configuration The server tries to connect with Your local computer on the given IP and port number.

The server checks a configuration of the Xdebug to find out the connection details.

The server tries to connect to your debugger via DBGP protocol.

You run PHP script or make a request to a website.

Your local computer starts listening on 9000 port (by default).

You start DBGP session in your debugger (Vim or some IDE like PHPStorm).

While not beeing a Xdebug nor DBGP protocol expert I see this architecture/communication as follows: So there is no need to publish it, your computer will never try to connect to the Xdebug via 9000 port. Docker run -p 9000:9000 your_xdebug_server_imageīecause Xdebug (which is running on your container/server) doesn't listen on that port, it just sends some data to that port (to your computer on which you are working).