In this article we assume that you are familiar with The YAML Format and Configuration File Principles.
The config_handlers.yml configuration file describes the configuration handler classes used to parse and interpret all other YAML configuration files. The config_handlers.yml file links the handlers to the configuration files according to a file path.
path_to_yml_file: class: class_name file: path/to/class param: prefix: prefix_name module: <true | false>
Defines the YAML file to parse. The path to the file is defines related to the %SF_APP_DIR% directory. You can also use wildcard characters (*). By default there are defined these YAML files:
Defines YAML file parser class. The default config_handlers.yml file defines the parser classes as follows:
Defines the full path to handler class. When adding your own configuration handlers, you must specify both the class name and the full path to your handler source file under the class and the file entries respectively. This is required as the configuration is initialized before the autoloading mechanism in sfApplicationConfiguration.
Each configuration file is defined by a class and can be further customized by defining some parameters under the param section.
The settings of configuration files handled by sfDefineEnvironmentConfigHandler can be made available directly in the code via the sfConfig class. This handler adds the prefix to each of the setting names. Be careful not to choose a prefix already used by another handler. Existing prefixes are sf_, app_, and mod_.
Defines whether to add module name to the prefix. This option is available only for sfDefineEnvironmentConfigHandler class. Possible values: <true | false> Default: false