Skip to content

Commit

Permalink
Remove suggestion of RubyGems in Rakefiles. (#128)
Browse files Browse the repository at this point in the history
* It implies you're always running commands through Rake, which isn't
  necessarily true.
* Adds `bundle exec` as a prefix to other commands.
  • Loading branch information
pboling authored and nickcharlton committed Nov 20, 2017
1 parent c3e369b commit dcfac43
Showing 1 changed file with 3 additions and 9 deletions.
12 changes: 3 additions & 9 deletions README.md
Expand Up @@ -52,30 +52,24 @@ your `Gemfile`, so you don't need to repeat anything that's the same for each
appraisal. If something is specified in both the Gemfile and an appraisal, the
version from the appraisal takes precedence.

It's also recommended that you setup bundler at the very top of your Rakefile,
so that you don't need to constantly run bundle exec:

require "rubygems"
require "bundler/setup"

Usage
-----

Once you've configured the appraisals you want to use, you need to install the
dependencies for each appraisal:

$ appraisal install
$ bundle exec appraisal install

This will resolve, install, and lock the dependencies for that appraisal using
bundler. Once you have your dependencies set up, you can run any command in a
single appraisal:

$ appraisal rails-3 rake test
$ bundle exec appraisal rails-3 rake test

This will run `rake test` using the dependencies configured for Rails 3. You can
also run each appraisal in turn:

$ appraisal rake test
$ bundle exec appraisal rake test

If you want to use only the dependencies from your Gemfile, just run `rake
test` as normal. This allows you to keep running with the latest versions of
Expand Down

0 comments on commit dcfac43

Please sign in to comment.