This is a hard problem we've been trying to answer for a few years here is our best response: http://www.12factor.net/config
Here are my personal feelings on it: https://speakerdeck.com/schneems/millions-of-apps-deployed-presented-at-lsrc?slide=40 Secrets in source control aren't secret, could you open source your app right now if you wanted to? Config vars are our best answer to date. They also allow you to change settings without re-deploying. Saves you time and allows you to use our "releases" feature more effectively. A better question might be, why do you _need_ to keep your secrets all in one place? -- Richard Schneeman http://heroku.com @schneems (http://twitter.com/schneems) On Monday, October 29, 2012 at 12:54 PM, Alex Heaton wrote: > Like the title says, what approaches do you use for keeping private things > out of Git? > > I'm currently considering Foreman and development/production.env files. I can > check the former into git, keep the latter private. I'd rather not simply > update the heroku config vars manually, I need to keep the secrets all in one > place. > > -- > 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
