From mboxrd@z Thu Jan  1 00:00:00 1970
From: david.guibert@cdcsp.univ-lyon1.fr (David Guibert)
Date: Wed, 01 Apr 2009 10:41:00 +0200
Subject: [sup-talk] Config in VCS
In-Reply-To: <1238234052-sup-2032@ausone.home>
References: <49CD0B3E.9010002@cs.rpi.edu> <1238234052-sup-2032@ausone.home>
Message-ID: <1238574341-sup-4744@orsine>

Hi,

>From Nicolas Pouillard:
> Excerpts from Ethan Glasser-Camp's message of Fri Mar 27 18:22:06 +0100 2009:
> > Hi, long time reader, first time caller.
> > 
> > Many years ago I used fetchmail+Mutt to handle my mail, but all my
> > configuration was lost in a hard drive crash and I didn't have the
> > energy to recreate it. So as I look at sup, I am judging how difficult
> > it is to keep its configuration in a git repo (for easier replication
> > and backup).
> 
> About backups, I recommend sup users to make regular sup-dump's, not only
> because sup still have bugs but also because it's the only (meta)data
> needed to reconstruct your index.

For backup, I keep my configuration files into a git repository.
I create the following pre-commit hook to create automatically sup-dump's on
each commit.
$ cat > .git/hooks/pre-commit <<EOF
#/bin/sh
sup-dump > sup.dump
git add -f sup.dump
EOF

For replication, you can also define the post-update hook as
$ cat > .git/hooks/post-update <<EOF
#!/bin/sh
sup-sync --restored --restore sup.dump
EOF
which reconstruct your index when you pull new commits.
-- 
David