Hey, I'm the author of the "original" issue: https://bugs.xdebug.org/view.php?id=2161#c6903

First of all, thank you. That would make lives of hundreds of developers much better :)

Second, there's a little concern: correct me if I'm wrong, but previously the connection was always initiated by PHP to the IDE. In a containerized environment, PHPStorm would even automatically specify the xdebug.client_host as host.docker.internal, so that the connection reaches the IDE. It doesn't require any additional configuration from either IDE or PHP side. With sockets, that'd no longer be the case: the socket file has to be bound from the container to host's filesystem so it can be accessed by an IDE. Additionally, IDEs would not be able to automate the configuration, as the path to the socket file would have to be specified by hand for every project. It's not a huge problem, but still something I noticed.

Anyways, do you want me to also create a ticket on PHPStorm's side so they can acknowledge the change and possibly start working on the integration? Thanks

I think there are a few things here, that I need to clarify:

• Each PHP request will have its own socket file.
• It is possible (for an IDE) to enumerate these sockets, like I do here: https://github.com/derickr/dbgp-tools/blob/master/xdebug/main.go#L77
• This only works if the IDE runs on the same host as Xdebug, or, you can run a small or binary script inside the host
• VS Code has experimental support, once that is merged, we can poke PhpStorm people
• Xdebug could also send the socket location in the init package, so that the IDE knows which one belongs to that running script. I've made a ticket for that: https://bugs.xdebug.org/view.php?id=2261