Difference between revisions of "Dotfiles"

From ArchWiki
Jump to: navigation, search
(Repositories: flag dead link)
m (Confidential information: style)
Line 60: Line 60:
  some-dotfile filter=remove-pass
  some-dotfile filter=remove-pass
Whenever the file “some-dotfile” is checked into git, git will invoke the filter “remove-pass” on the file before checking it in. The filter must be defined in .git/config, e. g.:
Whenever the file “some-dotfile” is checked into git, git will invoke the filter “remove-pass” on the file before checking it in. The filter must be defined in {{ic|.git/config}}, e. g.:
[filter "remove-pass"]
[filter "remove-pass"]
clean = "sed -e 's/^password=.*/#password=TODO/'"
clean = "sed -e 's/^password=.*/#password=TODO/'"
== Repositories ==
== Repositories ==

Revision as of 08:25, 18 June 2017

This article collects user repositories with custom configuration files, commonly known as dotfiles.

Version control

Managing dotfiles with version control software such as Git helps to keep track of changes, share with others, and synchronize dotfiles across various hosts.

Using gitignore

Keeping a git directory inside the home folder allows to directly keep track of changes. It is recommended to selectively add file contents to the index with git-add(1).

To prevent untracked files (appearing in commits and removed by git-clean(1)), first exclude all files with gitignore(5):


Then use git add -f, for example:

$ git add -f ~/.config/*

And commit the changes with git-commit(1):

$ git commit -a

Other tools

  • dotbot — A minimalist dotfiles manager that can be installed as a git submodule of your dotfiles repository.
https://github.com/anishathalye/dotbot || not packaged? search in AUR
  • dotdrop — A tool to manage different versions of your dotfiles on different hosts.
https://github.com/deadc0de6/dotdrop || not packaged? search in AUR
  • dotfiles — A tool to make managing your dotfile symlinks in $HOME easy, allowing you to keep all of them in a single directory.
https://github.com/jbernard/dotfiles || dotfilesAUR
  • dotgit — A comprehensive solution to managing your dotfiles.
http://github.com/Cube777/dotgit || dotgitAUR
  • dots — A portable tool for managing a single set of dotfiles in an organized fashion.
https://github.com/EvanPurkhiser/dots || dots-managerAUR
  • etckeeper — Intended to version-control system-wide configuration in /etc. Works by keeping track of permissions and modes which version-control software often ignores. Can use various SCM systems as a backend. Hooks can auto-commit changes to the repository before a system-upgrade.
http://etckeeper.branchable.com/ || etckeeper
  • GNU Stow — Can be used to symlink dotfiles from a repository into the $HOME tree. See [1] for more information.
http://www.gnu.org/software/stow/ || stow
  • homeshick — git dotfiles synchronizer written in bash.
https://github.com/andsens/homeshick || homeshick-gitAUR
  • homesick — Your home directory is your castle. Don't leave your dotfiles behind.
https://github.com/technicalpickles/homesick || homesickAUR
  • mackup — a small Python utitlity to keep your application settings in sync.
https://github.com/lra/mackup || mackupAUR
  • Pearl — Package manager for dotfiles, plugins, programs and any form of code accessible via git. Allow to easily share and sync packages across systems and have them ready to work out of the box.
https://github.com/pearl-core/pearl || pearl-gitAUR
  • rcm — Can be used to symlink dotfiles from a repository into the $HOME tree.
https://github.com/thoughtbot/rcm || rcmAUR
  • vcsh — Allows separating differents modules (e.g., Emacs config vs. zsh config) into individual repositories which can be maintained separately, as opposed to keeping all dotfiles in a single repository. Works with git only.
https://github.com/RichiH/vcsh || vcshAUR
  • yadm — Manages files across systems using a single Git repository. Provides a way to use alternate files on a specific OS or host. Supplies a method of encrypting confidential data so it can safely be stored in your repository.
https://github.com/TheLocehiliosan/yadm || yadm-gitAUR

Maintaining dotfiles across multiple machines

Tango-edit-clear.pngThis article or section needs language, wiki syntax or style improvements.Tango-edit-clear.png

Reason: This and the section below need a rewrite (Discuss in Talk:Dotfiles#)

One way of maintaining dotfiles across various machines across various hosts while still allowing for per-host customizations, is by maintaining a master-branch for all shared configuration, while each individual machine has a machine-specific branch checked out. Host-specific configuration can be committed to the machine-specific branch; as shared configuration is added to the master-branch, the per-machine branches are then rebased on top of the updated master.

Another approach is to put machine-specific configuration into specially commented blocks and to use qualia to automatically uncomment them on each machine. This approach requires less manual work and doesn't cause merge conflicts.

Confidential information

Occasionally, software may keep plain-text passwords in configuration files, as opposed to hooking into a keyring. In these cases, git clean-filters may be handy to avoid accidentally commiting confidential information. E. g., the following .gitattributes file assigns a filter to the file “some-dotfile”:

# .gitattributes
some-dotfile filter=remove-pass

Whenever the file “some-dotfile” is checked into git, git will invoke the filter “remove-pass” on the file before checking it in. The filter must be defined in .git/config, e. g.:

[filter "remove-pass"]
clean = "sed -e 's/^password=.*/#password=TODO/'"


Author Shell (shell framework) WM / DE Editor Terminal Multiplexer Audio Monitor Mail IRC
Ambrevar zsh awesome emacs rxvt-unicode cmus htop/vicious mutt
awal fish i3 vim sakura tmux i3status The Lounge
bamos zsh i3/xmonad vim/emacs rxvt-unicode tmux mpv/cmus conky/xmobar mutt ERC
brisbin33 zsh xmonad vim rxvt-unicode screen dzen mutt irssi
bstaletic zsh dwm vim[dead link 2016-11-19] terminator screen ncmpcpp[dead link 2016-11-19] conky
cinelli zsh dwm vim termite-git pianobar htop mutt-kz weechat
drkhsh[dead link 2017-06-18] zsh dwm vim st screen cmus conky mutt weechat
Earnestly zsh i3/orbment vim/emacs termite tmux mpd conky mutt weechat
ErikBjare zsh xmonad/xfce4 vim terminator tmux xfce4-panel weechat
falconindy bash i3 vim rxvt-unicode ncmpcpp conky mutt
graysky zsh xfce4 vim terminal ncmpcpp custom thunderbird
gtmanfred[dead link 2016-11-19] zsh dwm vim termite-git tmux mpd conky mutt weechat
hugdru zsh awesome neovim rxvt-unicode tmux thunderbird weechat
insanum bash herbstluftwm vim evilvte tmux dzen mutt-kz
izmntuk zsh xfce4 vim rxvt-unicode/yaft tmux cmus xfce4-panel irssi
jasonwryan bash/zsh dwm vim rxvt-unicode tmux ncmpcpp custom mutt irrsi
jdevlieghere zsh xmonad vim terminal tmux htop mutt weechat
jelly zsh i3 vim termite tmux ncmpcpp mutt-kz-git weechat
meskarune bash herbstluftwm vim rxvt-unicode screen conky weechat
neersighted zsh i3 vim rxvt-unicode tmux ncmpcpp htop mutt irssi
OK100 bash dwm vim rxvt-unicode cmus conky, dzen mutt weechat
pid1 zsh dwm neovim st tmux custom mutt weechat
polyzen zsh i3 vim termite tmux i3status weechat
swalladge[dead link 2016-11-19] zsh/bash i3 neovim/vim termite tmux cmus i3pystatus mutt
thiagowfx bash/zsh i3 vim/emacs rxvt-unicode ncmpcpp i3blocks
unexist zsh subtle vim rxvt-unicode ncmpcpp mutt irssi
vodik zsh xmonad vim termite-git tmux ncmpcpp custom mutt weechat
w0ng zsh dwm vim rxvt-unicode tmux ncmpcpp custom mutt irssi
Wintervenom bash herbstluftwm vim rxvt-unicode screen mpd (mpc-utils) hlwm-dzen2 mutt weechat
wolfcore bash dwm vim rxvt-unicode tmux cmus custom weechat
xfausto[dead link 2016-11-19] zsh dwm vim st ncmpcpp conky
zendeavor zsh i3 vim rxvt-unicode tmux ncmpcpp i3status weechat
dillebidum zsh/mksh dwm/i3 vim/vis st tmux/dvtm ncmpcpp/mpv htop/i3blocks mutt ii/irssi

See also