DotEnv + Unicorn zero downtime = fail about dotenv HOT 4 CLOSED

Apparently this feature was up voted when implemented... I don't really understand why since dotenv solves the, i.m.o, mess of having env vars from all kinds of places you don't even know of sometimes. Why not have it all in the same place?

Anyway I forked the repo and made the change (which is obviously extremely simple). Here it is:
johnae@0556d5e

from dotenv.

See #38. I'm not against changing how this is implemented, it just needs to be done properly.

and honestly, i.m.o, I don't think NOT overwriting keys in production is a bad default.

I disagree. The deployment environment should ALWAYS have the final say. dotenv is primary aimed at solving the problem in development. In production, it's really easy to just set your config options in the environment.

from dotenv.

Well I guess we disagree, at least in part. I like the fact that you can now have the same variables defined in the same way for both dev and prod. That way it is less confusing where the variables come from. We store all config in a config-repo where we've got development and production stuff defined. It's all in the same place and gets deployed when the apps are deployed, or synced automatically in development. I could understand why some developers would want to set vars on the command line and expect them to not be overwritten but in production - not really. Anyway, perhaps someone wants that too - I realize people do things differently :-).

Sorry for missing the existing issue, my bad. Anyway - a configuration option or something for this would be a very nice feature.

from dotenv.

Here's more of the philosophy that inspires dotenv: http://12factor.net/config

Anyway - a configuration option or something for this would be a very nice feature.

Pull requests welcome.

from dotenv.