ddev: apache-cgi gets inappropriately configured and Xdebug cannot be enabled if php7.2-ldap is added (v1.14.2, PHP 7.2, apache-fpm)

Describe the bug I use Xdebug on a daily basis, and usually enable it using ddev exec enable_xdebug. Today, I haven’t been able to activate it properly using the following configuration:

name: project
type: php
docroot: public
php_version: "7.2"
webserver_type: apache-fpm
router_http_port: "80"
router_https_port: "443"
additional_hostnames: []
additional_fqdns: []
mysql_version: "5.7"
provider: default
webimage_extra_packages: [php7.2-ldap]
use_dns_when_possible: true

To Reproduce Steps to reproduce the behavior:

  1. Start the project
  2. Check whether XDebug is enabled using phpinfo
  3. Start a SSH terminal using ddev ssh
  4. Call enable_xdebug
  5. Check whether XDebug is enabled using phpinfo

Expected behavior Xdebug should be enabled not, but it is not

This works properly after changing to nginx-fpm, but I’d like to use Apache as this is closer to the live environment

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 21 (21 by maintainers)

Most upvoted comments

I’m able to recreate your situation by adding webimage_extra_packages: [php7.2-ldap], so yay!

My bet is that this only occurs when a major new PHP release has happened since the ddev version in use, and that the cascading list of things that have to be installed with php7.2-ldap ends up breaking something about the config. I don’t think it should be too hard to chase down, and imaging that it can be recreated by a manual update of php7.2-ldap.

Changed the title to represent the situation. Thanks so much for your patience in unraveling this!

I imagine that you wouldn’t have trouble with https://github.com/drud/ddev/releases/tag/v1.15-rc1 because it has newer images. Also, it has php7.2-ldap from the beginning, but even if using some other extension that required a cascading set of changes it would probably not demonstrate this, because there’s nothing that big.

But a couple of months after the release of v1.15, this would probably happen again. It will be good to sort it out.