Yaf configurations could be merged with user configurations. The difference is, Yaf configurations are prefixed with "yaf." or "application.", if there are both "yaf." and "application.", "application." will be accepcted preferentially.
Example #1 An array of yaf configuration example
$configs = array(
"application" => array(
"directory" => dirname(__FILE__),
"dispatcher" => array(
"catchException" => 0,
"view" => array(
"ext" => "phtml",
$app = new Yaf_Application($config);
Example #2 an ini file of yaf configuration example
[yaf] yaf.directory = APPLICATION_PATH "/appliation" yaf.dispatcher.catchException = 0 [product : yaf] ; user configuartions list here
|application.library||application.directory . "/library"|
|application.library.directory||application.directory . "/library"|
|application.bootstrap||application.directory . "/Bootstrap" . application.ext|
Here's a short explanation of the configuration directives.
The directory of the application, that is the folder which contains the "controllers", "views", "models", "plugins" folders.
This config entry is the only one which doesn't has a default value, which means you should always define it.
The file ext of the PHP script, used in class autoloading( Yaf_Loader).
The file ext of the view template script.
A commaseparated list of the registered modules, used in the route process, especially while there are more than three segments in the PATH_INFO,
Yaf need a way to find out whether the first segment is a module name or not.
As of Yaf 2.1.6, this config entry can also be a array, when it is array, then the library path will try to use the value of application.library.directory
Introduced in Yaf 2.1.6
A comma separated prefix of local library namespace.
Introduced in Yaf 2.1.6
A absolute path of the Bootstrap class script.
Used to remove a fixed prefix of request uri in route process. Take a example, comes a request with request uri "/prefix/controller/action". if you set application.baseUri to "/prefix", then only "/controller/action" will take as the PATH_INFO in route process.
In generally, you have no need to set this value.
If this is On, Yaf will throw exception while some error occurring. see also Yaf_Dispatcher::throwException().
If this is On, Yaf will forward to Error controller, Error Action while there is a uncaught exception. see also Yaf_Dispatcher::catchException().
The default Route, if it is not specificed, Static route will be used as default route, see: Yaf_Router::addRoute().
The default module name, see also Yaf_Dispatcher::setDefaultModule().
The default controller name, see also Yaf_Dispatcher::setDefaultController().
The default action name, see also Yaf_Dispatcher::setDefaultAction().