From 99a8d9b39b2dddd8f3ab8d009cd8a8913f7e1e9c Mon Sep 17 00:00:00 2001 From: Patrick Jaroszewski Date: Fri, 28 Nov 2025 18:20:07 -0800 Subject: [PATCH] Update README.md --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 222c798..387a7fa 100644 --- a/README.md +++ b/README.md @@ -35,7 +35,7 @@ The following playbook was tested on the latest Debian 12, it should work on Ubu ## Backup and Restore The backup system currently backs up all the data mounts and creates a compressed archive. The archive is stored on the remote machine at the directory given by `gitea_root_backup_dir`. The Ansible controller then downloads the archive and stores it at `gitea_local_backup_dir`. -> ![NOTE] +> [!NOTE] > The backup task stops the Compose stack to avoid data corruption. There will be a short downtime. ### Creating a Backup @@ -62,7 +62,7 @@ To trigger a backup: To restore from a backup, set the `gitea_restore_backup` variable to `true`. The tasks will use the latest backup in your backups directory on the Ansible controller. You may also specify a backup file to use with `gitea_backup_file`. > [!WARNING] -> Restore operations will **completely replace** all existing Gitea data +> Restore operations will **completely replace** all existing Gitea data. ```yaml ---