Merge branch '26-external-backup-on-s3' into 'main'
Resolve "external backup on S3" Closes #26 See merge request lydra/yunohost/ansible-yunohost!42
This commit is contained in:
Christophe Chaudier
commit
54d5b33e85
8 changed files with 247 additions and 84 deletions
|
|
@ -11,10 +11,11 @@ YunoHost doit déjà être installé sur votre serveur.
|
|||
## Variables du rôle
|
||||
|
||||
Les variables par défaut sont disponibles dans `default/main.yml` cependant il est possible de les surcharger selon vos besoins.
|
||||
Nous avons intégré deux systèmes de sauvegardes différents à ce rôle YunoHost :
|
||||
Nous avons intégré trois systèmes de sauvegardes différents à ce rôle YunoHost :
|
||||
|
||||
- sauvegardes natives YunoHost en local
|
||||
- sauvegardes à distance avec un [depot BorgBackup](https://borgbackup.readthedocs.io/en/stable/)
|
||||
- sauvegardes à distance avec un [dépôt BorgBackup](https://borgbackup.readthedocs.io/en/stable/)
|
||||
- sauvegardes à distance avec un [dépôt Restic](https://restic.readthedocs.io/en/stable/)
|
||||
|
||||
### Sauvegardes natives YunoHost locales
|
||||
|
||||
|
|
@ -23,7 +24,7 @@ Nous avons intégré deux systèmes de sauvegardes différents à ce rôle YunoH
|
|||
```yml
|
||||
ynh_backup:
|
||||
scheduled: True
|
||||
directory: "/data/backup"
|
||||
directory: "/data/backup/local_ynh_backups"
|
||||
scheduled_hour: "*"
|
||||
scheduled_minute: "*/30"
|
||||
scheduled_weekday: "*"
|
||||
|
|
@ -31,7 +32,6 @@ ynh_backup:
|
|||
system: True
|
||||
apps: True
|
||||
number_days_to_keep: "2"
|
||||
|
||||
```
|
||||
|
||||
- `ynh_backup.scheduled` : active la fonctionnalité de sauvegarde des applications YunoHost en mettant la valeur à `True`.
|
||||
|
|
@ -44,13 +44,12 @@ ynh_backup:
|
|||
|
||||
### Sauvegardes distantes avec BorgBackup
|
||||
|
||||
- Les sauvegardes avec [BorgBackup](https://borgbackup.readthedocs.io/en/stable/) et [Borgmatic](https://github.com/witten/borgmatic) : Grâce au rôle Ansible `m3nu.ansible_role_borgbackup` nous pouvons automatiser le processus d'installation et de configuration de BorgBackup sur un serveur YunoHost. Les sauvegardes Borg sont accessibles sur un dépôt Borg local ou distant. Plus d'info sur ce rôle [ici](https://github.com/borgbase/ansible-role-borgbackup)
|
||||
- Les sauvegardes avec [BorgBackup](https://borgbackup.readthedocs.io/en/stable/) et [Borgmatic](https://github.com/witten/borgmatic) : Grâce au rôle Ansible `m3nu.ansible_role_borgbackup`, nous pouvons automatiser le processus d'installation et de configuration de BorgBackup sur un serveur YunoHost. Les sauvegardes Borg sont accessibles sur un dépôt Borg local ou distant. Plus d'info sur ce rôle [ici](https://github.com/borgbase/ansible-role-borgbackup)
|
||||
|
||||
```yml
|
||||
ynh_borg_backup_scheduled: True
|
||||
borg_source_directories:
|
||||
- "/data/yunohost"
|
||||
borg_repository: "/data/backup/live"
|
||||
borg_source_directories: "{{ ynh_backup.directory }}"
|
||||
borg_repository: "/data/backup/borg_repository"
|
||||
borg_encryption_passphrase: "PLEASECHANGEME"
|
||||
borgmatic_config_name: "borgmatic_ynh_config"
|
||||
borgmatic_cron_name: "borgmatic_ynh_cron"
|
||||
|
|
@ -64,8 +63,8 @@ ynh_ssh_borg_command: "ssh_command: ssh -p 7410 -o StrictHostKeychecking=no -i {
|
|||
|
||||
- `ynh_borg_backup_scheduled` : Active / désactive la fonctionnalité de sauvegarde avec BorgBackup.
|
||||
- `ynh_borg_backup_remote_repo` : Active / désactive la fonctionnalité de sauvegarde sur un dépôt distant BorgBackup (tâches liées à la mise en place des clés SSH). Si vous activez cette fonctionnalité, vous aurez besoin d'utiliser les variables `borg_ssh_keys_src` et `borg_ssh_keys_dest`.
|
||||
- `borg_source_directories` : Liste des dossiers source à sauvegarder. Par défaut, il s'agit du dossier contenant toutes les données YunoHost (configuration, applications).
|
||||
- `borg_repository` : Chemin complet vers le dépôt Borg. Possibilité de donner une liste de dépôts pour sauvegarder les données dans plusieurs endroits. Par défaut, il s'agit du dépôt `/data/backup/live`.
|
||||
- `borg_source_directories` : Liste des dossiers source à sauvegarder. Par défaut, il s'agit du dossier qui contient les sauvegardes faites par YunoHost.
|
||||
- `borg_repository` : Chemin complet vers le dépôt Borg. Possibilité de donner une liste de dépôts pour sauvegarder les données dans plusieurs endroits.
|
||||
- `borg_encryption_passphrase` : **Obligatoire**, mot de passe à utiliser pour la clé de chiffrement du dépôt Borg.
|
||||
- `borgmatic_config_name` : **Optionnel**, nom du fichier de configuration Borgmatic.
|
||||
- `borgmatic_cron_name` : **Optionnel**, nom du fichier de tâche cron.
|
||||
|
|
@ -76,9 +75,64 @@ ynh_ssh_borg_command: "ssh_command: ssh -p 7410 -o StrictHostKeychecking=no -i {
|
|||
|
||||
N'hésitez pas à regarder les variables disponibles dans le [rôle](https://github.com/borgbase/ansible-role-borgbackup).
|
||||
|
||||
### Sauvegardes distantes avec Restic
|
||||
|
||||
- Les sauvegardes avec [Restic](https://restic.net/) : Grâce au rôle Ansible `do1jlr.restic`, nous pouvons automatiser le processus d'installation et de configuration de Restic sur un serveur YunoHost. Les sauvegardes Restic peuvent être effectuées sur un dépôt Restic en local ou à distance (dépôt compatible stockage objet S3). Plus d'info sur ce rôle [ici](https://github.com/roles-ansible/ansible_role_restic).
|
||||
|
||||
⚠️ Attention, pour pouvoir utiliser le rôle Ansible `do1jlr.restic`, vous devez avoir les [paquets suivants](https://github.com/roles-ansible/ansible_role_restic#requirements) installés sur la machine qui exécute Ansible :
|
||||
|
||||
- `bzip2` (binaire disponible sur la plupart des systèmes Linux).
|
||||
- `jmespath` (paquet python, installable avec pip).
|
||||
|
||||
```yml
|
||||
ynh_restic_backup_scheduled: True
|
||||
restic_create_schedule: True
|
||||
restic_keep_time: "0y2m0d0h"
|
||||
|
||||
restic_repos:
|
||||
s3_ynh_restic_repo:
|
||||
location: "s3:s3.fr-par.scw.cloud/dummy_bucket_name"
|
||||
password: "dummy_restic_repo_password"
|
||||
aws_access_key: "dummy_access_key"
|
||||
aws_secret_access_key: "dummy_secret_access_key"
|
||||
aws_default_region: "fr-par"
|
||||
init: True
|
||||
|
||||
restic_backups:
|
||||
YunoHost_remote:
|
||||
name: "remote_ynh_restic"
|
||||
repo: "s3_ynh_restic_repo"
|
||||
src: "{{ ynh_backup.directory }}"
|
||||
tags:
|
||||
- yunohost
|
||||
- remote
|
||||
keep_within: "{{ restic_keep_time }}"
|
||||
scheduled: True
|
||||
schedule_hour: 1
|
||||
schedule_minute: 0
|
||||
```
|
||||
|
||||
- `ynh_restic_backup_scheduled` : Active / désactive la fonctionnalité de sauvegarde avec Restic.
|
||||
- `restic_keep_time` : Permet de régler finement la période de temps durant laquelle les snapshots doivent être conservés. la valeur par défaut est de 1 mois `0y1m0d0h`.
|
||||
- `restic_repos`: Restic conserve les données dans des dépôts. Vous devez spécifier au moins un dépôt pour utiliser ce rôle. Un dépôt doit comporter les variables suivantes :
|
||||
- `location` : **Obligatoire**, le chemin vers le dépôt. Ça peut être un chemin local (par exemple `/data/backup`) ou un chemin vers un bucket S3 (voir l'exemple ci-dessus).
|
||||
- `password`: **Obligatoire**, mot de passe à utiliser pour le dépôt Restic.
|
||||
- `init` : Décrit si le dépôt doit être initialisé ou pas. Utilisez `false` si vous utilisez un dépôt Restic déjà initialisé.
|
||||
- ⚠️ Attention, s'il s'agit d'un dépôt stockage objet S3, vous devez fournir des variables supplémentaires pour que Restic puisse s'authentifier et accéder au fournisseur cloud (voir l'exemple ci-dessus).
|
||||
- `restic_backups`: Un backup précise un répertoire ou un fichier à sauvegarder. Il comporte les variables suivantes :
|
||||
- `name` : **Obligatoire**, ce nom de cette sauvegarde. Il doit être unique et est utilisé avec le __pruning__ et la planification.
|
||||
- `repo` : **Obligatoire**, le nom du dépôt où sauvegarder les snapshots. Ce dépôt devra avoir été déclaré au préalable (voir plus haut pour les variables à renseigner).
|
||||
- `src` : **Obligatoire**, le répertoire ou le fichier à sauvegarder.
|
||||
- `tags` : **Optionnel**, liste de tags pour ajouter des informations.
|
||||
- `keep-within` : Peut être utilisé en relation avec la variable `restic_keep_time` (dans ce cas, gardez la variable telle quelle) ou alors vous pouvez choisir une période de rétention pour chaque sauvegarde.
|
||||
- `scheduled` : Utilisez `true` si vous souhaitez mettre en place une tâche cron pour le déclenchement d'une sauvegarde à intervalle régulier. En corrélation avec `restic_create_schedule: true` (les deux doivent être à `true` pour que la tâche soit créé).
|
||||
- `schedule_[minute|hour|weekday|month]` : Permet de régler finement la planification du déclenchement de la tâche cron.
|
||||
|
||||
N'hésitez pas à regarder les variables disponibles dans le [rôle](https://github.com/roles-ansible/ansible_role_restic).
|
||||
|
||||
## Dépendances
|
||||
|
||||
Le rôle `m3nu.ansible_role_borgbackup` sera installé sur la machine exécutant Ansible pour que les tâches liées à Borg fonctionnent. Un fichier `requirements.yml` est à la racine du rôle et va télécharger le rôle (par défaut vers `~/.ansible/roles`).
|
||||
Le rôle `m3nu.ansible_role_borgbackup` et `do1jlr.restic` seront installés sur la machine exécutant Ansible pour que les tâches liées à Borg et Restic fonctionnent.
|
||||
|
||||
## Exemple de Playbook
|
||||
|
||||
|
|
|
|||
|
|
@ -11,10 +11,11 @@ YunoHost needs to be installed on your server.
|
|||
## Role Variables
|
||||
|
||||
The default variables are available in `default/main.yml` however it is possible to override them according to your needs.
|
||||
We have integrated two different backup systems to this YunoHost role:
|
||||
We have integrated three different backup systems to this YunoHost role:
|
||||
|
||||
- YunoHost native local backups
|
||||
- Remote backups with a [BorgBackup repository](https://borgbackup.readthedocs.io/en/stable/)
|
||||
- Remote backups with a [Restic repository](https://restic.readthedocs.io/en/stable/)
|
||||
|
||||
### YunoHost native local backups
|
||||
|
||||
|
|
@ -23,15 +24,14 @@ YunoHost provides its own native backup system. It is able to back up YunoHost c
|
|||
```yml
|
||||
ynh_backup:
|
||||
scheduled: True
|
||||
directory: "/data/backup"
|
||||
directory: "/data/backup/local_ynh_backups"
|
||||
scheduled_hour: "*"
|
||||
scheduled_minute: "*/30"
|
||||
scheduled_weekday: "*"
|
||||
scheduled_month: "*"
|
||||
system: True
|
||||
apps: True
|
||||
src_script: "templates/ynh_backup.sh.j2"
|
||||
dest_script: "/usr/bin"
|
||||
number_days_to_keep: "2"
|
||||
```
|
||||
|
||||
- `ynh_backup.scheduled`: Enable the YunoHost applications backup feature by setting the value to `True`.
|
||||
|
|
@ -39,7 +39,7 @@ ynh_backup:
|
|||
- `ynh_backup.scheduled_[hour|minute|weekday|month]`: modifies the scheduling of the cron task. By default, it will run every day of the year at 3am. For more information about cron time settings, this tool can be useful: <https://crontab.guru/>.
|
||||
- `ynh_backup.system`: Disable YunoHost system backup by setting the value to `False`, the default value is `True`.
|
||||
- `ynh_backup.apps`: Disable backup of YunoHost applications by setting the value to `False`, the default is `True`.
|
||||
- `ynh_backup.number_days_to_keep` : Determines the number of days to keep for the purging system, the default is 2.
|
||||
- `ynh_backup.number_days_to_keep`: Determines the number of days to keep for the purging system, the default is 2.
|
||||
- ⚠️ Beware, once you enable the local backup feature `ynh_backup.scheduled`, you cannot disable system **and** application backups. If you set `ynh_backup.system` **and** `ynh_backup.apps` to `False`, the role will fail.
|
||||
|
||||
### remote backups with YunoHost BorgBackup
|
||||
|
|
@ -48,9 +48,8 @@ ynh_backup:
|
|||
|
||||
```yml
|
||||
ynh_borg_backup_scheduled: True
|
||||
borg_source_directories:
|
||||
- "/data/yunohost"
|
||||
borg_repository: "/data/backup/live"
|
||||
borg_source_directories: "{{ ynh_backup.directory }}"
|
||||
borg_repository: "/data/backup/borg_repository"
|
||||
borg_encryption_passphrase: "PLEASECHANGEME"
|
||||
borgmatic_config_name: "borgmatic_ynh_config"
|
||||
borgmatic_cron_name: "borgmatic_ynh_cron"
|
||||
|
|
@ -59,11 +58,12 @@ borg_retention_policy:
|
|||
ynh_borg_backup_remote_repo: True
|
||||
borg_ssh_keys_src: "files/prd/ssh_keys/ynh_ed25519.vault"
|
||||
borg_ssh_keys_dest: "/home/debian/.ssh/ynh_ed25519"
|
||||
ynh_ssh_borg_command: "ssh_command: ssh -p 7410 -o StrictHostKeychecking=no -i {{ borg_ssh_keys_dest }}"
|
||||
```
|
||||
|
||||
- `ynh_borg_backup_scheduled`: Enable / disable the backup feature with BorgBackup.
|
||||
- `ynh_borg_backup_remote_repo`: Enable / disable the backup functionality on a BorgBackup remote repository (tasks related to SSH keys setup). If you enable this feature, then you will need to use `borg_ssh_keys_src` and `borg_ssh_keys_dest` variables.
|
||||
- `borg_source_directories`: List of source folders to back up. By default, this is the folder containing all YunoHost data (configuration, applications).
|
||||
- `borg_source_directories`: List of source folders to back up. By default, this is the folder in which YunoHost local backups are located.
|
||||
- `borg_repository`: Full path to the Borg repository. Possibility to give a list of repositories to save data in several places.
|
||||
- `borg_encryption_passphrase` : **Mandatory**, password to use for the Borg repository encryption key.
|
||||
- `borgmatic_config_name`: **Optional**, name of the Borgmatic configuration file.
|
||||
|
|
@ -75,9 +75,64 @@ borg_ssh_keys_dest: "/home/debian/.ssh/ynh_ed25519"
|
|||
|
||||
Feel free to look at the variables available in the [role](https://github.com/borgbase/ansible-role-borgbackup).
|
||||
|
||||
### remote backups with YunoHost Restic
|
||||
|
||||
- Backups with [Restic](https://restic.net/): Thanks to the Ansible role `do1jlr.restic` we can automate the installation and configuration process of Restic on a YunoHost server. Restic backups can be done on a local or a remote Restic repository and compatible with S3 object storage. More info about this role [here](https://github.com/roles-ansible/ansible_role_restic).
|
||||
|
||||
⚠️ Be careful, in order to use the Ansible role `do1jlr.restic`, you must have the following [packages](https://github.com/roles-ansible/ansible_role_restic#requirements) installed on the machine running Ansible:
|
||||
|
||||
- `bzip2` (binary available on most Linux systems).
|
||||
- `jmespath` (python package, can be installed through pip).
|
||||
|
||||
```yml
|
||||
ynh_restic_backup_scheduled: True
|
||||
restic_create_schedule: True
|
||||
restic_keep_time: "0y2m0d0h"
|
||||
|
||||
restic_repos:
|
||||
s3_ynh_restic_repo:
|
||||
location: "s3:s3.fr-par.scw.cloud/dummy_bucket_name"
|
||||
password: "dummy_restic_repo_password"
|
||||
aws_access_key: "dummy_access_key"
|
||||
aws_secret_access_key: "dummy_secret_access_key"
|
||||
aws_default_region: "fr-par"
|
||||
init: True
|
||||
|
||||
restic_backups:
|
||||
YunoHost_remote:
|
||||
name: "remote_ynh_restic"
|
||||
repo: "s3_ynh_restic_repo"
|
||||
src: "{{ ynh_backup.directory }}"
|
||||
tags:
|
||||
- yunohost
|
||||
- remote
|
||||
keep_within: "{{ restic_keep_time }}"
|
||||
scheduled: True
|
||||
schedule_hour: 1
|
||||
schedule_minute: 0
|
||||
```
|
||||
|
||||
- `ynh_restic_backup_scheduled`: Enable / disable the backup feature with Restic.
|
||||
- `restic_keep_time`: Allows to fine tune the time period during which snapshots should be kept. The default value is 1 month `0y1m0d0h`.
|
||||
- `restic_repos`: Restic keeps data in repositories. You must specify at least one repository to use this role. A repository must have the following variables:
|
||||
- `location`: **Mandatory**, the path to the repository. This can be a local path (e.g. `/data/backup`) or a path to an S3 bucket (see example above).
|
||||
- `password`: **Mandatory**, password to use for the Restic repository.
|
||||
- `init`: Describes whether the repository should be initialized or not. Use `false` if you are using an already initialized Restic repository.
|
||||
- ⚠️ Beware, if this is an S3 object storage repository, you must provide additional variables for Restic to authenticate and access the cloud provider (see example above).
|
||||
- `restic_backups`: A backup specifies a directory or file to be backed up. It has the following variables:
|
||||
- `name` : **Mandatory**, this name of this backup. It must be unique and is used with the __pruning__ and scheduling.
|
||||
- `repo`: **Mandatory**, the name of the repository where to save the snapshots. This repository should have been declared beforehand (see above for variables to fill in).
|
||||
- `src` : **Mandatory**, the directory or file to be backed up.
|
||||
- `tags`: **Optional**, list of tags to add information.
|
||||
- `keep-within`: Can be used in connection with the `restic_keep_time` variable (in this case, keep this variable as it is) or you can choose a retention period for each backup.
|
||||
- `scheduled`: Use `true` if you want to set up a cron job to trigger a backup at regular intervals. In correlation with `restic_create_schedule: true` (both need to be set to `true` for the cron task to be created).
|
||||
- `schedule_[minute|hour|weekday|month]`: Allows you to fine-tune the timing of the cron job.
|
||||
|
||||
Feel free to look at the variables available in the [role](https://github.com/roles-ansible/ansible_role_restic).
|
||||
|
||||
## Dependencies
|
||||
|
||||
The `m3nu.ansible_role_borgbackup` role will be installed on the machine running Ansible for Borg-related tasks to work. A `requirements.yml` file is in the root of the role and will download the role (by default to `~/.ansible/roles`).
|
||||
The `m3nu.ansible_role_borgbackup` and `do1jlr.restic` roles will be installed on the machine running Ansible for Borg and Restic related tasks to work.
|
||||
|
||||
## Example Playbook
|
||||
|
||||
|
|
|
|||
|
|
@ -25,8 +25,16 @@ ynh_backup:
|
|||
# Variables for YunoHost BorgBackup
|
||||
ynh_borg_backup_scheduled: False
|
||||
borg_source_directories:
|
||||
- "/data/yunohost"
|
||||
borg_repository: "/data/backup/live"
|
||||
- "/home/yunohost.backup"
|
||||
borg_repository: "/data/backup/borg_repository"
|
||||
borg_init_command: "borgmatic init -c /etc/borgmatic/{{ borgmatic_config_name }} -e repokey --syslog-verbosity 1"
|
||||
borg_archive_name_format: "'{hostname}-yunohost-live-data-{now:%Y-%m-%d-%H%M%S}'"
|
||||
ynh_borg_backup_remote_repo: False
|
||||
|
||||
# Variables for YunoHost Restic
|
||||
# https://github.com/roles-ansible/ansible_role_restic
|
||||
ynh_restic_backup_scheduled: False
|
||||
do1jlr_restic_version: "v0.7.1"
|
||||
restic_version: "0.12.1"
|
||||
restic_schedule_type: "cronjob"
|
||||
restic_keep_time: "0y1m0d0h"
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@
|
|||
# #
|
||||
#-----------------------------------------------------------------------------#
|
||||
- name: Download BorgBackup role on localhost
|
||||
ansible.builtin.command: ansible-galaxy install m3nu.ansible_role_borgbackup,v0.9.0 -p ~/.ansible/roles
|
||||
ansible.builtin.command: ansible-galaxy install m3nu.ansible_role_borgbackup,v0.9.0 -p "{{ _ansible_role_directory }}"
|
||||
delegate_to: localhost
|
||||
become: False
|
||||
tags:
|
||||
|
|
|
|||
|
|
@ -17,15 +17,21 @@
|
|||
# along with this program. If not, see <http://www.gnu.org/licenses/>. #
|
||||
# #
|
||||
#-----------------------------------------------------------------------------#
|
||||
|
||||
- name: Enable Yunohost apps backup
|
||||
- name: Enable Yunohost local backups
|
||||
ansible.builtin.include_tasks: backup.yml
|
||||
when: ynh_backup.scheduled
|
||||
tags: backup
|
||||
|
||||
- name: Use Borg Backup with YunoHost
|
||||
- name: Use BorgBackup with YunoHost
|
||||
ansible.builtin.include_tasks: borgbackup.yml
|
||||
when: ynh_borg_backup_scheduled
|
||||
tags:
|
||||
- backup
|
||||
- borg
|
||||
|
||||
- name: Use Restic with YunoHost
|
||||
ansible.builtin.include_tasks: restic.yml
|
||||
when: ynh_restic_backup_scheduled
|
||||
tags:
|
||||
- backup
|
||||
- restic
|
||||
|
|
|
|||
39
roles/ynh_backup/tasks/restic.yml
Normal file
39
roles/ynh_backup/tasks/restic.yml
Normal file
|
|
@ -0,0 +1,39 @@
|
|||
---
|
||||
#-----------------------------------------------------------------------------#
|
||||
# ansible-yunohost allows to deploy Yunohost using Ansible #
|
||||
# Copyright 2021-present Lydra https://www.lydra.fr/ #
|
||||
# #
|
||||
# this program is free software: you can redistribute it and/or modify #
|
||||
# it under the terms of the GNU General Public License as published by #
|
||||
# the Free Software Foundation, either version 3 of the License, or #
|
||||
# (at your option) any later version. #
|
||||
# #
|
||||
# this program is distributed in the hope that it will be useful, #
|
||||
# but WITHOUT ANY WARRANTY; without even the implied warranty of #
|
||||
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the #
|
||||
# GNU General Public License for more details. #
|
||||
# #
|
||||
# You should have received a copy of the GNU General Public License #
|
||||
# along with this program. If not, see <http://www.gnu.org/licenses/>. #
|
||||
# #
|
||||
#-----------------------------------------------------------------------------#
|
||||
- name: Download Restic role on localhost
|
||||
ansible.builtin.command: "ansible-galaxy install do1jlr.restic,{{ do1jlr_restic_version }} -p {{ _ansible_role_directory }}"
|
||||
delegate_to: localhost
|
||||
become: False
|
||||
tags:
|
||||
- backup
|
||||
- restic
|
||||
|
||||
- name: Gather facts for Restic role
|
||||
ansible.builtin.setup:
|
||||
tags:
|
||||
- backup
|
||||
- restic
|
||||
|
||||
- name: Run Restic role
|
||||
ansible.builtin.import_role:
|
||||
name: do1jlr.restic
|
||||
tags:
|
||||
- backup
|
||||
- restic
|
||||
|
|
@ -22,3 +22,4 @@
|
|||
ynh_backup_src_script: "templates/ynh_backup.sh.j2"
|
||||
ynh_backup_dest_script: "/usr/local/bin/ynh_backup.sh"
|
||||
_ynh_backup_directory: "/home/yunohost.backup/archives"
|
||||
_ansible_role_directory: "~/.ansible/roles"
|
||||
|
|
|
|||
Loading…
Reference in a new issue