ansible-roles/evobackup-client
Jérémy Lecour ee21973371
Ansible Lint |Total|New|Outstanding|Fixed|Trend |:-:|:-:|:-:|:-:|:-: |2777|524|2253|2462|:+1: Reference build: <a href="https://jenkins.evolix.org/job/gitea/job/ansible-roles/job/unstable/223//ansiblelint">Evolix » ansible-roles » unstable #223</a> Details
gitea/ansible-roles/pipeline/head This commit looks good Details
Use FQCN
Fully Qualified Collection Name
2023-03-20 23:33:19 +01:00
..
defaults evobackup-client now uses the default ed25519 key of the server 2020-04-24 10:36:36 -04:00
handlers Use FQCN 2023-03-20 23:33:19 +01:00
tasks Use FQCN 2023-03-20 23:33:19 +01:00
templates remove whitespace for stream redirection 2021-06-28 15:56:19 +02:00
README.md Allow heterogeneous ports 2019-09-03 10:29:05 -04:00

README.md

evobackup-client

Allows the configuration of backups to one or more remote filesystems.

The backup hosts and the ports in use need to be defined in evobackup-client__hosts before running it.

The default zzz_evobackup.sh configures a system only backup, but the template can be overriden to configure a full backup instead. If you change the variables in defaults/main.yml you can easily run this again and configure backups to a second set of hosts.

Do not forget to set the evobackup-client__mail variable to an email adress you control.

You can add this example to an installation playbook to create the ssh key without running the rest of the role.

  post_tasks:
    - include_role:
        name: evobackup-client tasks_from: ssh_key.yml