Storing your CLI config files (.bash_profile and all the rest) on github makes sense - as a backup, but also to compare and learn.
Using Git and the bootstrap script
I have a cloned version of the dotfile directory on my machine. To update
cd path/to/dotfile/clone git pull origin master ./bootstrap.sh #./bootstrap.sh -f to avoid the prompt . ~/.bash_profile
I have no problem with putting the path under github - there's no confidential stuff in there.
Add custom commands without creating a new fork
~/.extra exists, it will be sourced along with the other files. You can use this to add a few custom commands without the need to fork this entire repository, or to add commands you don’t want to commit to a public repository.
~/.extra looks something like this:
# Git credentials # Not in the repository, to prevent people from accidentally committing under my name GIT_AUTHOR_NAME="Fritz Stelluto" GIT_COMMITTER_NAME="$GIT_AUTHOR_NAME" git config --global user.name "$GIT_AUTHOR_NAME" GIT_AUTHOR_EMAIL="xxxxxxx" GIT_COMMITTER_EMAIL="$GIT_AUTHOR_EMAIL" git config --global user.email "$GIT_AUTHOR_EMAIL"
You could also use
~/.extra to override settings, functions and aliases from my dotfiles repository. It’s probably better to fork this repository instead, though.
Sensible OS X defaults
When setting up a new Mac, you may want to set some sensible OS X defaults:
Install Homebrew formulae
When setting up a new Mac, you may want to install some common Homebrew formulae (after installing Homebrew, of course):
brew bundle ~/Brewfile
Install native apps with
You could also install native apps with