Comments on: rails 3, bundler, capistrano

By: matt

matt — Wed, 01 Sep 2010 18:25:23 +0000

Cool, thanks! I knew it would just be a matter of time…

By: Evan

Evan — Wed, 01 Sep 2010 00:48:52 +0000

Looks like this is easier to deal with these days, add the following to your deploy.rb:

require ‘bundler/capistrano’

…and you’re done!

By: links for 2010-08-17 « Caiwangqin’s delicious bog

links for 2010-08-17 « Caiwangqin’s delicious bog — Tue, 17 Aug 2010 23:04:51 +0000

[...] rails 3, bundler, capistrano — matt vs world (tags: bundler capistrano rails3) [...]

By: kazjote

kazjote — Wed, 04 Aug 2010 13:12:23 +0000

Thanks for great recipe

I use it already for some time and found an issue with failing deployments.

In simple words, if anything goes wrong during the deployment after bundler install task you will end up with unbootable application state.

The solution is to provide on_rollback tasks which I covered on my blog: http://kazjote.eu/2010/08/04/bundler-and-capistrano-the-right-way

By: matt

matt — Thu, 29 Jul 2010 18:38:12 +0000

You’re right, but what I wanted to accomplish was not having the bundle re-generated during each deployment. If the bundle configuration remains the same, it doesn’t have to “re-install” anything if you use the symlink approach. If you don’t mind the extra deployment time (and space taken up by multiple copies of bundles), then it’s not necessary to symlink.

I generally run rails applications as a custom user, and deploy “as” another one. That’s entirely up to you and your particular deployment scenario — i.e., what kind of access you have, how your web server is configured, etc, etc. Of course, you can always run and deploy as root if you feel like living on the edge…

By: J. Pablo Fernández

J. Pablo Fernández — Thu, 29 Jul 2010 12:30:24 +0000

You could cd to #{current_path} and avoid creating the symlink at all. By the way, under which user are you deploying and which user are you running the app as?

By: Michael Pearson

Michael Pearson — Tue, 20 Jul 2010 03:35:16 +0000

Thanks, you just saved me my afternoon. (see: https://gist.github.com/f25b7b8b4a63b398a400)

By: matt

matt — Tue, 13 Apr 2010 11:51:56 +0000

I think it came through correctly here… thanks for the tip, I think I’m gonna try it myself!

By: neal clark

neal clark — Tue, 13 Apr 2010 08:02:22 +0000

hey matt, great post! i integrated part of it into my first production bundler deploy. cheers!

the biggest change i made was not to call ‘bundle install’ if ‘bundle check’ tells me there’s nothing to install. here’s what i have for the ‘bundle install’ step on my app (i have no idea how this will look when pasted into your blog):

task :bundle, :role => [:app, :web] do
deploy.create_bundler_symlink
run “cd #{release_path} ; bundle check 2>&1 > /dev/null ; if [ $? -ne 0 ] ; then sh -c ‘bundle install –disable-shared-gems –without test’ ; fi”
end

thanks for the help!