Migrate role from cron to systemd

Systemd gives us the ability to monitor backup job status using existing
monitoring solutions (node exporter) and allows us greater control over
the scheduling of the backup jobs.

This introduces a breaking change that requires users to manually remove
the old repositories from the clients and redeploying them with the
role. You will have to remove the Cron job that was created by the
Ansible script, everything else will be overwritten with a run from the
newer version.

- name: Remove backup cron jobs
  ansible.builtin.cron:
    name: BORG (Application level backups)
    state: absent
  become: true
- name: Remove env for backup cron job
  ansible.builtin.cron:
    name: BORG_PASSPHRASE
    env: true
    state: absent
  become: true

Performing manual migrations on the Borg server is not required.

We now additionally support multiple Borg repositories per client host
using the `borg_backup_argument` variable.

Signed-off-by: Colin Wilk <colin.wilk@tum.de>

1 files changed, 3 insertions, 3 deletions

diff --git a/README.md b/README.md
index 1e9a634..4c2fd32 100644
--- a/README.md
+++ b/README.md
@@ -1,9 +1,9 @@
 Ansible Role: BorgBackup
 ========================
 
-An ansible role that installs and configures a cron task for BorgBackup on a
-client and (delegated) server.
-This allows you to very simply add backups to your hosts.
+An Ansible role that installs and configures a systemd service for BorgBackup on
+a client and (delegated) server.
+This allows you to very easily add backups to your hosts.
 
 The documentation assumes basic knowledge about BorgBackup. You can get up to
 speed with Borg by reading their excellent documentation on