Deployer tasks for Point Blue apps
Supporting deployer tasks
This will install the package globally
composer global require pointblue/deployer
- Edit the
php.inifor your command line environment at
VERSIONis something like
Find out your php cli version with
- Find composer's global path with
composer config --list --globaland find the property [home]. Append
/vendorto this property and use this path for the next step.
include_pathby appending the global composer's vendor path to the end of the string as
:/home/user/.config/composer/vendorand save the file.
include_path = ".:/usr/share/php:/home/ubuntu/.config/composer/vendor".
To use the deployer tasks, just require the tasks in your
deployer.php file at the top, but after other
//deployer's common tasks require 'recipe/common.php'; //Point Blue's deployter tasks require 'pointblue/deployer/common-tasks.php';
Next, add the hooks need for the tasks to run:
//right before release, call the point blue deployer hooks after('deploy:clear_paths', 'deploy:pb_deployer_post_hook');
To test commands without running them on the target server, use the
dep deploy:symlink_envs aws --pb-test -vvv
This will run the
deploy:symlink_envs task with the aws stage settings from the
servers.yml file and
print the symlink commands in the console instead of running them on the server. This will let you test
your configurations before deploying.
Some additional variables can be added to your hosts definition in the
env_symlinks - see
update_autoload_classmap - see
Please see the source code for task names and their use