We are using a special value which will be automatically replaced with the IP address of Docker Host. For more possible values, click hereĬlient_host (remote_host in Xdebug 2): This is the address which Xdebug will try to contact using DGBP protocol when our php container receives a request to process a php script. XDEBUG_MODE: debug configures which Xdebug features should be enabled. It's basically the same configuration for the development environment with PHP and Nginx from the previous article, but we have added a few environment variables for the Xdebug configuration: XDEBUG_CONFIG: client_host= client_port=9003 The complete configuration looks like this: version: "3"
Let's take a look at php.ini located in the php folder for its use with Xdebug. You can see the Dockerfile here: FROM nginx:alpineĬOPY nginx/nf /etc/nginx/conf.dįastcgi_param SCRIPT_FILENAME $document_root/$fastcgi_script_name It's Dockerfile and settings did not change.
NginxĪs I said before, we will be using Nginx. You can also add copying of custom php.ini file in the end of Dockerfile, but we can setup everything we will need with the use of Environment variables in docker-compose.yml. You can find out more about this command here. The only thing we have to install is Xdebug, and then enable it with the docker-php-ext-enable helper command. In Debian, they are present without any work. Xdebug depends on some libraries, which would have to be installed manually, if we would use Alpine. Instead of using the Alpine version of php-fpm image, we are using the default php-fpm image with Debian for simplicity. Let's start by modifying PHP Dockerfile: FROM php:fpm We'll be using PHP with Nginx, just like in our previous article. In our case, we will be using Visual Studio Code with PHP Tools. On the picture below, you can see a very simplified pipeline of execution: that's what we're going to build in this tutorial.Īfter a request to our docker container, Xdebug will initiate a connection with our IDE. Debugging is a way to pause the execution of codeto see what's going on. We will be using our php+nginx setup from the last article and you can find all the source codes for this one at github Xdebug In this article, we'll continue our discussion about development environments - more specifically, we will talk about debugging with the help of PHP Tools inside Visual Studio Code. In the previous article, we learned how to create two connected containers with php and nginx with the help of Docker compose, and we also talked about different environments where your software needs to work. Welcome to the third article of PHP on Docker.
0 kommentar(er)
