Using git and github to manage your dotfiles(blog.smalleycreative.com)
blog.smalleycreative.com
Using git and github to manage your dotfiles
http://blog.smalleycreative.com/tutorials/using-git-and-github-to-manage-your-dotfiles/
1 comments
For things that allow this like Emacs and Bash, I separate things into (for example) a config and a config-private repo. The config repo I put on github, and the private repo on my own server.
Then, with the public config file (~/.emacs.d/init.el and ~/.bashrc) I load a file based on the hostname that contains location-specific and private information.
This is useful because I can use the same framework at work and on personal machines. I don't have to mix the two.
Then, with the public config file (~/.emacs.d/init.el and ~/.bashrc) I load a file based on the hostname that contains location-specific and private information.
This is useful because I can use the same framework at work and on personal machines. I don't have to mix the two.
As someone who keeps his dotfiles on Github (but is sure, for the moment at least, that there's nothing sensitive in there) I'm having a hard time imagining what sort of sensitive information a shell alias or a vim macro could expose to a potential attacker. Can you be more specific?
.ssh or .ec2 or any other api keys set as env within .bashrc comes to mind.
Agreed, run a local git repo and never expose your sensitive environment settings.
Replace Github with Dropbox and you'll be a lot safer. You can still use Git to manage revisions. That part of the idea was fine. Just don't have the remote repository on a public service unless you are sure you can avoid errors.