Allow for multiple php-fpm services to be run in downstream containers.

[nigelgbanks]

This doesn't really change anything functionally in this container but allows for downstream containers to run multiple php-fpm services if needed.

One may want to run multiple php-fpm services so they can include/exclude php extensions like xdebug dynamically. In this scenario two php-fpm services are running one with xdebug loaded and the other without.

nginx then looks at the cookies of requests, if it finds a XDEBUG_SESSION cookie it forwards the request on the the php-fpm socket/service which has xdebug enabled otherwise it passes the request to the php-fpm socket/service with xdebug disabled.

Why would one do this? xdebug really kills performance and can cause failures due to timeouts even when not running, just by having the module enabled (this includes having profiling disabled, auto debug and remote debugging disabled).

Changes inspired by this article: https://jtreminio.com/blog/developing-at-full-speed-with-xdebug/

N.B. Food for thought, maybe split up php/nginx container into two. Which would allow for running multiple php containers and have them communicate over tcp rather than sockets. Though no small feat lots of changes required but ultimately might be more flexible for developers.

[dannylamb]

I see what you're getting at. I can't say I understand 💯 but I can definitely test and merge for you.

[dannylamb]

No explosions. Let's pull it in.

[dannylamb]

👍