`BUNDLE_GEMFILE` can't be configured

[gerrywastaken]

`BUNDLE_GEMFILE` can't be configured

[dadooda]

Hey @tiagoamaro,

$ BUNDLE_GEMFILE=Gemfile.local bundle install

It's b install if you use bundler-gemlocal. Times shorter and foolproof.

$ BUNDLE_GEMFILE=Gemfile.local bundle exec rake -T

It's bx rake -T if you use bundler-gemlocal.

Also, keep in mind that your command will only work if the command is typed while standing next to Gemfile.local. If, for instance, you cd to app/models of your project, you'll have to uglify your command like this: $ BUNDLE_GEMFILE=../../Gemfile.local bundle ....

It's sad Bundler doesn't support local Gemfile out of the box. Most teams need it even if they don't realize it yet. Let's hope for the best. Until then, may the Hack be with us. :)

Cheers!

[dadooda]

Hey Gerry,

Check out a working solution for a local Gemfile, in case you're interested: https://github.com/dadooda/bundler-gemlocal.

Cheers!

Alex

[tiagoamaro]

@dadooda, thanks for your solution. Based on yours and @gerrywastaken's, I was able to create a Gemfile.local only using bundler and its embedded features, using environment variables to configure a different Gemfile [1]. Here's the solution:

# Gemfile.local

eval_gemfile File.expand_path('./Gemfile') # [2]

# Add any gems and groups that you don't want to keep local
group :development do
  gem 'pry'
end

# Using BUNDLE_GEMFILE
$ BUNDLE_GEMFILE=Gemfile.local bundle install
$ BUNDLE_GEMFILE=Gemfile.local bundle exec rake -T

[1] http://www.schneems.com/post/59689229829/specify-different-gemfile-while-using-bundler/
[2] only using eval as @gerrywastaken introduced on this repository raised exceptions. This was solved by @dadooda's usage of Bundler's eval_gemfile method.