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 _______________________________________________ sup-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/sup-talk
