Feature/Enhancement: Option for separate backup sets about duplicity-backup.sh HOT 3 CLOSED

I think that the possibility to specify the config file to use on the command line enables already the possibility to have such a backup strategy:

• create(/copy) one config file per folder which should be backuped in a different backup set
• in your cronjob, call the script by passing each time a different config file

For example (in the cronjob):

test -x /path/to/duplicity-backup/duplicity-backup.sh || exit 0
/path/to/duplicity-backup/duplicity-backup.sh -c /etc/duplicity-backup.foo.conf --backup
/path/to/duplicity-backup/duplicity-backup.sh -c /etc/duplicity-backup.bar.conf --backup
/path/to/duplicity-backup/duplicity-backup.sh -c /etc/duplicity-backup.foobar.conf --backup

Not sure if it's worth to embed such a system in the script logic when it's already simple to do it through config files... Moreover, such a work (of creating different config files) would usually be made once by the user (before the first backup), so I don't think that's such a hassle to do it like that.

I'm still open to counter-arguments and implementation suggestions ;)

from duplicity-backup.sh.

oops, sorry for the close/open, was discovering Github's issues mobile app...

from duplicity-backup.sh.

np ;)
I think this issue can be closed anyway. I didn't think of handling this by using separate config files - which isn't indeed a hassle to do it.

from duplicity-backup.sh.