From: david.guibert@cdcsp.univ-lyon1.fr (David Guibert)
Subject: [sup-talk] Config in VCS
Date: Wed, 01 Apr 2009 10:41:00 +0200 [thread overview]
Message-ID: <1238574341-sup-4744@orsine> (raw)
In-Reply-To: <1238234052-sup-2032@ausone.home>
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
prev parent reply other threads:[~2009-04-01 8:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 17:22 Ethan Glasser-Camp
2009-03-28 10:03 ` Nicolas Pouillard
2009-03-31 4:57 ` Ethan Glasser-Camp
2009-03-31 11:39 ` Nicolas Pouillard
2009-03-31 13:36 ` Ben Walton
2009-04-01 8:41 ` David Guibert [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1238574341-sup-4744@orsine \
--to=david.guibert@cdcsp.univ-lyon1.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox