...
Existing concepts FAQ
Settings
New-style settings:
In a single yml file: ezpublish.yml for eZ Publish, config.yml for other bundles (it is possible to import other files from here as well).
Note that it's possible to specialize settings for specific environments (e.g.ezpublish_dev.yml
,config_dev.yml
)3 scopes (global == override; extension scope is gone)
Order of precedence between extensions (bundles) is set by bundle loading order.
Runtime siteaccess configuration is resolved through the ConfigResolver service.
- Some notes about generic (non-eZ) settings for Symfony
- Symfony supports 3 formats for config files: yml, xml, php (eZ recommends yml)
- A single configuration file exists: config.yml (at least, in the final, compiled version, many files exist on disk)
- A configuration file can include another one via the imports statement (e.g.
config_dev.yml
would importconfig.yml
) - When creating a bundle, it is not sufficient to add a config file to it, the developer needs to specify that it is to be loaded (either via an import statement from app/config/config.yml or via a ServiceContainer extension in php).
Note that if you use the generator bundle command, all needed code will be automatically generated for you.
Siteaccesses
See http://confluence.ez.no/display/EZPEZP52/Siteaccess+Matching
Mostly unchanged
Better way of not duplicating settings: "groups" of siteaccesses
- Siteaccess settings specializes siteaccess group settings.
New way to define siteaccess: via environment variable (super-fast)
...