Glad that worked. I should make it clearer in the docs that "deploy.rb" is a railsism, and that all you really need is a Capfile. If you do have a deploy.rb, you need to make sure that you ALSO have a Capfile, and that the Capfile has a line like
load "path/to/deploy" Which loads your deploy.rb. Also, your deploy.rb must not reside in the same directory as the Capfile...which I suspect was the problem you were having. The "load 'deploy'" in the Capfile was loading your custom deploy.rb, instead of the built-in deploy recipes. - Jamis On 7/30/07, SanPy <[EMAIL PROTECTED]> wrote: > > Wow! That's it, it works, amazing! Thanks so much, I almost have been > eating my shoes over this. > > Regards, Sander. > > On 30 jul, 21:04, "Jamis Buck" <[EMAIL PROTECTED]> wrote: > > Alright, let's try this. Take the entire contents of your deploy.rb > > and paste it into the bottom of your Capfile. Then get rid of your > > deploy.rb. Then try: > > > > cap -T > > > > Does it include "cap deploy" in the output? If so, try > > > > cap deploy > > > > Does that then try to run the deploy? > > > > - Jamis > > > > On 7/30/07, SanPy <[EMAIL PROTECTED]> wrote: > > > > > > > > > My Capfile looks like this: > > > load 'deploy' if respond_to?(:namespace) # cap2 differentiator > > > > > That is the only line. > > > > > On 30 jul, 20:55, "Jamis Buck" <[EMAIL PROTECTED]> wrote: > > > > What does your Capfile look like? Does it have: > > > > > > load "deploy" > > > > > > near the top, before it loads your deploy.rb? > > > > > > - Jamis > > > > > > On 7/30/07, SanPy <[EMAIL PROTECTED]> wrote: > > > > > > > Hi, > > > > > > > I'm trying to use Capistrano for deployment of a django app. I have > > > > > generated a Capfile and deploy.rb with capify. After customizing the > > > > > deploy.rb with my settings, and testing it with my stop/start/restart > > > > > Apache tasks, I tried to call 'cap deploy', but I keep getting the > > > > > message: the task `deploy' does not exist . Whatever I do, with -f > > > > > deploy, -f Capfile, or both, or without, everytime I the message: the > > > > > task `deploy' does not exist . > > > > > > > My deploy.rb looks like this: > > > > > ----------- > > > > > set :application, "myproject" > > > > > set :repository, "http://svn. myproject.com/myproject/trunk/myproject" > > > > > > > set :apache_dir, "$HOME/webapps/django/apache2" > > > > > > > role :app, "xx.xx.xxx.xx" > > > > > role :web, "xx.xx.xxx.xx" > > > > > role :db, "xx.xx.xxx.xx" > > > > > > > #set :use_sudo, false > > > > > > > set :deploy_to, "$HOME/deployments/#{application}" > > > > > > > namespace :apache do > > > > > desc "A task that can be used to stop Apache." > > > > > task :stop do > > > > > run "#{apache_dir}/bin/stop" > > > > > end > > > > > > > desc "A task that can be used to start Apache." > > > > > task :start do > > > > > run "#{apache_dir}/bin/start" > > > > > end > > > > > > > desc "A task that can be used to restart Apache." > > > > > task :restart do > > > > > run "#{apache_dir}/bin/restart" > > > > > end > > > > > end > > > > > ----------- > > > > > > > Since I don't know anything about ruby or capistrano (just found it > > > > > today and thought it might simplify my deployments), it could be that > > > > > I'm missing something very obvious, but I can't find it. > > > > > In summary, what do I need to do to access the 'built-in' deploy task? > > > > > > > Regards, Sander. > > > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
