$ cap deploy:check --file config/deploy.rb
the task `deploy:check' does not exist
$ cap --tasks deploy:check
cap deploy:check # Test deployment dependencies.
Extended help may be available for these tasks.
Type `cap -e taskname' to view it.
$
Is there an alternate way to specify which deploy file to use? Am I
missing something blindingly obvious? :-)
$ cap --version
Capistrano v2.5.19
$ ruby -v
ruby 1.8.7 (2009-06-12 patchlevel 174) [universal-darwin10.0]
TIA,
--
Hassan Schroeder ------------------------ hassan.s...@gmail.com
twitter: @hassan
Yours,
Tom
> --
> * You received this message because you are subscribed to the Google Groups "Capistrano" group.
> * To post to this group, send email to capis...@googlegroups.com
> * To unsubscribe from this group, send email to capistrano+...@googlegroups.com For more options, visit this group at http://groups.google.com/group/capistrano?hl=en
Yes, but that only works with the default "deploy.rb" file -- I need to be
able to specify alternate filenames for specific situations.
##
# SSH parameters
#
set :user, "wadus"
desc "Task for testing to load a config from other file"
task :config_file, :hosts => 'test-server.com' do
run "sleep 10"
end
> I cann't reproduce your error, I hope it give you some clues.
Thanks for the response but perhaps I didn't explain well, as I see no
relationship between your example and the problem.
To put it another way:
$ cap deploy:check
# works fine
* executing `deploy:check'
* executing "test -d /webapps/example/releases"
.....
command finished
You appear to have all necessary dependencies installed
$ cap deploy:check -f config/deploy_alternate.rb # fails
the task `deploy:check' does not exist
$
Does that work for anyone?
Yikes. For quite a while I've been using e.g.
$ cap deploy -f config/deploy_alternate.rb
: to specify the deployment target, and that works fine. But you're
saying that's just a fluke, and the fact that deploy:check and other
variants fail is expected?
Having to create 2 files instead of 1 -- Capfile.alternate, referencing
config/deploy_alternate.rb -- doesn't seem very DRY...
But OK, thanks for the clarification!
> - sounds like you should be using multistage?
Not having been aware of it before -- yes, I believe you're right :-)
Sorry for the noise!