I noticed Xdebug 2.9 is installed on the dev containers. But Xdebug 3 ini settings are used. May I suggest installing:

• Xdebug 3.1 on the php72 containers
• Xdebug 3.3 on the php82 containers

See: https://xdebug.org/docs/compat for a version compatibility (and maintenance window) matrix

The clear advantage is that we can use the same xdebug.ini settings for both PHP flavors. Quite a lot of config settings changed between Xdebug 2 and 3.

Hi!

I could not help myself, and had to give the DevConf based Stepup dev-env a spin! My use case was to debug an issue we encountered in Stepup-Gateway. But that's not important now.

After a quite streamlined setup, only hindered by a missing Yubico config file and a local occupant on port 80, I had a running Stepup dev env with Gateway serving my local code 🦾

I did however noticed that Xdebug was not enabled on the gateway-dev image. After investigating, I noticed that Xdebug was installed, but not enabled.

The && docker-php-ext-enable xdebug portion of the code pasted below is not executed. Suggesting the pecl install command returned a non-zero response. Should be an easy fix by making it into a twoliner, or by using the ; separator?

RUN pecl install xdebug-2.9.0 && docker-php-ext-enable xdebug

https://github.com/OpenConext/OpenConext-BaseContainers/blob/ee516e9b3f89b5ef9da54095f64dcb0374779ab0/php72-apache2-node16-composer2/Dockerfile#L8C1-L8C62