>
> I have a Rails 4 app setup to deploy using Capistrano. It all works good
> except having Cap bundle install any gems. For some reason the new version
> of Capistrano is cloning the repo from CloudForge into /apps/
> app.com/current/app.com(or whatever repo is called on CloudForge) instead
> of how it used to work. It would clone into /apps/app.com/current. Now
> when Cap tries to bundle it can't find the Gemfile because its not looking
> one directory deeper into the current symlink.
>

​I believe this was a problem with Capistrano 3.2, please try 3.2.1

- Lee​

-- 
You received this message because you are subscribed to the Google Groups 
"Capistrano" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to capistrano+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/capistrano/CAN_%2BVLWWiAsPDo_QvYCmqXB1Q0kt%2BKa8trmtkmuZk1qTR0W0bw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to