[request] A task like figaro:heroku about dotenv HOT 7 CLOSED

+1 heroku config:push only supports a single .env file. Would be great to have something similar for Dotenv that observes environmental specific files:

dotenv heroku:push --staging

from dotenv.

+1

from dotenv.

It seems like a task like that would encourage you to put production variables in your local .env. My philosophy is that all the settings in your local .env should be development-only. The server is really the only thing that should know the production credentials.

from dotenv.

@bkeepers production credentials could be manually uploaded to the server and copied into the app using deployment recipe, would this case still adhere to your philosophy? If not could you please clarify what are the advantages of dotenv vs, say, SettingsLogic approach?

from dotenv.

I'm pretty much against anything that encourages you to store production credentials in the repository.

If not could you please clarify what are the advantages of dotenv vs, say, SettingsLogic approach?

dotenv is really just meant as a development shim for apps that conform to twelve factor principles for config like Heroku. It does not attempt to solve any of the of the application concerns that SettingsLogic or Figaro try to solve.

from dotenv.

I think we're talking at cross-purposes. There is a difference between pushing an .env file to a repo and pushing the adding the variables it contains to Heroku. Using $ heroku config:push adds all the variables from a .env file to the Heroku server - equivalent to calling $heroku config:add SOME_VAR=123 for each variable.

Environmental variables can generally be split into 2 sets: Application configuration shared across development/production/staging - configuration that is shared across environments such as TZ=Europe/London and environmental configuration that is specific to a particular server/environment.

It seems to me that a mechanism for keeping the former in sync between environments can only be a good thing. Dotenv already supports sharing envs between environments using a base .env file, so why not support keeping environments in sync by making it easy to push the variables to production or staging. Rather than encouraging people to upload envs it removes the need for it.

The second group are more debatable. Personally I find it very useful to have a single location where all my envs are stored. Obviously they aren't under source control, but it the advantage is that it greatly reduces the chances of what I think are the envs on staging or production and what I know are the envs. I currently add envs to production/staging as part of deployment, but I think it would be useful and within Dotenv's remit to offer a simple way to push the envs themselves.

from dotenv.

Having a command like this would certainly be cool. I understand that there are some legitimate uses as @1ndivisible describes, but it also could encourage people to store production creds in .env. For now, I don't think the benefits outweigh the costs.

I would encourage someone to create a dotenv-heroku gem that has this functionality.

from dotenv.