.. index:: single: Configuration Reference; Framework
This reference document is a work in progress. It should be accurate, but all options are not yet fully covered.
The FrameworkBundle contains most of the "base" framework functionality
and can be configured under the framework key in your application configuration.
This includes settings related to sessions, translation, forms, validation,
routing and more.
type: string default: UTF-8
The character set that's used throughout the framework. It becomes the service
container parameter named kernel.charset.
type: string required
This is a string that should be unique to your application. In practice,
it's used for generating the CSRF tokens, but it could be used in any other
context where having a unique string is useful. It becomes the service container
parameter named kernel.secret.
type: string default: null
If you're using an IDE like TextMate or Mac Vim, then Symfony can turn all of the file paths in an exception message into a link, which will open that file in your IDE.
If you use TextMate or Mac Vim, you can simply use one of the following built-in values:
textmatemacvim
You can also specify a custom file link string. If you do this, all percentage
signs (%) must be doubled to escape that character. For example, the
full TextMate string would look like this:
framework:
ide: "txmt://open?url=file://%%f&line=%%l"Of course, since every developer uses a different IDE, it's better to set
this on a system level. This can be done by setting the xdebug.file_link_format
PHP.ini value to the file link string. If this configuration value is set, then
the ide option does not need to be specified.
type: Boolean
If this configuration parameter 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). For more information, see :doc:`/book/testing`.
type: integer default: 0
This determines the lifetime of the session - in seconds. By default it will use
0, which means the cookie is valid for the length of the browser session.
default: { http: [], https: [] }
This option allows you to define base URL's to be used for assets referenced
from http and https pages. A string value may be provided in lieu of a
single-element array. If multiple base URL's are provided, Symfony2 will select
one from the collection each time it generates an asset's path.
For your convenience, assets_base_urls can be set directly with a string or
array of strings, which will be automatically organized into collections of base
URL's for http and https requests. If a URL starts with https:// or
is protocol-relative (i.e. starts with //) it will be added to both
collections. URL's starting with http:// will only be added to the
http collection.
.. versionadded:: 2.1
Unlike most configuration blocks, successive values for ``assets_base_urls``
will overwrite each other instead of being merged. This behavior was chosen
because developers will typically define base URL's for each environment.
Given that most projects tend to inherit configurations
(e.g. ``config_test.yml`` imports ``config_dev.yml``) and/or share a common
base configuration (i.e. ``config.yml``), merging could yield a set of base
URL's for multiple environments.
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:
.. configuration-block::
.. code-block:: html+jinja
<img src="{{ asset('images/logo.png') }}" alt="Symfony!" />
.. code-block:: php
<img src="<?php echo $view['assets']->getUrl('images/logo.png') ?>" alt="Symfony!" />
By default, this will render a path to your image such as /images/logo.png.
Now, activate the assets_version option:
.. configuration-block::
.. code-block:: yaml
# app/config/config.yml
framework:
# ...
templating: { engines: ['twig'], assets_version: v2 }
.. code-block:: xml
<!-- app/config/config.xml -->
<framework:templating assets-version="v2">
<framework:engine id="twig" />
</framework:templating>
.. code-block:: php
// app/config/config.php
$container->loadFromExtension('framework', array(
// ...
'templating' => array(
'engines' => array('twig'),
'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 assets_version value
before each deployment so that the query parameters change.
You can also control how the query string works via the assets_version_format option.
type: string default: %%s?%%s
This specifies a sprintf() pattern that will be used with the assets_version
option to construct an asset's path. By default, the pattern adds the asset's
version as a query string. For example, if assets_version_format is set to
%%s?version=%%s and assets_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 interpretted
as :ref:`book-service-container-parameters`.
Tip
Some CDN's do not support cache-busting via query strings, so injecting the
version into the actual file path is necessary. Thankfully, assets_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, we
cannot modify it in-place (e.g. /images/logo-v5.png); however, we 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.
.. configuration-block::
.. code-block:: yaml
framework:
# general configuration
charset: ~
secret: ~ # Required
ide: ~
test: ~
default_locale: en
trust_proxy_headers: false
# form configuration
form:
enabled: true
csrf_protection:
enabled: true
field_name: _token
# esi configuration
esi:
enabled: true
# profiler configuration
profiler:
only_exceptions: false
only_master_requests: false
dsn: sqlite:%kernel.cache_dir%/profiler.db
username:
password:
lifetime: 86400
matcher:
ip: ~
path: ~
service: ~
# router configuration
router:
resource: ~ # Required
type: ~
http_port: 80
https_port: 443
# session configuration
session:
auto_start: ~
storage_id: session.storage.native
name: ~
lifetime: 86400
path: ~
domain: ~
secure: ~
httponly: ~
# templating configuration
templating:
assets_version: ~
assets_version_format: "%%s?%%s"
assets_base_urls:
http: []
ssl: []
cache: ~
engines: # Required
form:
resources: [FrameworkBundle:Form]
# Example:
- twig
loaders: []
packages:
# Prototype
name:
version: ~
version_format: ~
base_urls:
http: []
ssl: []
# translator configuration
translator:
enabled: true
fallback: en
# validation configuration
validation:
enabled: true
cache: ~
enable_annotations: false
# annotation configuration
annotations:
cache: file
file_cache_dir: %kernel.cache_dir%/annotations
debug: true