...run it from the directory that holds your projects. Note that, like the vanilla bundle install, this will fail whenever a new gem compiles native components and requires a missing...
...need to run bin/rake to use them. On older projects, you want to run "bundle exec rake" to avoid those ugly "already activated rake x.y.z" errors that hit you when...
...plain rake command which uses a binstubbed bin/rake if available and falls back to bundle exec rake if necessary. Try it To see if it works for you, run the...
...ran into trouble on a fairly fresh installed VM, running Ubuntu. I tried to bundle install and got this stacktrace: Fetching gem metadata from https://rubygems.org/.Unfortunately, a fatal error...
...has occurred. Please see the Bundler troubleshooting documentation at http://bit.ly/bundler-issues. Thanks! /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:36:in `gem_original_require': no such file to load -- net/https (LoadError) from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:36:in...
You can specify the version of bundler to execute a command (most often you need an older version of bundler, but don't want to uninstall newer ones):
Bundler version 1.0.10 An example is rails 3.2, which freezes bundler at version ~> 1.0: Bundler could not find compatible versions for gem "bundler": In Gemfile: rails (~> 3.2) was resolved...
...results in deploys not working when running with old deploy.rb files. So let's bundle it. Put capistrano into your Gemfile, like this: # Gemfile group :deploy do gem 'capistrano'
...capistrano_colors' end It's possible you need to do a bundle update net-ssh to get things running. Now double check that all your custom hooks are actually still...
Bundler 2 requires at least Ruby 2.3.0 and RubyGems 2.5.0. You might get the following error when you try to install bundler for Ruby < 2.3: ERROR: Error installing bundler:
...error upgrade your project's ruby version or install the last supported version of Bundler for Ruby < 2.3: gem install bundler -v '~>1' You will also see an error if...
Recent Bundler (1.16.1) started complaining about missing dependencies in the Gemfile. This is due to a stricter handling of specifications (see attached link). The error message looks like this:
...API or the lockfile (other-gem (< 3)). Either installing with `--full-index` or running `bundle update example-gem` should fix the problem. However, bundle install --full-index did not any...
As a user of Bundler you have spent significant time looking at this message: Fetching source index for http://rubygems.org/ To make Bundler skip this index update and only use...
...installed gems, you can use the --local option: bundle install --local Unfortunately this does not work with bundle update. It is said that Bundler 1.1 will use a feature of...
To install gems Bundler needs to be able to talk to https://api.rubygems.org. If you are behind a proxy you can use the https_proxy environment variable:
...myproxy:123 bundle install Note that if there is no https_proxy env variable, Bundler will also look for a http_proxy env variable. With Capistrano Ideally the server you...
If you just upgraded to Bundler 10.0.10 you might get the following error when bringing up Rails: /usr/lib/ruby/1.9.1/psych.rb:148:in `parse': couldn't parse YAML at line 17 column...
...by Rails localization files (en.yml, de.yml, etc.) using symbols for various translation strings, and Bundler 10.0.10 defaults to a new YAML engine which cannot handle symbols. You can switch back...
Even when you're using bundler, it might be significant in which order your gems are listed in your Gemfile. This can happen when gems are running around calling require...
...solutions as we become more experienced with using Bundler, and more command line tools become Bundler-aware. b will use bundle exec if there is a Gemfile in the working...
...directory, and run the call without Bundler otherwise. b spec spec This script is part of our geordi gem on github...
...followed by a backtrace, memory map and more. Fix The culprit seems to be Bundler 1.14 when used with Ruby 1.8.7. Downgrade to the maximum version that is compatible...
...comparators like >= or ~>. That way it is possible to fetch the latest version of Bundler 1 with this command: gem install bundler -v '~>1' How to install bundler for Ruby...
...is a common usecase where you might need Bundler...
Bundler 1.1 has been released. With this version you no longer need to wait for this: Fetching source index… The new Bundler is smarter and can fetch required metadata in...
You can install the new version by saying: sudo gem install bundler
If bundle install shows the following message for you ... Error Bundler::HTTPError during request to dependency API ... upgrade to Bundler ≥ 1.2.4: gem install bundler Apparently, it just hides the message...
Confusingly, RVM installs the bundler gem into the @global gemset, which is available to all gemsets and Rubies. You can get around this and install a particular bundler version like...
rvm @global do gem uninstall bundler rvm @global do gem install bundler -v...
Given you use Capistrano together with bundler to automatically install your gems when deploying. I recently had the problem that Capistrano stalled like this: [err :: host.name.tld] Username:
...tests/gherkin/runtime_logger Error creating formatter: ParallelTests::Gherkin::RuntimeLogger (LoadError) This will happen when you upgrade Bundler to version 1.13.x and appears to be "by design" since there is a Bundler...
...by setting that flag. You should commit the resulting config file into the repository! bundle config --local disable_exec_load true There is a GitHub issue that you can follow...
When you are calling Bundler from your shell scripts, you might find it useful that a failed bundle call returns a different error code depending on the type of problem...
When running an executable, ALWAYS use bundle exec. In some cases, running executables without bundle exec may work, if the executable happens to be installed in your system and does...
...not pull in any gems that conflict with your bundle. However, this is unreliable and is the source of considerable pain. Even if it looks like it works, it may...
Capistrano task for Bundler...
Bundler 2 introduced various incompatibilites und confusing behavior. To add to the confusion, Bundler's behavior changed after the release of their version 2. The linked article explains what happened...
If you cannot install the gem 'RedCloth' via bundle install you might want to try the following. Specifying extra build options for bundler which will only be applied when building...
bundle config build.RedCloth --with-cflags=-w