3 comments

[ 4.7 ms ] story [ 20.8 ms ] thread
I've always found the various solutions that use git for sharing configuration files cumbersome. I set out to make my own simple version control system, and a lightweight web application where I can browse and edit them remotely. The main idea is that file paths are aliased to short names, so from the shell I can use:

  dotfile pull emacs
and it will install https://dotfilehub.com/knoebber/emacs to ~/.emacs.d/init.el

Dotfilehub is designed to be used with the Dotfile CLI, but it doesn't require it. My goal is to make files always easily accessible. For example, I can always retrieve my vim config with:

  `curl https://dotfilehub.com/knoebber/vim > ~/.vimrc`
The web interface is built on simple HTML and is JavaScript free. I've tested it with terminal based browsers, so users can browse through files without a graphical environment.

Dotfilehub is easy to self host. See https://github.com/knoebber/dotfile for source code.

is git really more combersome than running a server that needs a database and then installing a cli to talk to that one service that I need to figure out where to run so all of my machines can access it?
I think it would easier than self hosting a git server.