From 6dfadc22ee2a96f7bae2e8bef1ccb45ce5ceab84 Mon Sep 17 00:00:00 2001 From: Luc Stroobant Date: Tue, 30 Jan 2018 19:42:56 +0100 Subject: [PATCH] update readme --- README.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index ec9f9d1..133bdb2 100644 --- a/README.md +++ b/README.md @@ -54,13 +54,14 @@ borgbackup_passphrase: Ahl9EiNohr5koosh1Wohs3Shoo3ooZ6p Per default the role creates a cronjob in /etc/cron.d/borg-backup running as root every day on a random hour between 0 and 5am on a random minute. Override the defaults if necessary: ``` -borgbackup_cron_user: root +borgbackup_client_user: root borgbackup_cron_day: "*" borgbackup_cron_minute: "{{ 59|random }}" borgbackup_cron_hour: "{{ 5|random }}" ``` +Override borgbackup\_client\_user where required, for example if you have a laptop with an encrypted homedir you'll have to run the backup as the user of that homedir. -Set borgbackup\_appendonly: True in host or group vars if you want append-only repositories. In that case it's possible to define a hostname in borgbackup\_management\_station where a borg prune script will be configured. +Set borgbackup\_appendonly: True in host or group vars if you want append-only repositories. In that case it's possible to define a hostname in borgbackup\_management\_station where a borg prune script will be configured. Only the management station will have permission to prune old backups for (all) clients. *Make sure to check the configured defaults for this role, which contains the list of default locations being backed up in backup_include.* Override this in your inventory where required.