aboutsummaryrefslogtreecommitdiff
path: root/README.mdwn
blob: 475e2927098b52f8ddc7ddb08182203f7b1ea4c4 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
Metadot: modular dotfile management
===================================

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 bundle.

It was inspired by [holman does dotfiles](https://github.com/holman/dotfiles)
and many other initiatives but with a modular design to ease dotfile sharing as
the `metadot` code is split from the dotfiles' folder.

Instalation
-----------

Get the code:

    git clone git://git.sarava.org/metadot.git && cd metadot

Then check the source integrity of the latest release:

    tag="`git describe --abbrev=0 --tags`"
    git tag -v $tag && git checkout $tag

Save the metadot repository anywhere but make sure it's available in your `$PATH`.
I'm my config I use `~/apps/metadot`.

Then get some modules. You can get the whole standard module bundle with

    metadot clone git://git.sarava.org/rhatto/dotfiles.git

Or simply using

    metadot clone default

Modules names as `dotfiles` have a special meaning and are handled like bundles
and are cloned directly as `~/.dotfiles`. After cloning, you can check the current
dotfiles revision using

    metadot version

Third-party bundles will hardly suit your needs, so you can fetch individual
modules:

    metadot clone git://git.sarava.org/rhatto/dotfiles/vim.git

Or even start your own:

    metadot create vim

In both cases your `vim` module will be available at `~/.dotfiles/modules/vim`.

You can use just one bundle at a time. While you can mixed a bundle with
individual modules, it's more sane to just start your own bundle and keep
modules as git submodules or subtrees.

Usage
-----

List existing modules:

    metadot ls

Load a module:

    metadot load <module>

Load all modules:

    metadot load --all

Update a module bundle or all individual modules:

    metadot update

Backups are made whenever a module is loaded.

Layout
------

- `~/.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

Module format
-------------

Modules rest at ~/.dotfiles/modules and can be git submodules or subtrees. File format is:

    [path/]<name>[.dot][.link]

Which means files

- with a `.link` extension are linked at `$HOME`.
- with a `.dot.link` extension are converted to a dotfile: `vimrc.dot.link` is linked as `~/.vimrc`.
- with other extensions are ignored.

Also,

- file structure is preserved: `apps/scripts.link` is linked as `$HOME/apps/scripts`.
- nested structures are allowed: `config.dot/awesome.link` is linked as `$HOME/.config/awesome`.

See also
--------

* http://dotshare.it
* http://dotfiles.org
* https://dotfiles.github.io
* https://wiki.archlinux.org/index.php/Dotfiles

Contact
-------

Comments and patches: rhatto at riseup.net