Metadot allows you to easilly manage and reuse existing dotfiles repositories
by simply cloning then to your
~/.dotfiles/modules and renaming a few files.
By being modular, it's possible to create modules for specific applications (vim, mutt, emacs, git, etc). By using git submodules or subtrees, one can even create her own dotfile collection.
It was inspired by holman does dotfiles
and many other initiatives but with a modular design to ease dotfile sharing as
metadot code is split from the dotfiles' folder.
Another approach is to use GNU Stow to manage your dotfiles.
Get the code:
git clone https://git.fluxo.info/metadot
Then check the source integrity of the latest release:
/usr/bin/git -C metadot verify-commit HEAD
/usr/bin/git is called to avoid any other
git wrappers or aliases
you might have available on your shell.
Save the metadot repository anywhere but make sure it's available in your
I'm my config I use
Then get some modules. You can get the whole standard module collection with
metadot clone https://git.fluxo.info/rhatto/dotfiles
Or simply using
metadot clone default
Modules names as
dotfiles have a special meaning and are handled like collections
and are cloned directly as
~/.dotfiles. After cloning, you can check the current
dotfiles revision using
Third-party collections will hardly suit your needs, so you can fetch individual modules:
metadot clone https://git.fluxo.info/rhatto/dotfiles/vim
Or even start your own:
metadot create vim
In both cases your
vim module will be available at
You can use just one collection at a time. While you can mixed a collection with individual modules, it's more sane to just start your own collection and keep modules as git submodules or subtrees.
The full list of commands is available with
metadot usage. You'll probably want
to start with the following.
List existing modules:
Load a module:
metadot load <module>
Load all modules:
metadot load --all
Backups are made whenever a module is loaded.
You can fetch updates in a module collection repository using
This commands don't automatically update your working copy. Instead, it just
does a git fetch in the
remotes/origin repository and display it's last
commit log including git signature.
You can check version differences using
metadot version and also standard
git commands such as
git-log(1). Once you're satisfied and want to apply
changes to the current working copy including updating and initializing
~/.dotfiles: where all dotfiles modules are stored
~/.backups: backups of old config files
~/.custom: some modules use this folder for custom configuration overriding default parameters
Modules rest at ~/.dotfiles/modules and can be git submodules or subtrees. File format is:
Which means files
- with a
.linkextension are linked at
- with a
.dot.linkextension are converted to a dotfile:
vimrc.dot.linkis linked as
- with other extensions are ignored.
- file structure is preserved:
apps/scripts.linkis linked as
- nested structures are allowed:
config.dot/awesome.linkis linked as
Comments and patches: rhatto at riseup.net