mmm yes is a typo, but that's not the cause of malfunctioning
Look another example of this behaviour, just one stripped version of some deploy I'm building now:
Capfile:
require 'capistrano/setup'
require 'capistrano/deploy'
Dir.glob('lib/capistrano/tasks/*.rake').each { |r| import r }
config/deploy.rb
lock '3.2.1'
set :application, 'my_app_name'
set :repo_url, 'asecretrepo.git'
namespace :deploy do
desc 'Installs missing software'
task :install do
puts "Begin install"
end
end
#after 'deploy:install', 'base:install' # this will work here if uncommented
lib/capistrano/tasks/base.rake
namespace :base do
desc "base install"
task :install do
on roles(:all) do
puts 'aptitude update'
end
end
end
after 'deploy:install', 'base:install' # this won't work here
This as it is, gives simply on a cap -vT
$ cap -vT
cap aborted!
Don't know how to build task 'deploy:install'
/home/carlos/capifu/lib/capistrano/tasks/base.rake:10:in `<top (required)>'
But
if you comment after in the rake task and uncomment the one in the
config/deploy.rb it'll work as expected. But makes more sense specify
the after/before hooks within the taks we want to be fired and not in
another file.
Could this bi a limitation of the chosen "rake" path? or there's another way to do this?