I use Unison to keep my important files synchronized between machines. This is a description of how I have it arranged and to some degree automated.
I put all my important files into a directory called 'tlt'. This happens to exactly correspond with the root http directory of my website. Most things in the directory are fine to be on the web, but things that shouldn't be published are locked through file permissions and .htaccess files. I put this 'tlt' directory into my home directory:
** tlt/ - my main directory, and the root of my website
*** private/ - holds private files
**** mail/ - holds my mail
**** dotfiles/ - holds my homedir .config files
*** projects/ - all my own code projects
*** docs/ - Various documents
I then symlink a few key directories and files from my home directory into this folder. So, for example:
And so on. So to get all my settings from one machine to another, I just need to get a copy of this 'tlt' directory and make a few key symlinks. To backup all my stuff I must back up this tlt directory. This is where unison comes in.
Unison is kinda like rsync, except smarter. It keeps a database on each machine so that it can remember what the directories looked like during the most recent synchronization. So if you delete a file on one machine it knows, and if you delete it on one machine and modify it on another it can tell that there is a conflict which you must resolve by hand. After you've synchronized two hosts, resolving all conflicts, you have an identical set of files on each host. We use the notation host1->host2 meaning a synchronization between host1 and host2 initiated from host1.
I have three machines on which I want an up-to-date copy of 'tlt'. They are my own computer (Feline), my website host (Mirabel), and my laptop (Jill). Generally I will sync Feline->Mirabel and Jill->Mirabel, but I could do other combinations (and often do Jill->Feline).
Lets say I am using Feline and want to sync with Mirabel. If you simply run 'unison' it will interactively prompt you for the local and remote directory you wish to synchronize, and step you through the initial sync. It'll remember too, and when you re-run it will sync what it can and ask you about conflicts. Try it a couple times, its fun.
It stores its settings in preference files inside of ~/.unison/. Here is the preference file I use for Feline->Mirabel.
# Unison preferences file # Located at feline:/home/awwaiid/.unison/mirabel.prf # It knows how to sync feline->mirabel root = /home/awwaiid/tlt/ root = ssh://firstname.lastname@example.org//home/awwaiid/tlt ignore = Path dev ignore = Path tmp rshargs = -C
OK, here's another tip -- most of the time there aren't any conflicts. So there is a flag for unison which lets it run in batch mode. Guess what it is?
awwaiid@feline:~$ unison -batch mirabel
This runs unison, from feline to mirabel, syncing my 'tlt' directory on each and skipping any conflicts and giving a report. This is exactly what we need for cron! Here is my entry in my own crontab on feline, along with some stuff to send me shorter email reports:
10 3 * * * unison -batch -terse -contactquietly mirabel 2>&1
Every now and then I will run unison without the -batch flag to make resolve any outstanding conflicts. A conflict might happen if I edit a file on my laptop (jill) and on my desktop (feline) without bothering to synchronize inbetween. Resolution mode will let me see a diff and select which one I want to keep (or run a merge tool or whatever I like).
I tend to sync Jill by hand. Actually I have two other machines which automatically get synced, but that is just more of the same.