In some situation, we need to override default values for specific pools or php version, to enable either custom php modules (version-specific) or account-specific directives.
The per-account is useful to preserve local modifications (like pm.max_children) when a user updates its php version.
I'm thinking of a mechanism based on the non-documented include directive.
The template (/etc/alternc/templates/php/fpm) could contain three directives:
include = /etc/alternc/php-fpm-custom/%%PHPVERSION%%.conf
include = /etc/alternc/php-fpm-custom/%%LOGIN%%.conf
include = /etc/alternc/php-fpm-custom/%%PHPVERSION%%-%%LOGIN%%.conf
Or theses directives could be added by the /usr/lib/alternc/php7-fpm if the file exists (not sure how include behave when the file is missing).
In some situation, we need to override default values for specific pools or php version, to enable either custom php modules (version-specific) or account-specific directives.
The per-account is useful to preserve local modifications (like pm.max_children) when a user updates its php version.
I'm thinking of a mechanism based on the non-documented
includedirective.The template (
/etc/alternc/templates/php/fpm) could contain three directives:Or theses directives could be added by the
/usr/lib/alternc/php7-fpmif the file exists (not sure how include behave when the file is missing).