Dotfiles: Difference between revisions

From ArchWiki
(flag article for moving to Managing dotfiles)
(revert to latest version by Lahwaacz, imma make a draft)
Line 1: Line 1:
{{Lowercase title}}
[[Category:Configuration files]]
[[Category:Configuration files]]
[[Category:Configuration management]]
[[Category:Configuration management]]
[[ja:ドットファイル]]
[[ja:ドットファイル]]
[[pt:Dotfiles]]
[[pt:Dotfiles]]
{{Move|Managing dotfiles|Article is mainly about managing dotfiles.}}
{{Related articles start}}
{{Related articles start}}
{{Related|XDG Base Directory support}}
{{Related|XDG Base Directory support}}
Line 10: Line 10:
This article collects user repositories with custom configuration files, commonly known as ''dotfiles''.
This article collects user repositories with custom configuration files, commonly known as ''dotfiles''.


== Managing dotfiles with Git ==
== Version control ==


Managing dotfiles with [[version control system]]s such as [[Git]] helps to keep track of changes, share with others, and synchronize dotfiles across various hosts.
Managing dotfiles with [[version control system]]s such as [[Git]] helps to keep track of changes, share with others, and synchronize dotfiles across various hosts.
Line 30: Line 30:


  $ git commit -a
  $ git commit -a
=== Other tools ===
* {{App|dotdrop|A tool to manage your dotfiles across different hosts and saving them to git without duplicates.|https://github.com/deadc0de6/dotdrop|{{AUR|dotdrop}}}}
* {{App|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|{{AUR|dotfiles}}}}
* {{App|dotgit|A comprehensive solution to managing your dotfiles.|http://github.com/Cube777/dotgit|{{AUR|dotgit}}}}
* {{App|dots|A portable tool for managing a single set of dotfiles in an organized fashion.|https://github.com/EvanPurkhiser/dots|{{AUR|dots-manager}}}}
* {{App|[[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/|{{Pkg|etckeeper}}}}
* {{App|GNU Stow|Can be used to symlink dotfiles from a repository into the $HOME tree. See [http://brandon.invergo.net/news/2012-05-26-using-gnu-stow-to-manage-your-dotfiles.html] for more information.|http://www.gnu.org/software/stow/|{{Pkg|stow}}}}
* {{App|homeshick|git dotfiles synchronizer written in bash.|https://github.com/andsens/homeshick|{{AUR|homeshick-git}}}}
* {{App|homesick|Your home directory is your castle. Don't leave your dotfiles behind.|https://github.com/technicalpickles/homesick|{{AUR|homesick}}}}
* {{App|mackup|a small Python utitlity to keep your application settings in sync.|https://github.com/lra/mackup|{{AUR|mackup}}}}
* {{App|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|{{AUR|pearl-git}}}}
* {{App|rcm|Can be used to symlink dotfiles from a repository into the $HOME tree.|https://github.com/thoughtbot/rcm|{{AUR|rcm}}}}
* {{App|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|{{AUR|vcsh}}}}
* {{App|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|{{AUR|yadm-git}}}}


=== Maintaining dotfiles across multiple machines ===
=== Maintaining dotfiles across multiple machines ===
Line 36: Line 52:


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.
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.
The drawback on having some of the configuration files in multiple branches is that you have to remember to maintain and synchronize changes. Use conditional logic to minimize the number of machine specific files. For example, bash scripts (i.e. {{ic|.bashrc}}) can apply different configuration depending on the machine name (or type, custom variable, etc.):
if <nowiki>[[ "$(uname -n)" == "archlaptop" ]];</nowiki> then
    # laptop specific commands here
else
    # desktop or server machine commands
fi


Another approach is to manage machine-specific configuration with tools based on template engines, e.g. [https://pypi.python.org/pypi/mir.qualia/ qualia] or [https://github.com/deadc0de6/dotdrop Dotdrop]. This approach requires less manual work and doesn't cause merge conflicts.
Another approach is to manage machine-specific configuration with tools based on template engines, e.g. [https://pypi.python.org/pypi/mir.qualia/ qualia] or [https://github.com/deadc0de6/dotdrop Dotdrop]. This approach requires less manual work and doesn't cause merge conflicts.
Line 61: Line 69:
clean = "sed -e 's/^password=.*/#password=TODO/'"
clean = "sed -e 's/^password=.*/#password=TODO/'"
</nowiki>}}
</nowiki>}}
== Tools ==
* {{App|dotdrop|A tool to manage your dotfiles across different hosts and saving them to git without duplicates.|https://github.com/deadc0de6/dotdrop|{{AUR|dotdrop}}}}
* {{App|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|{{AUR|dotfiles}}}}
* {{App|Dots|A portable tool for managing a single set of dotfiles in an organized fashion.|https://github.com/EvanPurkhiser/dots|{{AUR|dots-manager}}}}
* {{App|GNU Stow|Can be used to symlink dotfiles from a repository into the $HOME tree. See [http://brandon.invergo.net/news/2012-05-26-using-gnu-stow-to-manage-your-dotfiles.html] for more information.|https://www.gnu.org/software/stow/|{{Pkg|stow}}}}
* {{App|Mackup|a small Python utitlity to keep your application settings in sync.|https://github.com/lra/mackup|{{AUR|mackup}}}}
* {{App|rcm|Can be used to symlink dotfiles from a repository into the $HOME tree.|https://github.com/thoughtbot/rcm|{{AUR|rcm}}}}
=== Tools wrapping Git ===
* {{App|dotgit|A comprehensive solution to managing your dotfiles.|https://github.com/Cube777/dotgit|{{AUR|dotgit}}}}
* {{App|[[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/|{{Pkg|etckeeper}}}}
* {{App|homeshick|git dotfiles synchronizer written in bash.|https://github.com/andsens/homeshick|{{AUR|homeshick-git}}}}
* {{App|homesick|Your home directory is your castle. Don't leave your dotfiles behind.|https://github.com/technicalpickles/homesick|{{AUR|homesick}}}}
* {{App|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|{{AUR|pearl-git}}}}
* {{App|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|{{AUR|vcsh}}}}
* {{App|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://thelocehiliosan.github.io/yadm/|{{AUR|yadm-git}}}}
=== Comparison ===
{{Expansion|Fill in the blanks.}}
{| class="wikitable sortable"
! Name !! Package !! Written in !! Versioning !! Host-specific<br>configuration
|-
! [https://deadc0de.re/dotdrop/ dotdrop]
| {{AUR|dotdrop}} || Python || {{No}} || {{Yes}}
|-
! [https://github.com/jbernard/dotfiles dotfiles]
| {{AUR|dotfiles}} || Python || {{No}} || ?
|-
! [https://github.com/kobus-v-schoor/dotgit dotgit]
| {{AUR|dotgit}} || Bash || {{G|wraps [[Git]]}} || ?
|-
! [https://github.com/EvanPurkhiser/dots Dots]
| {{AUR|dots-manager}} || Python || {{No}}<sup>1)</sup> || ?
|-
! [[etckeeper]]
| {{Pkg|etckeeper}} || Shell || {{G|multiple VCSs}} || ?
|-
! [https://www.gnu.org/software/stow/ GNU Stow]
| {{Pkg|stow}} || Perl || {{No}} || {{Y|Partial}}<sup>2)</sup>
|-
! [https://github.com/andsens/homeshick homeshick]
| {{AUR|homeshick-git}} || Bash || {{G|wraps [[Git]]}} || ?
|-
! [https://github.com/technicalpickles/homesick homesick]
| {{AUR|homesick}} || Ruby || {{G|wraps [[Git]]}} || ?
|-
! [https://github.com/lra/mackup Mackup]
| {{AUR|mackup}} || Python || {{No}} || ?
|-
! [https://github.com/pearl-core/pearl Pearl]
| {{AUR|pearl-git}} || Bash || {{G|wraps [[Git]]}} || ?
|-
! [https://github.com/thoughtbot/rcm rcm]
| {{AUR|rcm}} || Perl || {{No}} || {{Yes}}
|-
! [https://github.com/RichiH/vcsh vcsh]
| {{AUR|vcsh}} || Shell || {{G|wraps [[Git]]}} || {{Y|Partial}}<sup>2)</sup>
|-
! [https://thelocehiliosan.github.io/yadm/ yadm]
| {{AUR|yadm-git}} || Shell || {{G|wraps [[Git]]}} || {{Yes|https://thelocehiliosan.github.io/yadm/docs/alternates}}
|}
# Just wraps {{man|1|git-diff}}.
# Requires different commands on different hosts.


== Repositories ==
== Repositories ==

Revision as of 17:47, 12 January 2019

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

Version control

Managing dotfiles with version control systems 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):

~/.git/info/exclude
*

Then use git add -f, for example:

$ git add -f ~/.config/*

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

$ git commit -a

Other tools

  • dotdrop — A tool to manage your dotfiles across different hosts and saving them to git without duplicates.
https://github.com/deadc0de6/dotdrop || dotdropAUR
  • 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

This article or section needs language, wiki syntax or style improvements. See Help:Style for reference.

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 manage machine-specific configuration with tools based on template engines, e.g. qualia or Dotdrop. 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 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 the git-configuration file, e. g.:

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

Repositories

Author Shell (Shell framework) WM / DE Editor Terminal Multiplexer Audio Monitor Mail IRC
alfunx zsh awesome vim kitty tmux ncmpcpp/mpd htop/lain thunderbird
Ambrevar zsh awesome emacs rxvt-unicode cmus htop/vicious mutt
awal fish i3 vim st tmux i3status The Lounge
ayekat zsh karuiwm vim rxvt-unicode tmux ncmpcpp/mpd karuibar mutt irssi
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
BVollmerhaus bash i3-gaps kakoune rxvt-unicode polybar thunderbird
cinelli zsh dwm vim termite-git pianobar htop mutt-kz weechat
dikiaap zsh i3-gaps neovim alacritty tmux i3blocks
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
hugdru zsh awesome neovim rxvt-unicode tmux thunderbird weechat
insanum bash herbstluftwm vim evilvte tmux dzen mutt-kz
jasonwryan bash/zsh dwm vim rxvt-unicode tmux ncmpcpp custom mutt irssi
jdevlieghere zsh xmonad vim terminal tmux htop mutt weechat
jelly zsh i3 vim termite tmux ncmpcpp mutt-kz-git weechat
maximbaz zsh i3-gaps neovim kitty py3status thunderbird
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
pablox-cl zsh (zplug) gnome3 neovim kitty
reisub0 bash awesome neovim termite mpd conky
sistematico zsh/fish/bash i3-gaps vim/nano termite tmux ncmpcpp polybar mutt weechat
sitilge zsh awesome neovim termite thunderbird
swalladge zsh/bash i3 neovim/vim termite tmux cmus i3pystatus mutt
SyfiMalik zsh i3 vim rxvt-unicode tmux ncmpcpp/mpd polybar mutt weechat
thiagowfx bash/zsh i3 vim/emacs rxvt-unicode ncmpcpp i3blocks
unexist[dead link 2018-05-29] 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
whitelynx fish i3 neovim kitty i3pystatus
Wintervenom bash herbstluftwm vim rxvt-unicode screen mpd (mpc-utils) hlwm-dzen2 mutt weechat
wolfcore bash dwm vim rxvt-unicode tmux cmus custom weechat
zendeavor zsh i3 vim rxvt-unicode tmux ncmpcpp i3status weechat

See also