// deploy.php
require 'vendor/deployer/recipes/cachetool.php';
- cachetool (optional): accepts a string with the unix socket or ip address to php5-fpm. If
cachetool
is not given, then the application will look for acachetool.yml
file and read the configuration from there.
// deploy.php
set('cachetool', '/var/run/php5-fpm.sock');
// or
set('cachetool', '127.0.0.1:9000');
You can also specify different cachetool settings for each server:
// deploy.php
server('staging', 'staging.example.com', 22)
->set('cachetool', '127.0.0.1:9000');
server('production', 'production.example.com', 22)
->set('cachetool', '/var/run/php5-fpm.sock');
By default, if no env setting is provided, this recipe will fallback to the global setting.
cachetool:clear:apc
Clears APC system cachecachetool:clear:opcache
Resets the contents of the opcode cache
Since APC and OPcache deal with compiling and caching files, they should be executed right after the symlink is created for the new release:
// deploy.php
after('deploy:symlink', 'cachetool:clear:opcache');
// or
after('deploy:symlink', 'cachetool:clear:apc');
Read more information about cachetool on the website: http://gordalina.github.io/cachetool/