mirror of
https://github.com/cupcakearmy/autorestic.git
synced 2024-12-22 08:16:25 +00:00
Update docs to explain restore hooks feature and add a migration guide
This commit is contained in:
parent
4375a38bba
commit
f43cc32ac3
@ -45,6 +45,7 @@
|
||||
>
|
||||
> [0.x → 1.0](/migration/0.x_1.0)
|
||||
> [1.4 → 1.5](/migration/1.4_1.5)
|
||||
> [1.7 → 1.8](/migration/1.7_1.8)
|
||||
|
||||
[Examples](/examples)
|
||||
[Docker](/docker)
|
||||
|
@ -55,6 +55,7 @@ version: 2
|
||||
|
||||
extras:
|
||||
hooks: &foo
|
||||
backup:
|
||||
before:
|
||||
- echo "Hello"
|
||||
after:
|
||||
|
@ -22,6 +22,7 @@ autorestic exec -b my-backend -- unlock
|
||||
extras:
|
||||
healthchecks: &healthchecks
|
||||
hooks:
|
||||
backup:
|
||||
before:
|
||||
- 'curl -m 10 --retry 5 -X POST -H "Content-Type: text/plain" --data "Starting backup for location: ${AUTORESTIC_LOCATION}" https://<healthchecks-url>/ping/<uid>/start'
|
||||
failure:
|
||||
|
@ -1,8 +1,8 @@
|
||||
# Hooks
|
||||
|
||||
If you want to perform some commands before and/or after a backup, you can use hooks.
|
||||
If you want to perform some commands before and/or after a backup or restore, you can use hooks.
|
||||
|
||||
They consist of a list of commands that will be executed in the same directory as the target `from`.
|
||||
They consist of a list of commands that will be executed in the same directory as the config file or in the `dir` directory if configured.
|
||||
|
||||
The following hooks groups are supported, none are required:
|
||||
|
||||
@ -17,6 +17,7 @@ locations:
|
||||
from: /data
|
||||
to: my-backend
|
||||
hooks:
|
||||
backup:
|
||||
before:
|
||||
- echo "One"
|
||||
- echo "Two"
|
||||
@ -27,6 +28,16 @@ locations:
|
||||
- echo "Something went wrong"
|
||||
success:
|
||||
- echo "Well done!"
|
||||
restore:
|
||||
dir: /var/www/html
|
||||
before:
|
||||
- echo "Let's restore this backup!"
|
||||
after:
|
||||
- echo "Finished to restore"
|
||||
failure:
|
||||
- echo "A problem has been encountered :("
|
||||
success:
|
||||
- echo "Successfully restored!"
|
||||
```
|
||||
|
||||
## Flowchart
|
||||
|
45
docs/markdown/migration/1.7_1.8.md
Normal file
45
docs/markdown/migration/1.7_1.8.md
Normal file
@ -0,0 +1,45 @@
|
||||
# Migration from `1.7` to `1.8`
|
||||
|
||||
## Config files
|
||||
|
||||
- The config version have been changed
|
||||
- You can now configure restore hooks
|
||||
|
||||
See detailed instructions below.
|
||||
|
||||
## Config Version
|
||||
|
||||
The version field of the config file has been changed from `2` to `3`.
|
||||
|
||||
## Hooks
|
||||
|
||||
Since `1.8` both backup and restore hooks are possible.
|
||||
For this reason, backup hooks have been moved one layer deeper, you have to move them in a `backup` object.
|
||||
|
||||
Before:
|
||||
|
||||
```yaml
|
||||
locations:
|
||||
l1:
|
||||
# ...
|
||||
from: /foo/bar
|
||||
hooks:
|
||||
before:
|
||||
- pwd
|
||||
```
|
||||
|
||||
After:
|
||||
|
||||
```yaml
|
||||
locations:
|
||||
l1:
|
||||
# ...
|
||||
from: /foo/bar
|
||||
hooks:
|
||||
backup:
|
||||
before:
|
||||
- pwd
|
||||
restore:
|
||||
after:
|
||||
- echo "My super restore hook"
|
||||
```
|
@ -2,3 +2,4 @@
|
||||
|
||||
- [From 0.x to 1.0](/migration/0.x_1.0)
|
||||
- [From 1.4 to 1.5](/migration/1.4_1.5)
|
||||
- [From 1.7 to 1.8](/migration/1.7_1.8)
|
||||
|
Loading…
Reference in New Issue
Block a user