You can clone the repository wherever you want. (I like to keep it in ~/Projects/dotfiles
, with ~/dotfiles
as a symlink.)
$ git clone https://github.com/olistic/dotfiles.git
When setting up a new Mac, you may want to start by installing some common Homebrew formulae and Cask native apps.
The installation script will install Homebrew with everything inside of Brewfile
, as well as Oh My Zsh!
$ ./install.sh
The bootstrapper script will pull in the latest version and copy the dotfiles to your home folder.
$ source bootstrap.sh
If ~/.path
exists, it will be sourced along with the other files, before any feature testing (such as detecting which version of ls
is being used) takes place.
Here’s an example ~/.path
file that adds /usr/local/bin
to the $PATH
:
export PATH="/usr/local/bin:$PATH"
If ~/.extra
exists, it will be sourced along with the other files. You can use this to add commands you don’t want to commit to a public repository.
My ~/.extra
looks something like this:
# Git credentials
# Not in the repository, to prevent people from accidentally committing under my name
GIT_AUTHOR_NAME="Matias Olivera"
GIT_COMMITTER_NAME="$GIT_AUTHOR_NAME"
git config --global user.name "$GIT_AUTHOR_NAME"
GIT_AUTHOR_EMAIL="moliverafreire@gmail.com"
GIT_COMMITTER_EMAIL="$GIT_AUTHOR_EMAIL"
git config --global user.email "$GIT_AUTHOR_EMAIL"
GIT_SIGNING_KEY="12081D793C943DA0"
git config --global user.signingkey "$GIT_SIGNING_KEY"
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.
When setting up a new Mac, you may also want to set some sensible macOS defaults:
$ ./macos.sh
- Mathias Bynens and his original dotfiles repository.