Gemfile in deployment environments

[seankibler]

The Gemfile has a lot of conditions in it that cause serious problems in environments where the deployment environment uses a different database back end than the local development environment.

What happens is even though the Gemfile.lock is checked in and up-to-date when Gemfile is evaluated it comes up with new dependencies because of the conditions contained within checking for the database adapter and ruby version. As a result Rails is unable to load because Bundler flips its lid seeing the discrepancy between the checked in Gemfile.lock and the Gemfile.lock from evaluating Gemfile.

[mvz]

The logic in the Gemfile is needed to facilitate the kind of distributed developement used for typo. For the same reason, we don't check in Gemfile.lock.

For your situation, If you've already got your own branch with Gemfile.lock checked in, I recommend tailoring the Gemfile as well. This will of course mean that it installs gems for the production database back end on your development machines.