Release 0.5.1
Correction: Don't allow for caps 'EXPORT' command

There's no such thing!
Merge pull request #24 from jcamenisch/export-keyword

Correction: Don't allow for caps 'EXPORT' command
Move version into lib
Add dotenv-rails gemspec
Show warning if loaded outside of dotenv-rails
Explicitly require dotenv in railtie
Update README and Changelog
Specify gemspec name in Gemfile
Seems to read better when being explicit.

A few times through I actually got confused when trying to
figure out if the S3_BUCKET should actually have been set to
`dotev` instead of whatever bucket you're actually using.

I realize this is sort of a no-brainer, but it'd seem like
lowering the bar to almost the floow is the best case for adoption.
more explicitness of where the file is
Merge pull request #26 from brntbeer/readme-rewording

Readme rewording
add guard
Clean up specs
Expand \n in quoted strings

Closes #21
Merge branch 'master' into dotenv-rails

* master:
  Clean up specs
  add guard
  more explicitness of where the file is
  Seems to read better when being explicit.
  Correction: Don't allow for caps 'EXPORT' command
  Allow for env variables set with 'export' keyword
  Test env file with 'export ' before variables
  Allow double quotes in .env variable assignment

Conflicts:
	Gemfile
Merge branch 'master' into dotenv-rails

* master:
  Expand \n in quoted strings
Merge pull request #25 from bkeepers/dotenv-rails

Move autoloading to dotenv-rails gem
Release 0.6.0
Fix indentation in changelog