Framework Configuration Reference (FrameworkBundle)
Warning: You are browsing the documentation for Symfony 3.x, which is no longer maintained.
Read the updated version of this page for Symfony 7.1 (the current stable version).
The FrameworkBundle defines the main framework configuration, from sessions and
translations to forms, validation, routing and more. All these options are
configured under the framework
key in your application configuration.
1 2 3 4 5
# displays the default config values defined by Symfony
$ php bin/console config:dump-reference framework
# displays the actual config values used by your application
$ php bin/console debug:config framework
Note
When using XML, you must use the http://symfony.com/schema/dic/symfony
namespace and the related XSD schema is available at:
https://symfony.com/schema/dic/symfony/symfony-1.0.xsd
Configuration
secret
type: string
required
This is a string that should be unique to your application and it's commonly used to add more entropy to security related operations. Its value should be a series of characters, numbers and symbols chosen randomly and the recommended length is around 32 characters.
In practice, Symfony uses this value for encrypting the cookies used in the remember me functionality and for creating signed URIs when using ESI (Edge Side Includes).
This option becomes the service container parameter named kernel.secret
,
which you can use whenever the application needs an immutable random string
to add more entropy.
As with any other security-related parameter, it is a good practice to change this value from time to time. However, keep in mind that changing this value will invalidate all signed URIs and Remember Me cookies. That's why, after changing this value, you should regenerate the application cache and log out all the application users.
http_method_override
type: boolean
default: true
This determines whether the _method
request parameter is used as the
intended HTTP method on POST requests. If enabled, the
Request::enableHttpMethodParameterOverride
method gets called automatically. It becomes the service container parameter
named kernel.http_method_override
.
See also
For more information, see How to Change the Action and Method of a Form.
Caution
If you're using the AppCache Reverse Proxy
with this option, the kernel will ignore the _method
parameter,
which could lead to errors.
To fix this, invoke the enableHttpMethodParameterOverride()
method
before creating the Request
object:
1 2 3 4 5 6 7 8
// web/app.php
// ...
$kernel = new AppCache($kernel);
Request::enableHttpMethodParameterOverride(); // <-- add this line
$request = Request::createFromGlobals();
// ...
trusted_proxies
The trusted_proxies
option was removed in Symfony 3.3. See How to Configure Symfony to Work behind a Load Balancer or a Reverse Proxy.
ide
type: string
default: null
Symfony turns file paths seen in variable dumps and exception messages into
links that open those files right inside your browser. If you prefer to open
those files in your favorite IDE or text editor, set this option to any of the
following values: phpstorm
, sublime
, textmate
, macvim
and emacs
.
Note
The phpstorm
option is supported natively by PhpStorm on MacOS,
Windows requires PhpStormProtocol and Linux requires phpstorm-url-handler.
If you use another editor, the expected configuration value is a URL template
that contains an %f
placeholder where the file path is expected and %l
placeholder for the line number (percentage signs (%
) must be escaped by
doubling them to prevent Symfony from interpreting them as container parameters).
1 2 3
# app/config/config.yml
framework:
ide: 'myide://open?url=file://%%f&line=%%l'
Since every developer uses a different IDE, the recommended way to enable this
feature is to configure it on a system level. This can be done by setting the
xdebug.file_link_format
option in your php.ini
configuration file. The
format to use is the same as for the framework.ide
option, but without the
need to escape the percent signs (%
) by doubling them.
Note
If both framework.ide
and xdebug.file_link_format
are defined,
Symfony uses the value of the xdebug.file_link_format
option.
Tip
Setting the xdebug.file_link_format
ini option works even if the Xdebug
extension is not enabled.
Tip
When running your app in a container or in a virtual machine, you can tell
Symfony to map files from the guest to the host by changing their prefix.
This map should be specified at the end of the URL template, using &
and
>
as guest-to-host separators:
1 2 3 4
// /path/to/guest/.../file will be opened
// as /path/to/host/.../file on the host
// and /foo/.../file as /bar/.../file also
'myide://%f:%l&/path/to/guest/>/path/to/host/&/foo/>/bar/&...'
3.2
Guest to host mappings were introduced in Symfony 3.2.
test
type: boolean
If this configuration setting is present (and not false
), then the services
related to testing your application (e.g. test.client
) are loaded. This
setting should be present in your test
environment (usually via
app/config/config_test.yml
).
See also
For more information, see Testing.
default_locale
type: string
default: en
The default locale is used if no _locale
routing parameter has been
set. It is available with the
Request::getDefaultLocale
method.
See also
You can read more information about the default locale in How to Work with the User's Locale.
trusted_hosts
type: array
| string
default: []
A lot of different attacks have been discovered relying on inconsistencies
in handling the Host
header by various software (web servers, reverse
proxies, web frameworks, etc.). Basically, every time the framework is
generating an absolute URL (when sending an email to reset a password for
instance), the host might have been manipulated by an attacker.
See also
You can read "`HTTP Host header attacks`_" for more information about these kinds of attacks.
The Symfony Request::getHost()
method might be vulnerable to some of these attacks because it depends on
the configuration of your web server. One simple solution to avoid these
attacks is to whitelist the hosts that your Symfony application can respond
to. That's the purpose of this trusted_hosts
option. If the incoming
request's hostname doesn't match one of the regular expressions in this list,
the application won't respond and the user will receive a 400 response.
1 2 3
# app/config/config.yml
framework:
trusted_hosts: ['^example\.com$', '^example\.org$']
Hosts can also be configured to respond to any subdomain, via
^(.+\.)?example\.com$
for instance.
In addition, you can also set the trusted hosts in the front controller
using the Request::setTrustedHosts()
method:
1 2
// web/app.php
Request::setTrustedHosts(['^(.+\.)?example\.com$', '^(.+\.)?example\.org$']);
The default value for this option is an empty array, meaning that the application can respond to any given host.
See also
Read more about this in the Security Advisory Blog post.
form
enabled
type: boolean
default: false
Whether to enable the form services or not in the service container. If
you don't use forms, setting this to false
may increase your application's
performance because less services will be loaded into the container.
This option will automatically be set to true
when one of the child
settings is configured.
Note
This will automatically enable the validation.
See also
For more details, see Forms.
csrf_protection
See also
For more information about CSRF protection in forms, see How to Implement CSRF Protection.
enabled
type: boolean
default: true
if form support is enabled, false
otherwise
This option can be used to disable CSRF protection on all forms. But you can also disable CSRF protection on individual forms.
If you're using forms, but want to avoid starting your session (e.g. using
forms in an API-only website), csrf_protection
will need to be set to
false
.
esi
See also
You can read more about Edge Side Includes (ESI) in Working with Edge Side Includes.
enabled
type: boolean
default: false
Whether to enable the edge side includes support in the framework.
You can also set esi
to true
to enable it:
1 2 3
# app/config/config.yml
framework:
esi: true
fragments
See also
Learn more about fragments in the HTTP Cache article.
enabled
type: boolean
default: false
Whether to enable the fragment listener or not. The fragment listener is used to render ESI fragments independently of the rest of the page.
This setting is automatically set to true
when one of the child settings
is configured.
path
type: string
default: '/_fragment'
The path prefix for fragments. The fragment listener will only be executed when the request starts with this path.
profiler
enabled
type: boolean
default: false
The profiler can be enabled by setting this option to true
. When you
are using the Symfony Standard Edition, the profiler is enabled in the dev
and test
environments.
Note
The profiler works independently from the Web Developer Toolbar, see the WebProfilerBundle configuration on how to disable/enable the toolbar.
collect
type: boolean
default: true
This option configures the way the profiler behaves when it is enabled.
If set to true
, the profiler collects data for all requests (unless
you configure otherwise, like a custom matcher). If you want to only
collect information on-demand, you can set the collect
flag to false
and activate the data collectors manually:
1
$profiler->enable();
only_exceptions
type: boolean
default: false
When this is set to true
, the profiler will only be enabled when an
exception is thrown during the handling of the request.
only_master_requests
type: boolean
default: false
When this is set to true
, the profiler will only be enabled on the master
requests (and not on the subrequests).
dsn
type: string
default: 'file:%kernel.cache_dir%/profiler'
The DSN where to store the profiling information.
See also
See Switching the Profiler Storage for more information about the profiler storage.
matcher
Caution
This option is deprecated since Symfony 3.4 and will be removed in 4.0.
Matcher options are configured to dynamically enable the profiler. For instance, based on the ip or path.
See also
See How to Use Matchers to Enable the Profiler Conditionally for more information about using matchers to enable/disable the profiler.
request
formats
type: array
default: []
This setting is used to associate additional request formats (e.g. html
)
to one or more mime types (e.g. text/html
), which will allow you to use the
format & mime types to call
Request::getFormat($mimeType) or
Request::getMimeType($format).
In practice, this is important because Symfony uses it to automatically set the
Content-Type
header on the Response
(if you don't explicitly set one).
If you pass an array of mime types, the first will be used for the header.
To configure a jsonp
format:
1 2 3 4 5
# app/config/config.yml
framework:
request:
formats:
jsonp: 'application/javascript'
router
resource
type: string
required
The path the main routing resource (e.g. a YAML file) that contains the routes and imports the router should load.
type
type: string
The type of the resource to hint the loaders about the format. This isn't
needed when you use the default routers with the expected file extensions
(.xml
, .yml
/ .yaml
, .php
).
http_port
type: integer
default: 80
The port for normal http requests (this is used when matching the scheme).
https_port
type: integer
default: 443
The port for https requests (this is used when matching the scheme).
strict_requirements
type: mixed
default: true
Determines the routing generator behavior. When generating a route that has specific requirements, the generator can behave differently in case the used parameters do not meet these requirements.
The value can be one of:
true
- Throw an exception when the requirements are not met;
false
-
Disable exceptions when the requirements are not met and return
null
instead; null
- Disable checking the requirements (thus, match the route even when the requirements don't match).
true
is recommended in the development environment, while false
or null
might be preferred in production.
session
storage_id
type: string
default: 'session.storage.native'
The service id used for session storage. The session.storage
service
alias will be set to this service id. This class has to implement
SessionStorageInterface.
handler_id
type: string
default: 'session.handler.native_file'
The service id used for session storage. The session.handler
service
alias will be set to this service id.
You can also set it to null
, to default to the handler of your PHP
installation.
See also
You can see an example of the usage of this in How to Use PdoSessionHandler to Store Sessions in the Database.
name
type: string
default: null
This specifies the name of the session cookie. By default, it will use the
cookie name which is defined in the php.ini
with the session.name
directive.
cookie_lifetime
type: integer
default: null
This determines the lifetime of the session - in seconds. The default value
- null
- means that the session.cookie_lifetime
value from php.ini
will be used. Setting this value to 0
means the cookie is valid for
the length of the browser session.
cookie_path
type: string
default: /
This determines the path to set in the session cookie. By default, it will
use /
.
cache_limiter
type: string
or int
default: ''
If set to 0
, Symfony won't set any particular header related to the cache
and it will rely on the cache control method configured in the
session.cache-limiter PHP.ini option.
Unlike the other session options, cache_limiter
is set as a regular
container parameter:
1 2 3 4
# app/config/services.yml
parameters:
session.storage.options:
cache_limiter: 0
cookie_domain
type: string
default: ''
This determines the domain to set in the session cookie. By default, it's blank, meaning the host name of the server which generated the cookie according to the cookie specification.
cookie_secure
type: boolean
default: false
This determines whether cookies should only be sent over secure connections.
cookie_httponly
type: boolean
default: true
This determines whether cookies should only be accessible through the HTTP protocol. This means that the cookie won't be accessible by scripting languages, such as JavaScript. This setting can effectively help to reduce identity theft through XSS attacks.
gc_probability
type: integer
default: 1
This defines the probability that the garbage collector (GC) process is
started on every session initialization. The probability is calculated by
using gc_probability
/ gc_divisor
, e.g. 1/100 means there is a 1%
chance that the GC process will start on each request.
gc_maxlifetime
type: integer
default: 1440
This determines the number of seconds after which data will be seen as "garbage" and potentially cleaned up. Garbage collection may occur during session start and depends on gc_divisor and gc_probability.
save_path
type: string
default: %kernel.cache_dir%/sessions
This determines the argument to be passed to the save handler. If you choose the default file handler, this is the path where the session files are created. For more information, see Configuring the Directory where Session Files are Saved.
You can also set this value to the save_path
of your php.ini
by
setting the value to null
:
1 2 3 4
# app/config/config.yml
framework:
session:
save_path: ~
metadata_update_threshold
type: integer
default: 0
This is how many seconds to wait between updating/writing the session metadata. This can be useful if, for some reason, you want to limit the frequency at which the session persists, instead of doing that on every request.
enabled
type: boolean
default: true
Whether to enable the session support in the framework.
1 2 3 4
# app/config/config.yml
framework:
session:
enabled: true
use_cookies
type: boolean
default: null
This specifies if the session ID is stored on the client side using cookies or
not. By default, it will use the value defined in the php.ini
with the
session.use_cookies
directive.
assets
base_path
type: string
This option allows you to define a base path to be used for assets:
1 2 3 4 5
# app/config/config.yml
framework:
# ...
assets:
base_path: '/images'
base_urls
type: array
This option allows you to define base URLs to be used for assets. If multiple base URLs are provided, Symfony will select one from the collection each time it generates an asset's path:
1 2 3 4 5 6
# app/config/config.yml
framework:
# ...
assets:
base_urls:
- 'http://cdn.example.com/'
packages
You can group assets into packages, to specify different base URLs for them:
1 2 3 4 5 6 7
# app/config/config.yml
framework:
# ...
assets:
packages:
avatars:
base_urls: 'http://static_cdn.example.com/avatars'
Now you can use the avatars
package in your templates:
1
<img src="{{ asset('...', 'avatars') }}">
Each package can configure the following options:
version
type: string
This option is used to bust the cache on assets by globally adding a query
parameter to all rendered asset paths (e.g. /images/logo.png?v2
). This
applies only to assets rendered via the Twig asset()
function (or PHP
equivalent) as well as assets rendered with Assetic.
For example, suppose you have the following:
1
<img src="{{ asset('images/logo.png') }}" alt="Symfony!"/>
By default, this will render a path to your image such as /images/logo.png
.
Now, activate the version
option:
1 2 3 4 5
# app/config/config.yml
framework:
# ...
assets:
version: 'v2'
Now, the same asset will be rendered as /images/logo.png?v2
If you use
this feature, you must manually increment the version
value
before each deployment so that the query parameters change.
You can also control how the query string works via the version_format option.
Note
This parameter cannot be set at the same time as version_strategy
or json_manifest_path
.
Tip
As with all settings, you can use a parameter as value for the
version
. This makes it easier to increment the cache on each
deployment.
version_format
type: string
default: %%s?%%s
This specifies a sprintf pattern that will be used with the
version option to construct an asset's path. By default, the pattern
adds the asset's version as a query string. For example, if
version_format
is set to %%s?version=%%s
and version
is set to 5
, the asset's path would be /images/logo.png?version=5
.
Note
All percentage signs (%
) in the format string must be doubled to
escape the character. Without escaping, values might inadvertently be
interpreted as Service Container.
Tip
Some CDN's do not support cache-busting via query strings, so injecting
the version into the actual file path is necessary. Thankfully,
version_format
is not limited to producing versioned query
strings.
The pattern receives the asset's original path and version as its first
and second parameters, respectively. Since the asset's path is one
parameter, you cannot modify it in-place (e.g. /images/logo-v5.png
);
however, you can prefix the asset's path using a pattern of
version-%%2$s/%%1$s
, which would result in the path
version-5/images/logo.png
.
URL rewrite rules could then be used to disregard the version prefix before serving the asset. Alternatively, you could copy assets to the appropriate version path as part of your deployment process and forgot any URL rewriting. The latter option is useful if you would like older asset versions to remain accessible at their original URL.
version_strategy
type: string
default: null
The service id of the asset version strategy applied to the assets. This option can be set globally for all assets and individually for each asset package:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
# app/config/config.yml
framework:
assets:
# this strategy is applied to every asset (including packages)
version_strategy: 'app.asset.my_versioning_strategy'
packages:
foo_package:
# this package removes any versioning (its assets won't be versioned)
version: ~
bar_package:
# this package uses its own strategy (the default strategy is ignored)
version_strategy: 'app.asset.another_version_strategy'
baz_package:
# this package inherits the default strategy
base_path: '/images'
Note
This parameter cannot be set at the same time as version
or json_manifest_path
.
json_manifest_path
type: string
default: null
3.3
The json_manifest_path
option was introduced in Symfony 3.3.
The file path to a manifest.json
file containing an associative array of asset
names and their respective compiled names. A common cache-busting technique using
a "manifest" file works by writing out assets with a "hash" appended to their
file names (e.g. main.ae433f1cb.css
) during a front-end compilation routine.
Tip
Symfony's Webpack Encore supports outputting hashed assets. Moreover, this can be incorporated into many other workflows, including Webpack and Gulp using webpack-manifest-plugin and gulp-rev, respectively.
This option can be set globally for all assets and individually for each asset package:
1 2 3 4 5 6 7 8 9 10 11 12
# app/config/config.yml
framework:
assets:
# this manifest is applied to every asset (including packages)
json_manifest_path: "%kernel.project_dir%/web/assets/manifest.json"
packages:
foo_package:
# this package uses its own manifest (the default file is ignored)
json_manifest_path: "%kernel.project_dir%/web/assets/a_different_manifest.json"
bar_package:
# this package uses the global manifest (the default file is used)
base_path: '/images'
Note
This parameter cannot be set at the same time as version
or version_strategy
.
Additionally, this option cannot be nullified at the package scope if a global manifest
file is specified.
Tip
If you request an asset that is not found in the manifest.json
file, the original -
unmodified - asset path will be returned.
templating
hinclude_default_template
type: string
default: null
Sets the content shown during the loading of the fragment or when JavaScript is disabled. This can be either a template name or the content itself.
See also
See How to Embed Asynchronous Content with HInclude for more information about HInclude.
form
resources
type: string[]
default: ['FrameworkBundle:Form']
A list of all resources for form theming in PHP. This setting is not required if you're using the Twig format for your templates, in that case refer to the form article.
Assume you have custom global form themes in
src/WebsiteBundle/Resources/views/Form
, you can configure this like:
1 2 3 4 5 6
# app/config/config.yml
framework:
templating:
form:
resources:
- 'WebsiteBundle:Form'
Note
The default form templates from FrameworkBundle:Form
will always
be included in the form resources.
See also
See How to Work with Form Themes for more information.
cache
type: string
The path to the cache directory for templates. When this is not set, caching is disabled.
Note
When using Twig templating, the caching is already handled by the TwigBundle and doesn't need to be enabled for the FrameworkBundle.
engines
type: string[]
/ string
required
The Templating Engine to use. This can either be a string (when only one engine is configured) or an array of engines.
At least one engine is required.
loaders
type: string[]
An array (or a string when configuring just one loader) of service ids for templating loaders. Templating loaders are used to find and load templates from a resource (e.g. a filesystem or database). Templating loaders must implement LoaderInterface.
translator
enabled
type: boolean
default: false
Whether or not to enable the translator
service in the service container.
fallbacks
type: string|array
default: ['en']
This option is used when the translation key for the current locale wasn't found.
See also
For more details, see Translations.
logging
default: true
when the debug mode is enabled, false
otherwise.
When true
, a log entry is made whenever the translator cannot find a translation
for a given key. The logs are made to the translation
channel and at the
debug
for level for keys where there is a translation in the fallback
locale and the warning
level if there is no translation to use at all.
formatter
type: string
default: translator.formatter.default
The ID of the service used to format translation messages. The service class must implement the MessageFormatterInterface.
paths
type: array
default: []
This option allows to define an array of paths where the component will look for translation files.
default_path
3.4
The default_path
option was introduced in Symfony 3.4.
type: string
default: %kernel.project_dir%/translations
This option allows to define the path where the application translations files are stored.
property_access
magic_call
type: boolean
default: false
When enabled, the property_accessor
service uses PHP's
magic __call() method when
its getValue()
method is called.
throw_exception_on_invalid_index
type: boolean
default: false
When enabled, the property_accessor
service throws an exception when you
try to access an invalid index of an array.
property_info
enabled
type: boolean
default: false
validation
enabled
type: boolean
default: true
if form support is enabled,
false
otherwise
Whether or not to enable validation support.
This option will automatically be set to true
when one of the child
settings is configured.
cache
type: string
The service that is used to persist class metadata in a cache. The service has to implement the CacheInterface.
Set this option to validator.mapping.cache.doctrine.apc
to use the APC
cache provide from the Doctrine project.
enable_annotations
type: boolean
default: false
If this option is enabled, validation constraints can be defined using annotations.
translation_domain
type: string | false
default: validators
The translation domain that is used when translating validation constraint error messages. Use false to disable translations.
static_method
type: string | array
default: ['loadValidatorMetadata']
Defines the name of the static method which is called to load the validation metadata of the class. You can define an array of strings with the names of several methods. In that case, all of them will be called in that order to load the metadata.
strict_email
type: Boolean
default: false
If this option is enabled, the egulias/email-validator library will be used by the Email constraint validator. Otherwise, the validator uses a simple regular expression to validate email addresses.
annotations
cache
type: string
default: 'file'
This option can be one of the following values:
- file
- Use the filesystem to cache annotations
- none
- Disable the caching of annotations
- a service id
- A service id referencing a Doctrine Cache implementation
file_cache_dir
type: string
default: '%kernel.cache_dir%/annotations'
The directory to store cache files for annotations, in case
annotations.cache
is set to 'file'
.
debug
type: boolean
default: %kernel.debug%
Whether to enable debug mode for caching. If enabled, the cache will automatically update when the original file is changed (both with code and annotation changes). For performance reasons, it is recommended to disable debug mode in production, which will happen automatically if you use the default value.
serializer
enabled
type: boolean
default: false
Whether to enable the serializer
service or not in the service container.
cache
type: string
The service that is used to persist class metadata in a cache. The service
has to implement the Doctrine\Common\Cache\Cache
interface.
See also
For more information, see How to Use the Serializer.
enable_annotations
type: boolean
default: false
If this option is enabled, serialization groups can be defined using annotations.
See also
For more information, see How to Use the Serializer.
name_converter
type: string
The name converter to use.
The CamelCaseToSnakeCaseNameConverter
name converter can enabled by using the serializer.name_converter.camel_case_to_snake_case
value.
See also
For more information, see The Serializer Component.
circular_reference_handler
type string
The service id that is used as the circular reference handler of the default
serializer. The service has to implement the magic __invoke($object)
method.
See also
For more information, see The Serializer Component.
php_errors
log
3.2
The log
option was introduced in Symfony 3.2.
type: boolean
default: %kernel.debug%
Use the application logger instead of the PHP logger for logging PHP errors.
throw
3.2
The throw
option was introduced in Symfony 3.2.
type: boolean
default: %kernel.debug%
Throw PHP errors as \ErrorException
instances. The parameter
debug.error_handler.throw_at
controls the threshold.
cache
app
type: string
default: cache.adapter.filesystem
The cache adapter used by the cache.app
service. The FrameworkBundle
ships with multiple adapters: cache.adapter.apcu
, cache.adapter.doctrine
,
cache.adapter.system
, cache.adapter.filesystem
, cache.adapter.psr6
,
cache.adapter.redis
and cache.adapter.memcached
.
Tip
It might be tough to understand at the beginning, so to avoid confusion remember that all pools perform the same actions but on different medium given the adapter they are based on. Internally, a pool wraps the definition of an adapter.
system
type: string
default: cache.adapter.system
The cache adapter used by the cache.system
service. It supports the same
adapters available for the cache.app
service.
directory
type: string
default: %kernel.cache_dir%/pools
The path to the cache directory used by services inheriting from the
cache.adapter.filesystem
adapter (including cache.app
).
default_doctrine_provider
type: string
The service name to use as your default Doctrine provider. The provider is
available as the cache.default_doctrine_provider
service.
default_psr6_provider
type: string
The service name to use as your default PSR-6 provider. It is available as
the cache.default_psr6_provider
service.
default_redis_provider
type: string
default: redis://localhost
The DSN to use by the Redis provider. The provider is available as the cache.default_redis_provider
service.
default_memcached_provider
3.3
The default_memcached_provider
option was introduced in Symfony 3.3.
type: string
default: memcached://localhost
The DSN to use by the Memcached provider. The provider is available as the cache.default_memcached_provider
service.
pools
type: array
A list of cache pools to be created by the framework extension.
See also
For more information about how pools works, see cache pools.
To configure a Redis cache pool with a default lifetime of 1 hour, do the following:
1 2 3 4 5 6 7
# app/config/config.yml
framework:
cache:
pools:
cache.mycache:
adapter: cache.adapter.redis
default_lifetime: 3600
name
type: prototype
Name of the pool you want to create.
Note
Your pool name must differ from cache.app
or cache.system
.
adapter
type: string
default: cache.app
The service name of the adapter to use. You can specify one of the default
services that follow the pattern cache.adapter.[type]
. Alternatively you
can specify another cache pool as base, which will make this pool inherit the
settings from the base pool as defaults.
Note
Your service MUST implement the Psr\Cache\CacheItemPoolInterface
interface.
provider
type: string
Overwrite the default service name or DSN respectively, if you do not want to
use what is configured as default_X_provider
under cache
. See the
description of the default provider setting above for the type of adapter
you use for information on how to specify the provider.
clearer
type: string
The cache clearer used to clear your PSR-6 cache.
See also
For more information, see Psr6CacheClearer.
prefix_seed
3.2
The prefix_seed
option was introduced in Symfony 3.2.
type: string
default: null
If defined, this value is used as part of the "namespace" generated for the
cache item keys. A common practice is to use the unique name of the application
(e.g. symfony.com
) because that prevents naming collisions when deploying
multiple applications into the same path (on different servers) that share the
same cache backend.
It's also useful when using blue/green deployment strategies and more generally, when you need to abstract out the actual deployment directory (for example, when warming caches offline).
lock
type: string
| array
The default lock adapter. If not defined, the value is set to semaphore
when
available, or to flock
otherwise. Store's DSN are also allowed.
enabled
type: boolean
default: true
Whether to enable the support for lock or not. This setting is
automatically set to true
when one of the child settings is configured.
resources
type: array
A list of lock stores to be created by the framework extension.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
# app/config/config.yml
framework:
# these are all the supported lock stores
lock: ~
lock: 'flock'
lock: 'semaphore'
lock: 'memcached://m1.docker'
lock: ['memcached://m1.docker', 'memcached://m2.docker']
lock: 'redis://r1.docker'
lock: ['redis://r1.docker', 'redis://r2.docker']
lock: '%env(MEMCACHED_OR_REDIS_URL)%'
# named locks
lock:
invoice: ['redis://r1.docker', 'redis://r2.docker']
report: 'semaphore'
name
type: prototype
Name of the lock you want to create.
Tip
If you want to use the `RetryTillSaveStore` for non-blocking locks, you can do it by decorating the store service:
1 2 3 4
lock.invoice.retry_till_save.store:
class: Symfony\Component\Lock\Store\RetryTillSaveStore
decorates: lock.invoice.store
arguments: ['@lock.invoice.retry_till_save.store.inner', 100, 50]
workflows
type: array
A list of workflows to be created by the framework extension:
1 2 3 4 5
# app/config/config.yml
framework:
workflows:
my_workflow:
# ...
See also
See also the article about using workflows in Symfony applications.
enabled
type: boolean
default: false
Whether to enable the support for workflows or not. This setting is
automatically set to true
when one of the child settings is configured.
name
type: prototype
Name of the workflow you want to create.
initial_place
type: string
default: null
One of the places
or null
. If not null and the supported object is not
already initialized via the workflow, this place will be set.
marking_store
type: array
Each marking store can define any of these options:
arguments
(type:array
)service
(type:string
)type
(type:string
possible values:'multiple_state'
or'single_state'
)
supports
type: string
| array
The FQCN (fully-qualified class name) of the object supported by the workflow configuration or an array of FQCN if multiple objects are supported.
support_strategy
type: string
transitions
type: array
Each marking store can define any of these options:
from
(type:string
orarray
) value from theplaces
, multiple values are allowed for bothworkflow
andstate_machine
;guard
(type:string
) an ExpressionLanguage compatible expression to block the transition;name
(type:string
) the name of the transition;to
(type:string
orarray
) value from theplaces
, multiple values are allowed only forworkflow
.
type
type: string
possible values: 'workflow'
or 'state_machine'
Defines the kind of workflow that is going to be created, which can be either a normal workflow or a state machine. Read this article to know their differences.