Capazon 0.2.0 is out. There’s only one new feature: support for Capistrano 2.0. There’s no backwards compatibility. If you’re still on Capistrano 1.4.x, please don’t upgrade. It won’t work.
To update Capazon:
gem install capazon
Changes
Capistrano 2.0 has support for Rake-like namespaces, so I’ve moved all tasks provided by Capazon to the ec2 namespace:
$ cap ec2:describe_images
* executing `ec2:describe_images'
IMAGE ami-0386636a rbuilder-online/nuxleus-1.3-x86_9327.img.manifest.xml 099034111737 available true
IMAGE ami-0683666f rbuilder-online/fedoracore6-1.0-x86_9677.img.manifest.xml 099034111737 available true
[...]To call these tasks from another namespace in a Capistrano recipe:
namespace :whatever do
task :something_cool do
[...]
ec2.describe_images
[...]
end
endCapistrano 2.0
Turns out updating extensions to work w/ Capistrano 2.0 is extremely easy. Just replace blocks like this:
Capistrano.configuration(:must_exist).load do
task :take_over_the _world do
[...]
end
end...with this:
Capistrano::Configuration.instance.load do do
task :take_over_the _world do
[...]
end
endFor more on upgrading your recipes to Capistrano 2, head over to the upgrade guide on Capistrano’s new website or this post on NubyOnRails. Happy capifying!


Comments
Leave a response