I'm having this same problem. Why is this happening? I was never
having this problem before. Was something changed in the source?

On Aug 20, 3:43 am, Lee Hambley <[email protected]> wrote:
> Matte,
> I believe we've had a patch for just this problem from someone who forked
> the capistrano-ext gem, can you file it 
> onhttp://capistrano.lighthouseapp.com/- you have found a bug - would be great
> to get the patch formalised then everyone can see the bug life-cycle!
>
> -- Lee Hambley
>
> Twitter: @leehambley
> Blog:http://lee.hambley.name/
> Working with Rails:http://is.gd/1s5W1
>
> 2009/8/19 silent (e) <[email protected]>
>
>
>
> > I've just installed the multistage extension on my Windows XP
> > development machine with the intent to deploy to my staging location
> > on a FreeBSD box.  I've removed my previous reference to
> > the :deploy_to setting in deploy.rb.
>
> > My config/deploy/staging.rb file says...
>
> > set :deploy_to, "/foo/bar/etc"
> > set :rails_env, :staging
>
> > however when I run my "cap staging deploy" the svn update line calls
> > to the shared_path value that's still using the default deploy_to
> > location, like "/u/apps/:application/shared" and not "/foo/bar/etc/
> > shared".
>
> > This looks to me like shared_path isn't being rebuilt in multistage.
> > line 49 of the cap gem recipes/deploy.rb file defines :shared_path but
> > it's never rebuilt.
>
> > I'm running cap 2.5.8 and cap/ext/multi-stage 1.2.1 on my WinXP
> > development box.
>
> > Am I missing something?  Adding "set :shared_path, File.join
> > (deploy_to, shared_path)" in my staging.rb file fixes the problem, but
> > I'd have thought it would "just work".  :)
>
> > matte

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to