Hi Jay, I really like storing config vars in .env adding the file to gitignore and it doesn't go into the database
If you didn't get enough from the heroku-config gem, there are more details are in a heroku article: https://devcenter.heroku.com/articles/config-vars#using-foreman Since foreman knows about the .env file (also written by David), locally it is quite simple to use. And it acts as a recipe to remember what to publish. If you are using pow, you may need to add add "source .env" to your .powenv you may want to check in a .env.sample file, much the same way you create a database.sample.yml file. So it is quick for people to get up to speed, but the secrets are not checked in. --Keenan On Monday, October 29, 2012 at 2:25 PM, Jay Vyas wrote: > It would be nice if heroku gave us a "bootstrap" script that could be > uploaded and downloaded, that came with default templates and commands that > we could toggle (like setting env variables and stuff). Does anything like > this exist already? Such a paradigm would be great for adding API keys and > stuff as env variables . > -- > You received this message because you are subscribed to the Google > Groups "Heroku" group. > > To unsubscribe from this group, send email to > [email protected] > (mailto:[email protected]) > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en_US?hl=en -- You received this message because you are subscribed to the Google Groups "Heroku" group. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en
