rake gems:install fails because database.yml is not created yet

[Henning Kiel]

When setting up a staging instance, during the first deploy rubber
tries to run "rake gems:install" before a rubber:config has
transformed and placed all templates, including the database.yml. This
makes gems:install fail.

Does this happen to anyone else? Or is it maybe a problem with our
environment configuration inside the Rails app?

[Matthew Conway]

Looks like a bug, filed at:
http://github.com/wr0ngway/rubber/issues#issue/4

If you need a workaround till the next gem release, add your needed
gems to rubber.yml, and stub out the rubber task by adding the
following to the bottom of deploy.rb:

rubber.task :install_rails_gems do
end

Matt

[Henning Kiel]

Yeah, I stubbed out the task, but in the mean time we have switched
over to install gems using the new gem bundler, and no longer use any
gem declarations in environment.rb. As the bundler does not depend on
any application code, this proved to be much more reliable.

[matt (wr0ngway)]

Is this the gem bundler that you were referring to? Still happy with
it?
http://github.com/wycats/bundler

Thanks,

Matt