To make this a little more convenient, we use dedicated make recipes for those actions in. docker/.envĭebug code executed via php-fpm, cli or from a workerįor code that is executed "directly" by a container without PhpStorm, we first need to enable xdebug in the container by removing the in front of the extension in /etc/php8/conf.d/zz-app-local.ini
Before, we have been using an SFTP Deployment configuration, which was kinda confusing ("What is SFTP doing here?"), so we will use an SSH Configuration instead and configure the path mappings in the Cli Interpreter interface SSH ConfigurationĪt File | Settings | Tools | SSH Configurations create a new SSH Configuration named "Docker PHP Tutorial" with the following settings We will configure a remote PHP interpreter that uses an SSH connection to run commands in the application container. # we use SSH deployment configuration in PhpStorm for local development # "sshd: no hostkeys available - exiting." # Required to start sshd, otherwise the container will error out on startup with the message See Fix Xdebug on PhpStorm when run from a Docker container for an explanation of the xdebug.client_host= setting (previously called xdebug.remote_host in xdebug &1 docker/images/php/base/conf.d/zz-app-local.ini We also don't want to enable xdebug immediately but only when we need it (due to the decrease in performance when the extension is enabled), hence we remove the default config file and disable the extension in the application. # ensure that xdebug is not enabled by default
#Phpstorm docker xdebug apk#
Install the extension via apk (only for the local target): docker/docker-compose/docker-compose-php-base.yml: docker/images/php/base/DockerfileįROM composer:$ as composerĬOPY -from=composer /usr/bin/composer /usr/local/bin/composerīecause we want our build to be deterministic, we "pin" the composer version by adding a COMPOSER_VERSION variable to the. In addition, composer needs the extensions mbstring and phar Install Tools Install composerĬomposer is installed by pulling the official composer docker image and simply "copying" the composer executable over to the base php image. This reduces complexity and removes any pesky warnings regarding "SSH keys being exposed in a repository". However, we will not use SSH keys any longer but simply authenticate via password. We will still rely on an always-running docker setup that we connect to via an SSH Configuration instead of using the built-in docker-compose capabilities as I feel it's closer to what we do in CI / production.
#Phpstorm docker xdebug update#
This article is an update of Setting up PhpStorm with Xdebug for local development on Docker but will also cover the "remaining cases" of debugging php-fpm and php worker processes. This tutorial was previously published on my personal blog at PhpStorm, Docker and Xdebug 3 on PHP 8.1 in 2022. You find the branch for this tutorial at part-4-2-phpstorm-docker-xdebug-3-php-8-1-in-2022.
#Phpstorm docker xdebug full#
There is also a Youtube video to guide you through the full processĪll code samples are publicly available in my Docker PHP Tutorial repository on github. We will also ensure that we can run PHPUnit tests from the command line as well as from PhpStorm. In this tutorial, we will set up our local dockerized PHP development environment to be used by PhpStorm and Xdebug.
A guide to debugging everything in PhpStorm (IDE, Browser, cli and workers)
0 kommentar(er)
