Skip to content
This repository has been archived by the owner on Jun 5, 2019. It is now read-only.

Remember alternative Gemfile #86

Closed
ineiti opened this issue May 14, 2015 · 5 comments
Closed

Remember alternative Gemfile #86

ineiti opened this issue May 14, 2015 · 5 comments

Comments

@ineiti
Copy link

ineiti commented May 14, 2015

When I use an alternative Gemfile like

bundle install --gemfile Gemfile.dev

I'd like the Gemfile.dev.lock be used in any require 'bundler/setup'

Usecase:

for my development, I like having path: in the Gemfile, but not for deployment. So I made a second Gemfile and I am trying to use that one, but it always takes the gems from Gemfile.lock

@segiddins
Copy link
Member

You can use the BUNDLER_GEMFILE environment variable to this effect

@ineiti
Copy link
Author

ineiti commented May 14, 2015

OK - that might work. But I still it would be more logical to continue the way of rubygems/bundler#3320 and also use the config:gemfile for bundler/setup.

@ineiti
Copy link
Author

ineiti commented May 14, 2015

Now a step further. If I do first

bundle config --local gemfile Gemfile.dev

everything works as expected. But one might wonder whether the --gemfile option in bundle install shouldn't set that configuration by itself.

@asymmetric
Copy link

@ineiti, according to this issue:

In Bundler 2.0, flags passed to commands will no longer be remembered, and instead should be set using bundle config if they should apply to every run

@coilysiren
Copy link
Contributor

This issue was moved to rubygems/bundler#4541

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants