use dotenv 0.11.x

[seamusabshere]

this is a less loose version of #436

0.11.x allows the use of dotenv-deployment which is a significant improvement over 0.7.x

[seamusabshere]

(it truncated my comment)

0.11.x allows the use of dotenv-deployment, which factors the very useful .env.{test,development,production} pattern out of the (now deprecated, I believe) dotenv-rails

[ddollar]

Breaking out internal functionality into a separate gem seems like a dotenv implementation detail that doesn't actually affect foreman. Could you please elaborate on why the bump is needed?

[seamusabshere]

I want to make sure we're using the latest foreman because it has lots of great fixes, but I also want to use dotenv-deployment for non-rails apps:

Bundler could not find compatible versions for gem "dotenv":
  In Gemfile:
    foreman (>= 0.64.0) ruby depends on
      dotenv (~> 0.7.0) ruby

    dotenv (0.11.1)

[ddollar]

You should not put foreman into your Gemfile as the dependencies of a developer utility should not be able to interfere with the dependencies of your app.

[seamusabshere]

ok, that's fair, I was following thoughbot convention:

https://github.com/thoughtbot/suspenders/blob/master/templates/Gemfile.erb

thanks @ddollar !

[ddollar]

Interesting I have always wondered where that trend got started. Having foreman be run inside the app using whatever random version of Ruby the user has installed is quite a pain point.

If you'd like to see something smaller with even less dependencies check out https://github.com/ddollar/forego

[seamusabshere]

brilliant