Bundler 1.4.0 (still beta) can install gems in parallel, making a run of bundle install much faster...
...like /usr/lib/ruby/gems/1.8/gems/your-broken-gem and /usr/lib/ruby/gems/1.8/specifications/your-broken-gem Update Rubygems or Slimgems by running gem update --system Run bundler on your project to reinstall the offending gem. If this happens to your during deployment...
After the update, log onto the server and remove the broken Bundler cache directories like (e. g. shared/bundle)
/home/.../ruby/gems/2.1.0/gems/bundler-1.14.3/lib/bundler/rubygems_ext.rb:45:in `full_gem_path': uninitialized constant Bundler::Plugin::API::Source (NameError) Solution: Upgrade Rubygems beyond...
bundle open BUNDLED_GEM will open the BUNDLED_GEM's source code in your default editor...
...Option 1: Run without headless You can call your tests with NO_HEADLESS=1 bundle exec cucumber to see the Chrome window for this test run. (This will not work...
...a bash alias alias nh='NO_HEADLESS=1' to shorten this command to nh bundle exec cucumber. Option 2: Remote debugging With remote debugging, you can access a Docker Chrome...
You need to install the official plugin, it is not bundled with RubyMine by default. Example: Setup a watcher to verify rubocop integrity First, open Settings -> Tools -> File Watchers...
...your $PATH. I worked around this constraint by using b as a shim for bundle exec. Resources File watchers documentation Settings documentation
It is possible to access Rails config (for example secrets) from within your webpack bundles, thanks to rails-erb-loader. When using webpacker, the setup is like this:
...If you do this, your gemspec will not validate and modern versions of Bundler will silently ignore it. This leads to errors like: Could not find your-gem-0.1.2 in...
...a debugger gem but still have it in development, add this line to .travis.yml: bundler_args: --without development Then move any debugger gem (debugger, ruby-debug) into the :development group...
After running bundler / gem install I could not load nokogiri lately. It died with cannot load such file -- nokogiri/nokogiri. This is not a problem of the gem but is due...
... If upgrading is not an option, configure build options for gherkin: bundle config --local build.gherkin --with-cflags=-w Your .bundle/config file should now look like this: ---
...GHERKIN: "--with-cflags=-w" You should now be able to install the gem with bundle install. Make sure to commit and push .bundle/config so your fellow developers (and all the...
steps: - uses: actions/checkout@v4 - uses: ./.github/actions/setup-node - uses: ./.github/actions/setup-ruby - name: Setup database schema run: bundle exec rails db:create db:schema:load - name: Precompile assets run: bundle exec rails assets...
...rf /var/lib/apt/lists/* shell: bash - name: Setup Ruby uses: ruby/setup-ruby@v1 with: ruby-version: ".ruby-version" bundler-cache: true cache-version: 1 - name: Verify Ruby and Bundler versions run: | ruby -v...
If you make a gem with Bundler, you will get a rake release task that will instantly publish your gem to rubygems.org for all the world to admire. For private...
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
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...
After installing Bundler 1.1 you will get the following warning when running tests: WARNING: Cucumber-rails required outside of env.rb. The rest of loading is being defered until env.rb is...
...gems in the Gemfile. Since all versions are saved in the Gemfile.lock, everyone running bundle install will get exactly the same versions. There are some exceptions, where you can consider...
...reason is highly recommended) You want to ensure no one upgrades a library with bundle update An drawback of this approach is, that adding new gems might also upgrade existing...
Install this gem and stop using bundle exec or even Geordi's handy b. Yay...
...Run the test to ensure it works within your app. The test should fail: bundle exec rspec spec/requests/default_etag_spec.rb Fixing random CSP nonces Open config/initializers/content_security_policy.rb and change the content_security_policy...
...game over anyway. Checking successful integration The test we added earlier should now pass: bundle exec rspec spec/requests/default_etag_spec.rb To manually test ETags, open the Network tab of your DevTools. Then...
...you get an error like this: An error occurred while installing pg (0.17.1), and Bundler cannot continue. Make sure that gem install pg -v '0.17.1' succeeds before bundling.
sudo apt-get install libpq-dev ... and run Bundler again...
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...
...about that but in some cases it can't. To resolve this issue, run: bundle install If this does not do the trick for you, take a look at the...
...r --clear-sources -s 'https://user:password@gemserver.tld/' This is useful to debug cases where Bundler complains of a gem existing in more than one gem source...
...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...