Do an 'ls -lah' inside the release directory and post the results; a mismatch in owner should be clearly apparent.
Make sure you execute the bundle install as the same user as your application runner; else chown the release directory and bundle path to your application runner after the bundle. Why are you using svn for a github repo? Have you tried setting the :scm to :git, and use remote_cache strategy? It should be much faster. > On Nov 4, 2013, at 4:26 PM, Gallagher Polyn <gallagher.po...@gmail.com> wrote: > > Firstly, thanks for your reply. > >> Make sure you didn't .gitignore Gemfile.lock > > No, I checked, and it is not included there. > >> 'bundle install' locally and commit the result. > > I performed this action, and with a clean working directory the result was > the same, unfortunately. > > After further investigation into this and reading this little post, is my > issue possibly related to ownership of the lock file on the server? Is is > possible that the permission structures are mismatched? > >>> On Nov 1, 2013, at 6:09 PM, Gallagher Polyn <gallagh...@gmail.com> wrote: >>> >>> Hi, >>> >>> Using Capistrano v2.11.2 and Ruby 2.0.0p247 and attempting cap deploy:cold, >>> it seems I encounter a hiccup related to some improper digestion of >>> Gemfile.lock. >>> >>> Here is a gist with my Capfile, deploy.rb and the readout resulting from >>> the command: https://gist.github.com/gpolyn/0c7d35e52c81b8b53032 >>> >>> …it seems to me that the problem is encountered here... >>> >>> [localhost] sh -c 'cd /var/massiveapp/releases/20131102003502 && bundle >>> install --gemfile /var/massiveapp/releases/20131102003502/Gemfile --path >>> /var/massiveapp/shared/bundle --deployment --quiet --without development >>> test' >>> ** [out :: localhost] The --deployment flag requires a Gemfile.lock. >>> Please make sure you have checked >>> ** [out :: localhost] your Gemfile.lock into version control before >>> deploying. >>> command finished in 112ms >>> *** [deploy:update_code] rolling back >>> >>> …though a (possibly unrelated) failure follows later... >>> >>> failed: "sh -c 'cd /var/massiveapp/releases/20131102003502 && bundle >>> install --gemfile /var/massiveapp/releases/20131102003502/Gemfile --path >>> /var/massiveapp/shared/bundle --deployment --quiet --without development >>> test'" on localhost > > > -- > -- > * You received this message because you are subscribed to the Google Groups > "Capistrano" group. > * To post to this group, send email to capistrano@googlegroups.com > * To unsubscribe from this group, send email to > capistrano+unsubscr...@googlegroups.com For more options, visit this group at > http://groups.google.com/group/capistrano?hl=en > --- > 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. > For more options, visit https://groups.google.com/groups/opt_out. -- -- * You received this message because you are subscribed to the Google Groups "Capistrano" group. * To post to this group, send email to capistrano@googlegroups.com * To unsubscribe from this group, send email to capistrano+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/capistrano?hl=en --- 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. For more options, visit https://groups.google.com/groups/opt_out.
