kernelservices.ini [ContainerSettings]
The block [ContainerSettings] of settings/kernelservices.ini, with 4 setting(s).
Never edit settings/kernelservices.ini itself: an update replaces it. Put the settings you change in an override, which wins over the shipped file:
settings/override/kernelservices.ini.append.phpfor every siteaccess,settings/siteaccess/<siteaccess>/kernelservices.ini.append.phpfor one siteaccess,extension/<extension>/settings/kernelservices.ini.append.phpin an extension (read when the extension is active).
Mode
These four are read before the extensions are active: set them here or in
settings/override/kernelservices.ini.append.php, not in an extension.compiled the web kernel applies the compiled container in CacheDir: the
extension activation of each siteaccess, recorded once, instead
of looking up every extension directory on every request (the
default). Without a compiled file, or when a request does not
start from exactly the recorded state, it runs as without a
container.
dev nothing compiled is used; services are read from the settings
as they stand (for development)
disabled the container takes no part in the boot; services can still be
asked for, read from the settings
Default: compiled.
# settings/override/kernelservices.ini.append.php
[ContainerSettings]
Mode=compiled
*/ ?>CacheDir
Where the compiled container lives, relative to the installation root:
index.php and one <siteaccess>.php per siteaccess.
Default: var/cache/kernelservices.
# settings/override/kernelservices.ini.append.php
[ContainerSettings]
CacheDir=var/cache/kernelservices
*/ ?>AutoRebuild
enabled a web request of a siteaccess without a current compiled file
records its own extension activation and writes it, so the next
request uses it (after an INI cache clear from the
administration, or before the first compile)
disabled only exp:services:compile, the deploy and ezcache.php on the
command line write it
Default: enabled.
# settings/override/kernelservices.ini.append.php
[ContainerSettings]
AutoRebuild=enabled
*/ ?>WorkerScope
The worker scope of the settings files: each settings file of a siteaccess
is built once per worker and handed out as a copy afterwards. On Exponential
Velocity a worker serves thousands of requests, so this saves loading every
settings file on every request; on PHP-FPM a worker is one request long.
auto on only when the INI cache does not check file times either
(EZP_INI_FILEMTIME_CHECK false in config.php), so a kept settings
file is exactly what loading it again would give (the default)
enabled always (an edited settings file then reaches a Velocity worker
with the next compile, INI cache clear or restart)
disabled never
Default: auto.
# settings/override/kernelservices.ini.append.php
[ContainerSettings]
WorkerScope=auto
*/ ?>Related
Generated by ./console exp:help:examples from settings/kernelservices.ini. Do not edit this page: change the source and generate again (how). Free documentation: GFDL 1.3 or later.