aboutsummaryrefslogtreecommitdiffstats
path: root/README.md
Commit message (Collapse)AuthorAgeFilesLines
* Declare community.crypto dependencyHEADmasterColin Wilk2026-07-021-1/+9
|
* Add state: absent variableColin Wilk2026-07-021-3/+74
| | | | Allow removing configuration for repositories.
* Support custom arguments for borg createColin Wilk2026-06-291-0/+13
|
* Parametrize server-side borg userColin Wilk2026-06-281-4/+15
| | | | Adds option to choose a non-default borg backup user on the server.
* Add option to disable decryption key exportColin Wilk2026-06-281-0/+6
|
* feat: add storage quota supportColin Wilk2026-06-271-10/+68
| | | | | | | | | Add borg_storage_quota variable to limit repository storage on the borg server via --storage-quota option in authorized_keys. When not using borg_ssh_key_per_repo, all repos for a host must share the same quota setting (similar to --append-only). Per-repo SSH keys enable independent quotas per repository.
* Add support for non-root backup clientsColin Wilk2026-06-271-1/+17
|
* borg!: support multiple backups to same targetColin Wilk2026-06-271-21/+208
| | | | | | | | | | | | | | | | | | This brings support for multiple backups pointing to the same borg server, different repositories, from the same client. We support this by parsing the SSH authorized key file first and appending allowed repositories to allow independent definitions of the borg targets. So that the decryption_keys do not clash we include the repository name as well as the host in the key. This will lead to new keys being created for existing hosts in the new format. Old Format: {{ combine({inventory_hostname: borg_keys.stdout}) }} New Format: {{ combine({(inventory_hostname ~ '_' ~ borg_repo_name): borg_keys.stdout}) }} If upgrading from an older version that used just the hostname as the key, your existing `decryption_keys.yml` can be manually removed once the new format is also added.
* docs: add passphrase warning for true e2eeColin Wilk2026-06-271-0/+5
| | | | We should mention that users need to add a passphrase for true E2EE.
* Fix typo in install scriptv1.0.3Colin Wilk2024-05-111-2/+2
| | | | Signed-off-by: Colin Wilk <colin.wilk@tum.de>
* Fix correct branch in READMEv1.0.2Colin Wilk2023-11-261-1/+1
| | | | Signed-off-by: Colin Wilk <colin.wilk@tum.de>
* Add proper variables docs to READMEColin Wilk2023-11-261-31/+91
| | | | Signed-off-by: Colin Wilk <colin.wilk@tum.de>
* Migrate role from cron to systemdColin Wilk2023-11-041-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* initColin Wilk2023-05-241-0/+158
Signed-off-by: Colin Wilk <colin.wilk@tum.de>