1. Customize PHP globally¶
PHP settings can be applied globally to all projects, but are bound to a specific PHP version. This means every PHP version can have its own profile of customized settings.
By default, all PHP container use roughly the same settings. This might only differ if some options or modules do not exist in a specific container.
Table of Contents
1.1. Configure PHP settings globally¶
PHP settings can either be applied in its
php.ini configuration file or through the
PHP-FPM configuration itself via
php.ini are also picked up by the PHP command line tool, whereas
php_flag settings are only valid for requests over the webserver.
This means you can set different values, when executing command line tasks and when the application is run through the browser.
1.1.1. Settings via php.ini¶
To configure PHP globally via php.ini follow the provided link:
1.1.2. Settings via php-fpm.conf¶
To configure PHP globally via PHP-FPM follow the provided link:
1.2. Configure non-overwritable settings globally¶
Settings defined via
php_flag are applied globally, however
they can still be overwritten by any project via the PHP function
If you want to create PHP settings and force them, so no application can accidentally or on purpose
overwrite them, you need to use
Keep in mind that those settings are not picked up by the command line execution of PHP, but only through the browser.
To configure PHP globally and non-overwritable via PHP-FPM follow the provided link:
1.3. Configure loaded PHP modules¶
.env file offers the option to specify what PHP modules to enable or disable specifically.
1.4. Configure PHP-FPM service¶
You can also configure the PHP-FPM service itself. Settings can be applied for the core service as well as for the pool. This is useful if you need to adjust performance settings such as number of running child processes, file- and memory limits, timeouts and many more.
Be sure to read up on the PHP-FPM documentation to understand what you are doing.