dotfiles

Dotfiles are configuration files in Unix-like systems that begin with a dot (.) and are hidden by default. They store user preferences and settings for various applications and shells.Common dotfiles include .bashrc (Bash configuration), .vimrc (Vim settings), .gitconfig (Git settings), and .ssh/ (SSH keys and config). Managing dotfiles typically involves version control and symlink strategies.

Git bare repository: Track dotfiles with git using a bare repo and work tree alias.Symlink managers: Tools like stow, dotbot, or chezmoi create symlinks from a central repository.Version control: Keep dotfiles in a git repository for history and synchronization across machines.

Dotfiles often hold secrets: API tokens in `~/.netrc` or `~/.aws/credentials`, private keys in `~/.ssh/`, and shell history in `~/.bash_history`. Check carefully before pushing a dotfiles repository to a public host, and prefer keeping secrets outside the repository entirely rather than trying to scrub them later, since git history keeps what you removed.Hiding is purely a display convention enforced by `ls` and file managers, not a permission: anything that can read your home directory can read them. Many programs also generate dotfiles and dot-directories automatically, including caches and state that should never be version controlled. The XDG Base Directory specification exists to curb the clutter by moving configuration to `~/.config/`, cached data to `~/.cache/`, and state to `~/.local/state/`, but adoption is uneven and a typical home directory still mixes both conventions.

Hidden dotfiles are a famous accident. Early Unix directories contained the entries `.` and `..`, and to keep them out of listings someone added a test to `ls` that skipped any name beginning with a dot, rather than the two-line check that would have skipped exactly those two entries. The side effect, that *any* file starting with `.` disappears from listings, was never designed; it was simply noticed and then used. Rob Pike has recounted this as a cautionary tale, arguing that a shortcut in one program grew into a convention that every subsequent program had to know about and that today litters home directories with hundreds of entries.Treating dotfiles as a version-controlled, portable artifact came much later, alongside the spread of Git and of engineers working across many machines. The bare repository trick, where `~` itself is the work tree, and symlink managers such as GNU Stow, dotbot, chezmoi, and yadm are all responses to the same problem: configuration that took years to accumulate and takes minutes to lose.

stow(1), dotbot(1), chezmoi(1), yadm(1), ls(1), git(1)