Personal macOS dotfiles managed with Dotbot.

This repo installs shell and tool configuration by symlinking tracked files into $HOME. It also includes a few companion workflows for Homebrew package management and Mackup-based app settings restore.

• install bootstraps the Dotbot submodule and applies install.conf.yaml
• zsh/ contains the main shell setup, sourced helper files, and prompt/tooling config
• git/, vim/, ssh/, gpg/, conda/, hg/, pypi/, cursor/, starship/ hold symlinked app configs
• claude/ holds Claude Code settings — permissions deny rules and sandbox config based on trailofbits/claude-code-config and own research
• homebrew/ contains Homebrew bootstrap and Brewfile helpers
• mackup/ stores macOS application preferences managed with Mackup

install.conf.yaml currently links:

• ~/.zshenv, ~/.zshrc, ~/.zprofile
• ~/.gitconfig, ~/.gitconfig.local, ~/.gitignore
• ~/.vimrc
• ~/.ssh/config
• ~/.gnupg/gpg.conf, ~/.gnupg/gpg-agent.conf
• ~/.condarc, ~/.hgrc, ~/.hgrc.local, ~/.pypirc
• ~/.config/starship.toml
• ~/.cursor/sandbox.json

Clone the repo with submodules, then run the installer:

git clone --recurse-submodules <repo-url> ~/dev/projects/dotfiles
cd ~/dev/projects/dotfiles
./install

Useful variants:

./install -v
./install --force-color

The installer syncs and initializes the bundled dotbot/ submodule automatically before applying links.

The shell setup is centered on zsh:

• zsh/zshenv.symlink loads Homebrew and fnm
• zsh/zprofile.symlink reapplies Homebrew after macOS path_helper
• zsh/zshrc.symlink loads zinit, caches starship init, and sources all zsh/*.zsh helper files

This repo currently expects a Homebrew-installed zinit at /opt/homebrew/opt/zinit/zinit.zsh and uses starship for the prompt.

Bootstrap Homebrew:

homebrew/install.sh

Manage packages from homebrew/Brewfile:

cd homebrew
make install-packages
make dump

Restore or back up macOS app settings:

cd mackup
make restore
make backup

• Put machine-specific or sensitive values in .local files such as git/gitconfig.local.symlink
• Keep new managed files in their domain directory with a .symlink suffix
• Add new links in install.conf.yaml using repo-relative paths
• Use create: true when a target parent directory may not exist

Examples already ignored from git include git/gitconfig.local.symlink, hg/hgrc.local.symlink, and pypi/pypirc.symlink.

1. Create the source file in the appropriate directory with a .symlink suffix.
2. Add a mapping in install.conf.yaml.
3. Run ./install.
4. Verify the symlink and the target application behavior.

• Do not edit dotbot/; it is a vendored submodule.
• Avoid committing secrets, private keys, tokens, or machine-specific credentials.