Update README.md
This commit is contained in:
@@ -35,7 +35,7 @@ The following playbook was tested on the latest Debian 12, it should work on Ubu
|
|||||||
## Backup and Restore
|
## 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`.
|
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.
|
> The backup task stops the Compose stack to avoid data corruption. There will be a short downtime.
|
||||||
|
|
||||||
### Creating a Backup
|
### 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`.
|
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]
|
> [!WARNING]
|
||||||
> Restore operations will **completely replace** all existing Gitea data
|
> Restore operations will **completely replace** all existing Gitea data.
|
||||||
|
|
||||||
```yaml
|
```yaml
|
||||||
---
|
---
|
||||||
|
|||||||
Reference in New Issue
Block a user