I found BUNDLE_DISABLE_SHARED_GEMS: '1'
, in .bundle/config
. What does it mean?
相关问题
- Question marks after images and js/css files in ra
- Using :remote => true with hover event
- Eager-loading association count with Arel (Rails 3
- How to specify memcache server to Rack::Session::M
- Why am I getting a “C compiler cannot create execu
相关文章
- Ruby using wrong version of openssl
- Right way to deploy Rails + Puma + Postgres app to
- AWS S3 in rails - how to set the s3_signature_vers
- Difference between Thread#run and Thread#wakeup?
- how to call a active record named scope with a str
- How to add a JSON column in MySQL with Rails 5 Mig
- “No explicit conversion of Symbol into String” for
- form_for wrong number of arguments in rails 4
Bundler takes some settings from the
~/.bundle/config
file -- not from the shell env.When set to true (default), the install of all gems will be to
BUNDLE_PATH
, regardless of whether those gems are installed in your system.Bundler will not install gems already in system gems by default, so this is especially useful if you're trying to package up an application with all dependencies unpacked.
Check also:
http://www.atentia.net/2013/08/fun-with-bundle/
I will say this much, I commented out BUNDLE_DISABLE_SHARED_GEMS: '1' on my system, and this prevented passenger standalone from serving a page, yielding an error starting with: "It looks like Bundler could not find a gem."
I am running all my gems except passenger in a locally bundled gemset.
That means that a "bundle install" will always install the gems into a local directory (defaults to
.bundle
), and use those, instead of system-wide installed gems.