Lee, Thanks for your help, turns out that for legacy reasons the code uses capistrano v 1.4.2, where this kind of syntax is perfectly viable. All I had to do what type:
cap _1.4.2_ my_task And the cap task auto senses that I want this task to run with capistrano 1.4.2 Well I've learnt something new. Tom On Jun 8, 1:34 pm, Lee Hambley <[email protected]> wrote: > Tom, > You have been mislead, I can't see that ever having worked, this should > though. change > > set :mongrel_config, "#{current_path}/config/staging_mongrel_cluster.yml" > > for > > set :mongrel_config, { "#{current_path}/config/staging_mongrel_cluster.yml" > > } > > The problem is that when defining the config you don't have access to the > current_path variable, enclosing it in curly braces replicates the Ruby > lambda syntax and evaluates the variable's value when it is used later in > the recipe. > > - Lee > > 2009/6/8 Tom Williams <[email protected]> > > > > > > > Hi, > > I am attempting to use capistrano to deploy a rails site set up using > > mongrels. I'm doing some maintenance on an existing site, so I'm > > assured that this rake file works, but it doesn't appear to be working > > on my computer. > > > Specifically it spits out the following error: > > > /Users/ceilingfish/.gem/ruby/1.8/gems/capistrano-2.5.5/lib/capistrano/ > > configuration/variables.rb:122:in `method_missing': undefined local > > variable or method `current_path' for #<Capistrano::Configuration: > > 0x1adff74> (NameError) > > from config/staging_deploy.rb:47:in `load' > > from /Users/ceilingfish/.gem/ruby/1.8/gems/capistrano-2.5.5/lib/ > > capistrano/configuration/loading.rb:172:in `load_from_file' > > from /Users/ceilingfish/.gem/ruby/1.8/gems/capistrano-2.5.5/lib/ > > capistrano/configuration/loading.rb:89:in `load' > > from /Users/ceilingfish/.gem/ruby/1.8/gems/capistrano-2.5.5/lib/ > > capistrano/configuration/loading.rb:86:in `load' > > from /Users/ceilingfish/.gem/ruby/1.8/gems/capistrano-2.5.5/lib/ > > capistrano/configuration/loading.rb:86:in `each' > > from /Users/ceilingfish/.gem/ruby/1.8/gems/capistrano-2.5.5/lib/ > > capistrano/configuration/loading.rb:86:in `load' > > from /Users/ceilingfish/.gem/ruby/1.8/gems/capistrano-2.5.5/lib/ > > capistrano/cli/execute.rb:64:in `load_recipes' > > from /Users/ceilingfish/.gem/ruby/1.8/gems/capistrano-2.5.5/lib/ > > capistrano/cli/execute.rb:64:in `each' > > from /Users/ceilingfish/.gem/ruby/1.8/gems/capistrano-2.5.5/lib/ > > capistrano/cli/execute.rb:64:in `load_recipes' > > from /Users/ceilingfish/.gem/ruby/1.8/gems/capistrano-2.5.5/lib/ > > capistrano/cli/execute.rb:30:in `execute!' > > from /Users/ceilingfish/.gem/ruby/1.8/gems/capistrano-2.5.5/lib/ > > capistrano/cli/execute.rb:14:in `execute' > > from > > /Users/ceilingfish/.gem/ruby/1.8/gems/capistrano-2.5.5/bin/cap:4 > > from /usr/bin/cap:19:in `load' > > from /usr/bin/cap:19 > > > Where line 47 in config/staging_deploy.rb is: > > > set :mongrel_config, "#{current_path}/config/ > > staging_mongrel_cluster.yml" > > > I can't seem to find anything on google to indicate that referencing > > current_path here would be a problem, does anyone know different? > > > Thanks for any help, > > Tom --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Capistrano" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.co.uk/group/capistrano?hl=en -~----------~----~----~----~------~----~------~--~---
