The easy metafile manager

NPM Version Build Status Build Status Dependency Status MIT LICENSE

Why use a metafile manager?

Reduce the cost of managing numerous metafiles

npm, grunt, bower, gulp, component, jshint, editorconfig, travis, saucelab, and the list goes on
With more and more convenient front-end development tools, that means more and more metafiles that you have to manage. This leads to the post-clone initialization process growing increasingly complex, not to mention an ugly root directory.

Enter chest.js

Manage your dotfiles

Bring your dotfiles to your local as "~/.chest" direcotry:
$ cd ~
$ git clone .chest

By running this, your dotfiles will be rolled out to your home directory as a symlink file:

$ ls

$ ls .chest .emacs.d .chestignore
.git .gitignore .tmux.conf .vim .vimrc .zshrc

$ chest open
.emacs.d .chest .tmux.conf .vim .vimrc .zshrc


You can ignore some files to create symlinkes like .git, .gitignore and by .chestignore:

Getting Started contains more detailed instructions on using chest in your projects.

Logo Image

Created by @watilde