3 ms·
Don't even store sensitive data in git, it can be a bad idea: http://www.jamiembrown.com/blog/one-in-every-600-websites-has-git-exposed/ http://www.jamiembrown.
by archimedespi 11y ago
Don't even store sensitive data in git, it can be a bad idea: http://www.jamiembrown.com/blog/one-in-every-600-websites-has-git-exposed/ http://www.jamiembrown.com/blog/one-in-every-600-websites-ha...
Store credentials in environment variables.
- jessaustin 11y agoThat link is talking about a problem with e.g. .htaccess and basic directory permissions, not a problem using git per se. But yeah, put that stuff in envars.
- Huggernaut 11y agoHow would you go about making a repeatable, automated deployment if you don't store configuration information in source control to load into the environment variables?
- aaronbasssett 11y agoDepends on what you're using for your deployments, for example if you were using Puppet you might use something like https://github.com/TomPoulton/hiera-eyaml https://github.com/TomPoulton/hiera-eyaml
- Huggernaut 11y agoSorry, how does this prevent you requiring configuration in source control, or are you just suggesting that those credentials should be encrypted?
- archimedespi 11y agoConsul and Vault go a long way to achieving that. https://consul.io/ https://consul.io/ https://vault.io https://vault.io
- Huggernaut 11y agoDoesn't this just push the problem up (down?) a level in the hierarchy? I mean, you still need to deploy these and configure them with the information the rest of your deployment requires right?