Default bin scripts from bundle gem command: bin/console and bin/setup

[pboling]

• bin/console
• bin/setup

A comparison between the current irb use case, and the new bin/console use case:
Old and janky:

∴ irb
>> require "bundler/setup"
=> true
>> require "hashie"
=> true
>> Hashie::Mash.new(hi: "@dblock")
=> #<Hashie::Mash hi="@dblock">

New hotness:

∴ bin/console
>> Hashie::Mash.new(hi: "@dblock")
=> #<Hashie::Mash hi="@dblock">

[dblock]

I am sure I am missing something ... why do we need this?

[pboling]

@dblock It is a new "gem" standard. Modern Gems built with the bundle gem template (most gems) come with a bin/ directory that has two scripts. console is an enhanced irb that preloads the gem, so you can get straight to hacking:

∴ bin/console
>> Hashie::Mash.new(hi: "@dblock")
=> #<Hashie::Mash hi="@dblock">

setup by default just bundle installs. On my gems I enhance the setup script to:

• create artifacts needed for testing (rails apps, databases, install all the various supported ruby versions, etc)
  The one here is still vanilla, but the point is that it could be useful. You do support a lot of rubies. You could have the setup script iterate over them and install them.

They are intended for developers that will be hacking on your project. You can use them to reduce the number of things people have to do when contributing. For example, you could add a bin/preflight.

[pboling]

@dblock this is ready (if you think it is worthwhile)

[dblock]

Ok I'll take these. Make sure they (are) run through RuboCop and squash the commits. Thx.

[pboling]

@dblock Rebased on intridea/master, Squashed to 1 commit and Rubocop'd. This is ready.

[dblock]

Merged, thanks.