Ibexa DXP configuration is delivered using a number of dedicated configuration files. It contains everything from selecting the content Repository to SiteAccesses to language settings.
The recommended configuration format is YAML. It is used by default in the kernel (and in examples throughout the documentation). However, you can also use XML or PHP formats for configuration.
Configuration files are located in the
Configuration is provided per package in the
and routes are defined per package in
config/packages/ibexa.yaml contains basic configuration.
It stores, among others, SiteAccess information and content view config.
Other configuration is provided in respective files, e.g.
Configuration can be made environment-specific using separate folders for each environment. These files contain additional settings and point to the general (not environment-specific) configuration that is applied in other cases.
New configuration files
It is good practice to provide your own configuration in separate files.
Any YAML files placed in the
config/packages folder is automatically included in the system configuration.
Read more about how configuration is handled in Symfony.
Avoid using special characters in your configuration files. More specifically, don't use Unicode characters from the "Other" (
C) categories, such as control or format characters.
Make sure your IDE displays them.
Be careful when copy-pasting text from a word processing software or a PDF, because it might contain hidden characters like the soft hyphen.
Basic configuration handling in Ibexa DXP is similar to what is commonly possible with Symfony. You can define key/value pairs in your configuration files.
Internally and by convention, keys follow a dot syntax, where the different segments follow your configuration hierarchy. Keys are usually prefixed by a namespace corresponding to your application. All kinds of values are accepted, including arrays and deep hashes.
For configuration that is meant to be exposed to an end-user (or end-developer), it's usually a good idea to also implement semantic configuration.
Note that you can also implement SiteAccess-aware semantic configuration.
1 2 3 4 5 6
For specific configuration settings, see: