You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 14, 2021. It is now read-only.
Yep. That's a documented limitation of Bundler. The .bundle/config file is actually found relative to the Gemfile, which means that the Gemfile location can't be changed in config.
The following is a list of all configuration keys and their purpose.
[...]
gemfile (BUNDLE_GEMFILE): The name of the file that bundler should use as the Gemfile. This
location of this file also sets the root of the project, which is used to resolve relative paths in the
Gemfile, among other things. By default, bundler will search up from the current working directory until
it finds a Gemfile.
[...]
You can set them globally either via environment variables or bundle config, whichever is preferable
for your setup. If you use both, environment variables will take preference over global settings.
I'd just suggest denoting the exception for gemfile in that last paragraph there.
In .bundle/config, I tried to add
BUNDLE_GEMFILE=Gemfile.local
But the config is ignored when running
$ bundle exec bundle
However this works:
$ BUNDLE_GEMFILE=Gemfile.local bundle exec bundle
The text was updated successfully, but these errors were encountered: