3 ms·
We know we shouldn't be committing password or personal key. But shit happens and it does happen very frequently, even top notched people do. What we need is n
by yeukhon 13y ago
We know we shouldn't be committing password or personal key. But shit happens and it does happen very frequently, even top notched people do.
What we need is not to say "don't it", because no shit we shouldn't be doing that. instead we need defense mechanism. It would be helpful and interesting if git or hg has a plugin that detects when some credentials is leaking through and warn users "hey you better check this shit out" before doing a real commit.
The other thing is "don't commit key into a private repository". Don't chef and puppet users usually do that? How are people backing up their keys?
- dwaltrip 13y agoFor rails, the Figaro gem is really helpful for managing environment variables, which is a good place to store credentials (the config file for Figaro is then added to .gitignore)
- yeukhon 13y agoBut how do you back up this set of environment variables. Yes, in practice I also use ignore file to prevent sensitive things leak into repository and I usually generate password dynamically on the fly or through some script.