4 ms·
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 se
by clessg 11y ago
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.
- krisdol 11y agoYeah, 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
- JadeNB 11y ago> 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.
- durkie 11y agoyou still own the repo and don't have to allow changes to it and can review any changes that folks submit.
- Karunamon 11y agoJust 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.
- copsarebastards 11y agoPeople can submit changes, but you aren't obligated to accept them.
- kerkeslager 11y agoIn that spirit: https://github.com/kerkeslager/dotfiles https://github.com/kerkeslager/dotfiles
- hyperhopper 11y agoMuch more in depth: https://github.com/garybernhardt/dotfiles https://github.com/garybernhardt/dotfiles
- Axsuul 11y agoMine: https://github.com/axsuul/dotfiles https://github.com/axsuul/dotfiles
- MBlume 11y agohttps://github.com/MichaelBlume/dotfiles https://github.com/MichaelBlume/dotfiles