Meza has many configuration options. This page is a work in progress to start documenting all of them. A good place to look is
/opt/meza/config/core/defaults.yml) for all the available options.
- Default: True
- Whether to use development or production settings for this server. Production being as performant and secure as possible, and development being less secure and providing optional features useful for dev.
- At present this only impacts Opcache, but is expected to be used for other settings in the future.
True(i.e. on production systems). This means you must reset the OPcache manually or restart the webserver for changes to the filesystem to take effect. In other words, if you edit live on production, Apache won't even see your changes unless you restart/reload the webserver using
sudo systemctl reload httpd.
opcache.log_verbosity_level(production less verbose)
php_opcache_memory_consumption: default = 256. The OPcache shared memory storage size.
php_opcache_interned_strings_buffer: default = 16. The amount of memory for interned strings in Mbytes
php_opcache_max_accelerated_files: default = 28001. The number of files Opcache will track. This is probably excessively high, but is enough to make sure all MediaWiki and a large number of local extensions will be covered.
php_opcache_revalidate_freq: default = 0. How often (in seconds) to check file timestamps for changes to the shared memory storage allocation. ("1" means validate once per second, but only once per request. "0" means always validate.
Additional PHP settingsEdit
php_max_input_vars: default = 2000. How many input variables may be accepted (limit is applied to $_GET, $_POST and $_COOKIE superglobal separately). Can be used for example to increase how many inputs a form from Extension:PageForms can handle
Note: Analysis of varying these settings within a Meza system is underway and will be published here at a later date.