Dotfile package manager.
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
.gitignore
README.rst
fabfile.py
requirements.txt

README.rst

dots

Modular dotfile manager. Symlinks dotfiles from plugins to HOME.

Rationale

Sharing dotfiles as a team is a nice idea, but in practice to do so requires solving several problems:

  • Not everyone uses the same apps. Vim users don't want your emacs dotfiles and vice-versa.

    Consequently, forking is not very useful. Anecdotally, people seem to just cherry-pick.

  • Putting all dotfiles in one repo makes history and documentation less useful.

  • If dotfiles are shared, decisions to change them must be conservative. It makes the most sense to have dotfiles as decentralized as possible to commit to the fewest decision-makers.

  • Many dotfiles themselves tend to be antimodular. By putting them in their own project, they can be organized (and then generated) in a more meaningful way.

What we want is a way to split up dotfiles by app, giving us meaningful history and fork-ability.

dots solves this problem by letting you easily install dotfile plugins, where a plugin is simply a directory from which dotfiles can be imported.

Installation

To install dots, simply:

git clone git@github.com:Ceasar/dots.git
cd dots
pip install -r requirements.txt

Quickstart

We can see how dots works by means of a simple example.

First we will create a simple plugin and then link it:

cd dots
mkdir plugins
cd plugins
mkdir example
echo "hello!" > example/.examplerc
echo "shows off how to make a plugin" > example/README.md

Next, we can link it to our $HOME directory:

fab link:plugins

If you check your home directory, .examplerc should exist.

Usage

dots relies on fabric. Therefore all commands are of the form:

fab COMMAND:ARG1,ARG2,..

Use fab --list to see all commands and fab -d COMMAND for detailed help.

Available commands:

link               Install each of the dotfiles from each repo or a single one.
repos.from_config  Install git repos from a config file in the directory.
repos.install      Install a git repo in the directory.
repos.uninstall    Uninstall a git repo in the directory.
repos.update       Update a git repo in the directory or all of them.

Remarks

Naturally, what you'll want to do in the future is to clone git repos into plugins and write more complex dotfiles. See Ceasar/dot_gitconfig as an example.

If you already have a dotfiles repo, the easiest way to get started is just to clone or move your repo into plugins and link it until you have time to factor everything out.

If you do not already have a dotfiles repo, dots allows you to clone other people's entire dotfiles and use them as your own! Github has kindly compiled many fantastic dotfiles that may be useful to get started.

You can also keep track of different sets of dotfiles by keeping different configurations in different folders.