Manage PHP versions, extensions, and FPM settings.
Multiple PHP versions can run side by side on one server. Each application selects a PHP-FPM version while the server also has a default PHP version for command-line tools.
Use Services → Install software to add a supported PHP release. After installation, set the server-wide CLI default or select the version on an individual PHP application.
Changing an application's version updates its managed Nginx and PHP-FPM configuration. Verify that the target version has every extension required by the application before switching production traffic.
The PHP service detail shows loaded PHP and Zend extensions and the configuration file that loaded each one. Extension availability can differ between PHP versions.
Configure the defaults applied to newly created PHP applications, including supported php.ini values, OPcache capacity, and PHP-FPM pool behavior. Existing applications keep their effective configuration until you update them.
An application can override supported php_value, php_admin_value, and process-manager settings. ServerChirp validates values and reconciles the resulting pool configuration through the agent.
Typical settings include:
memory_limit = 512M
max_execution_time = 60
upload_max_filesize = 64M
post_max_size = 64MUse application overrides when one workload needs different limits. Use server defaults when the value should apply consistently to future PHP applications.
OPcache sizing is a server capacity decision. If the cache is consistently full, increase its memory only after confirming that the server has enough unused RAM. A larger cache that forces swapping can make the application slower, not faster.