it would be nice if the backup could be pushed in a remote SCM (e.g. in my configuration: git).
Summarized it could be done like this:
- Check if the target directory is in a SCM (for git: check if .git directory is present)
- Automatic backup
- Stage the backup files and commit
- Push to origin (the remote repository)
Alternative to that, let the user run a shell script after backups.
When stored in a SCM the naming scheme is disturbing, as the files should get overwritten each time a backup is running.
So if thinBackup creates "backups/FULL-2011-12-01_12-15/" and "backups/FULL-2011-12-08_12-15/" it is not possible to directly put them in a SCM without moving files around or it will create duplicate content.