ansible-roles/evobackup-client/defaults/main.yml
Patrick Marchand 53ae27b250
All checks were successful
continuous-integration/drone/push Build is passing
evobackup-client now uses the default ed25519 key of the server
We used to prefer creating a specific one for backups, but everybody
kept thinking the wrong key was being used and "fixing" it. The
advantages of having a specific key for backups did not outweigh
the challenge of creating a culture change.
2020-04-24 10:36:36 -04:00

16 lines
589 B
YAML

---
evobackup_client__root_key_path: "/root/.ssh/id_ed25519"
evobackup_client__root_key_type: "ed25519"
evobackup_client__cron_path: "/etc/cron.daily/zzz_evobackup"
evobackup_client__cron_template_name: "zzz_evobackup"
evobackup_client__mail: null
evobackup_client__servers_fallback: -1
evobackup_client__pid_path: "/var/run/evobackup.pid"
evobackup_client__log_path: "/var/log/evobackup.log"
evobackup_client__backup_path: "/home/backup"
evobackup_client__hosts: null
# - name: "backups.example.org"
# ip: "xxx.xxx.xxx.xxx"
# fingerprint: "ecdsa-sha2-nistp256 ..."
# port: xxxx