The primary configuration is located at application/config/config.ini. This file is parsed, loaded and cached by Zend_Config_Ini as part of the bootstrapping process. By default, most settings are copied or cloned from WordPress. This includes things like database connection strings or your site URL, allowing much of your application's configuration to come directly from the WordPress administration panel.
Environment
By default, Vulnero will be running in the [development] environment. This environment has caching disabled, will display errors, and is generally unsuitable for production web sites but handy when debugging your code. To set your environment:
- Login to the WordPress administration area (http://yourdomain.com/wp-admin).
- Click the Vulnero link on the left-hand panel.
- Change the environment drop-down to your desired environment.
- Save changes.
The setting will be stored in WordPress' internal options table.
Caching
Several sections of the configuration file are commented out in blocks for cache drivers like Memcached, Apc and Sqlite. Vulnero will check for the fastest drivers first and attempt to make local connections by default. This can be expensive depending on how often and vigorously it has to check, so it's recommended to uncomment your preferred caching method.
Vulnero uses your cache in many areas such as caching the configuration file processing and other expensive bootstrapping items. The cache is made available as a bootstrap item for your controllers and views to leverage as well.
Routes
Routes are configured in application/config/routes.ini. All page requests not answered by these routes are passed on to WordPress; therefore, you must explicitly add routes for your application to this file. More information and examples on routing are discussed in the Adding Routes documentation.