You can clone the repository wherever you want. (I like to keep it in ~/code/dotfiles) The bootstrapper script will pull in the latest version and copy the files to your home folder.
git clone [email protected]:NetCE/macos-dotfiles.git && cd dotfiles && source bootstrap.shTo update, cd into your local dotfiles repository and then:
source bootstrap.shAlternatively, to update while avoiding the confirmation prompt:
set -- -f; source bootstrap.shTo install these dotfiles without Git:
https://github.com/NetCE/macos-dotfiles.git
cd; curl -#L https://github.com/NetCE/macos-dotfiles/tarball/main | tar -xzv --strip-components 1 --exclude={README.md,bootstrap.sh,.osx,LICENSE-MIT.txt}To update later on, just run that command again.
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.
Remember: Any time you think about updating .bash_profile or similar to modify your default paths, remember that it will be rewritten the next time you source dotfiles. Put path configuration into ~/.path instead, and then source your dotfiles.
Here’s an example ~/.path file that adds certain preferred keg-only brew installs to the $PATH:
# Set preferred versions of certain keg-only brew installs
PATH="/usr/local/opt/[email protected]/bin:$PATH"
PATH="/usr/local/opt/[email protected]/bin:$PATH"
If ~/.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.
Remember: Any time you think about updating .bash_profile or similar to add custom commands, remember that it will be rewritten the next time you source dotfiles. Put them into ~/.extra instead, and then source your dotfiles.
My ~/.extra looks something like this:
# Git configs
# Not in the repository, to prevent people from accidentally committing with these values
GIT_AUTHOR_NAME="Firstname Lastname"
GIT_AUTHOR_EMAIL="[email protected]"
GIT_COMMITTER_NAME="$GIT_AUTHOR_NAME"
GIT_COMMITTER_EMAIL="$GIT_AUTHOR_EMAIL"
git config --global user.name "$GIT_AUTHOR_NAME"
git config --global user.email "$GIT_AUTHOR_EMAIL"
git config --global commit.gpgsign false
git config --global pull.rebase true
echo 'eval "$(rbenv init -)"' >> ~/.bashrcYou 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 want to set some sensible macOS defaults:
./.macosWhen setting up a new Mac, you may want to install some common Homebrew formulae (after installing Homebrew, of course):
./brew.shSome of the functionality of these dotfiles depends on formulae installed by brew.sh. If you don’t plan to run brew.sh, you should look carefully through the script and manually install any particularly important ones. A good example is Bash/Git completion: the dotfiles use a special version from Homebrew.
Suggestions/improvements welcome!
| Mathias Bynens |
- @ptb and his macOS Setup repository
- Ben Alman and his dotfiles repository
- Cătălin Mariș and his dotfiles repository
- Gianni Chiappetta for sharing his amazing collection of dotfiles
- Jan Moesen and his ancient
.bash_profile+ shiny tilde repository - Lauri ‘Lri’ Ranta for sharing loads of hidden preferences
- Matijs Brinkhuis and his dotfiles repository
- Nicolas Gallagher and his dotfiles repository
- Sindre Sorhus
- Tom Ryder and his dotfiles repository
- Kevin Suttle and his dotfiles repository and macOS-Defaults project, which aims to provide better documentation for
~/.macos - Haralan Dobrev
- Anyone who contributed a patch or made a helpful suggestion
