Add Gemfile dependencies

[AndyDangerous]

Closes #2

I just added '~>' whatever my current version was. Is this what we want?

[JoshCheek]

• [x] Lets go with most recent versions of the gems, so we're as up to date as possible. You can find that at https://rubygems.org/gems/:gemname
• [x] The ~> operator means that the last number can increase, but the others can't. But if our gems are following semantic versioning, we don't need to be that strict, we should be able to let the middle number increase, as well, so remove the last digit from the spec. (Cara made a good post about this, search for "Twiddle-Wakka" here
• [x] Can you line them up so its easier to read? example

---

I made these into check boxes instead of bullet points, b/c I have a hypothesis that this makes it easier to go implement (I think this would be true for me, anyway), since it's easier to map the statement to a thing to do. If that doesn't work, let me know and I'll not keep doing that.

[AndyDangerous]

I'm into the checkboxes. It does seem easier for me to work through them that way.

I hope this looks good.

Regarding versioning: If I just run bundle (without explicitly defining versions) won't it just pull down the most recent versions?

[JoshCheek]

Looks good, merge it!

Regarding versioning: If I just run bundle (without explicitly defining versions) won't it just pull down the most recent versions?

No, the Gemfile specifies what we will allow. Bundler will then "resolve" those (find the versions that fit all the requirements), and stick them in the Gemfile.lock. After that, it always goes with whatever the Gemfile.lock says, so it always uses the same version every time for everyone.