Skip to content

Commit dcfac43

Browse files
pbolingnickcharlton
authored andcommitted
Remove suggestion of RubyGems in Rakefiles. (thoughtbot#128)
* It implies you're always running commands through Rake, which isn't necessarily true. * Adds `bundle exec` as a prefix to other commands.
1 parent c3e369b commit dcfac43

1 file changed

Lines changed: 3 additions & 9 deletions

File tree

README.md

Lines changed: 3 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -52,30 +52,24 @@ your `Gemfile`, so you don't need to repeat anything that's the same for each
5252
appraisal. If something is specified in both the Gemfile and an appraisal, the
5353
version from the appraisal takes precedence.
5454

55-
It's also recommended that you setup bundler at the very top of your Rakefile,
56-
so that you don't need to constantly run bundle exec:
57-
58-
require "rubygems"
59-
require "bundler/setup"
60-
6155
Usage
6256
-----
6357

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

67-
$ appraisal install
61+
$ bundle exec appraisal install
6862

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

73-
$ appraisal rails-3 rake test
67+
$ bundle exec appraisal rails-3 rake test
7468

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

78-
$ appraisal rake test
72+
$ bundle exec appraisal rake test
7973

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

0 commit comments

Comments
 (0)