Did you run 'capify' on your project directory? capify .
(note the '.', which means 'current directory'). - Jamis On 3/11/09 5:40 PM, Josh Rachner wrote: > I actually meant to put cap deploy:update, sorry about that. I got it to > the point now where it says "the task 'deploy:update' does not exist." I > have the deploy.rb in my config dir. That is the correct place for it > right? > > If all my gems are in /usr/lib/ruby/gems/1.8/gems, then I just include > that in my path right? > > On Wed, Mar 11, 2009 at 6:36 PM, Sarah Mei <[email protected] > <mailto:[email protected]>> wrote: > > > Could it be as easy as moving the semicolon? > > cap deploy:update > > On Wed, Mar 11, 2009 at 4:13 PM, [email protected] > <mailto:[email protected]> > <[email protected] <mailto:[email protected]>> wrote: > > > > I get this eror when I run the cmd cap:deploy update > > > > bash: cap:deploy: command not found > > > > The gem is installed, the path is in my .bashrc file, and I even > > copied and pasted the gem into my vendor/plugins folder (not sure if > > that matters). I have had a lot of problems with installing gems in > > the past 8 months and so I was wondering if maybe I need a require > > 'ruby_gems' somewhere. I usually have to result in copying the gem > > into my project. If someone has any ideas that would be great. I can > > do a cap -h, so it is installed on my system. I am on Ubuntu 8.04 > > Hardy > > > > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
