ENV Variables Not Available When Deploying about dotenv

[bkeepers]

I haven't used capistrano for a while, but I'm guessing there is some kind of hook that it could use. Otherwise, you could just do it manually:

require 'dotenv'
Dotenv.load

[nnc]

I had the same problem with Capistrano 2 as @jherdman described, but it turns out the only problem was I blindly followed instructions in the README to add

gem 'dotenv-rails', :groups => [:development, :test]

to Gemfile. Once I removed the groups part, everything is working as advertised.

[bkeepers]

@nnc thanks for the report! Can you try upgrading to the latest, which pulls capistrano support into https://github.com/bkeepers/dotenv-deployment.

[nnc]

@bkeepers I think I already have the latest dotenv and dotenv-deployment, as I installed it all yesterday.

[nnc]

@bkeepers I just checked to make sure I have the latest of all 3 gems:

$ bundle list|grep dotenv
  * dotenv (0.11.1)
  * dotenv-deployment (0.0.2)
  * dotenv-rails (0.11.1)

However, I now see I completely missed the part about adding 'dotenv-deployment' to Gemfile, in the dotenv-deployment README. I saw dotenv-deployment was installed as a dependency of dotenv, so I thought I'm all set there.

Are there any downsides to having just

gem 'dotenv-rails'

in the Gemfile, as opposed to

gem 'dotenv-rails', :groups => [:development, :test]
gem 'dotenv-deployment'

as instructed by READMEs?

[bkeepers]

dotenv-deployment will be removed as a dependency of dotenv in the next release (1.0).

I will update the docs for dotenv-deployment for 1.0 to just have:

gem 'dotenv-deployment'

[nnc]

@bkeepers docs for dotenv-deployment already say that, but docs for dotenv-rails say you should put it only in development and test groups.

So docs are actually already correct, one just needs to follow both of them precisely. The problem I had was simply because I didn't do that.

Thanks for dotenv btw!

[jherdman]

Oh boy. I didn't realize there was a dotenv-deployment. That definitely explains my issue! I looked into it this morning, but I don't think it's flexible enough to meet my needs (it looks for .env.* in the wrong place for my application).

I'm happy with closing this issue unless there's an action item that be generated from this still.