-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation regarding configuration. #241
Comments
This is indeed very confusing, especially if one for example wanted to use unix sockets instead of TCP. |
It would indeed be good to have this documented better -- I think the appropriate place would be a Either adjusting or removing the Docker-provided configuration should be totally fine. I believe the rationale for us using |
See also #498 for another minor bit that ought to be included in such a docs PR, namely that |
Any reason why zz- prefix is preferred instead of numeric prefix for config file ordering? |
To make sure it comes after alphabetic configuration files (since [a-z]
sorts lower than 0 lexicographically).
|
@aleskinen if we look at their values, I think that should be a little more clear: $ docker run --rm php:7.4-fpm sh -c "grep -rn 'listen =' /usr/local/etc/php-fpm.d/*.conf"
/usr/local/etc/php-fpm.d/www.conf:36:listen = 127.0.0.1:9000
/usr/local/etc/php-fpm.d/zz-docker.conf:5:listen = 9000 The one in Lines 3 to 39 in a80762e
The This also makes it trivial for someone who wants the stock upstream configuration to revert to it (by deleting |
Any reason why 9000 port is used here as a default? Since this is infra detail I would really recommend we use some other port. This way we need to change xdebug port for every project which has php-fpm setup. |
XDebug changed its port to |
The configuration in
/usr/local/etc/php-fpm.d/
is a bit unclear to me:What is the purpose of
zz-docker.conf
anddocker.conf
why are there 2 files?Is this so that
docker.conf
gets includes before andzz-docker.conf
after the pool configuration?If that's the case doesn't it make sense to use
aa-docker.conf
for consistency?Why would we always want to force the
[www]
pool to listen on[::]:9000
?It would be great if some documentation could be added regarding best / expected practices for changing configuration.
The text was updated successfully, but these errors were encountered: