See the Configuring your Application documentation for information on how to set up your preferred cache. If left unset, Vulnero will attempt to auto-detect the most efficient one available.
While it may be possible to run Vulnero without a cache, it is highly recommended not to — even on low traffic websites.
cache directory. This cache is separate from your bootstrap cache because it must be loaded prior to any bootstrapping in order to seed the Zend_Application object's initialization parameters.Retrieving the cache by bootstrapping it. For example, to access it from your controller:
public function visitAction()
{
$cache = $this->getInvokeArg('bootstrap')
->bootstrap('cache')
->getResource('cache');
$cache->load('key');
}
This would return a Zend_Cache factory front end cache. During bootstrapping, this is already going to be seeded to Zend_Db_Table, Zend_Date, and Zend_Locale as well as utilized throughout Vulnero.
Cache Backend Configuration, Time to Live and Other Options
The sample application includes a WordPress administration page (Vulnero icon on the left bar) that will show you the cache backends available to PHP. From here, you can select and configure any cache that you choose and this will be saved to the WordPress options and leveraged in your bootstrap. You can also manually setup caching in your application/config/config.ini which might be useful if you're doing any advanced setup (e.g.: multiple memcached instances).