Environment configuration as provided by Symfony was enhanced as=
of eZ Publish 5.2 and eZ Publish Community Project 2013.06 to allow specif=
ying this in the virtual host configuration.
You can configure several e=
nvironments, from production, development or staging, even if for each one =
of them you need require using different configurations sets.
For example, using apache, in the VirtualHost example in th=
e Virtual host setup chapte=
r the required VirtualHost configurations have been already in=
cluded. You can switch to the desired environment by setting the ENVI=
RONMENT environment variable to "prod", "dev" or other custom value, as you can see in the following example:
# Environment.
# Possible values: "prod" and "dev" out-of-the-box, other values possib=
le with proper configuration (described below)
# Defaults to "prod" if omitted
SetEnv ENVIRONMENT "prod"=20
If you want to use a custom environment (something else then "prod=
" and "dev") the next step is to create the dedicated c=
onfiguration files for your environment:
ezpublish/config/config_<env_name>.ymlezpublish/config/ezpublish_<env_name>.ymlThe name used as <env_name>=
will be the one that can be used as value of the ENVIRONMENT =
environment variable.
Those files must import the main configuration file, just like the defau=
lt config_dev.yml already does. Here's an example:
imports:
- { resource: config.yml }=20
This allows you to override settings defined in the main configuration f= ile, depending on your environment (like the DB settings or any other setti= ng you may want to override).