History

Mathieu Trossevin 7c632352a0 Replace the `include` module with `include_tasks` or `import_tasks` The behaviour of the `include` module is badly defined (it try to choose between statically importing the tasks and dynamically including them) and can cause problems depending on any number of constraints (mostly if it choose the wrong behaviour). Replace it with the `import_tasks` (always statically import tasks) unless the `include` is in a loop in which case we replace it with `include_tasks` (always dynamically include tasks).		2023-01-03 14:43:42 +01:00
..
defaults	evobackup-client now uses the default ed25519 key of the server	2020-04-24 10:36:36 -04:00
handlers	minifirewall: fix failed_when conditions on restart	2022-05-10 16:40:45 +02:00
tasks	Replace the `include` module with `include_tasks` or `import_tasks`	2023-01-03 14:43:42 +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