Re:Dotfiles are your Digital Backpack
by clessg on Tuesday August 04, 2015 @03:59AM
(#10002158)
Even better: place your dotfiles in a public repo on GitHub with an open license, so that everybody can learn from it and contribute improvements/fixes. I've seen immense value from this approach.
[ Parent
| on HN ]
Yeah, I wouldnt waste a private repo on dotfiles; however, it's important to maintain a .gitignore that ignores locations such as .bash_history, .ssh, and so on. You won't believe how many private keys, IP addresses, and user IDs are exposed on github because of people not practicing due diligence with their public dotfiles repos
Re:Dotfiles are your Digital Backpack
by kerkeslager on Tuesday August 04, 2015 @10:33AM
(#10003596)
In that spirit: https://github.com/kerkeslager/dotfiles
Re:Dotfiles are your Digital Backpack
by hyperhopper on Tuesday August 04, 2015 @11:08AM
(#10003868)
Much more in depth: https://github.com/garybernhardt/dotfiles
> everybody can … contribute improvements/fixes.
I've never worked with a public GitHub repository, so I probably just don't understand; but how do you prevent disaster when allowing other people to modify your configuration? Setting aside malicious modifications, no-one else knows your set-up like you do, and it seems like it would be easy inadvertently to get yourself into a non-recoverable state.
Just because you're posting the code publicly doesn't mean anyone can change your copy willy-nilly. There's a pull request process to go through, something that requires positive consent to do.
Re:Dotfiles are your Digital Backpack
by copsarebastards on Tuesday August 04, 2015 @10:31AM
(#10003582)
People can submit changes, but you aren't obligated to accept them.
you still own the repo and don't have to allow changes to it and can review any changes that folks submit.