From b5ab1ff0cdf0dbd95dd4aea004207ffa066a2581 Mon Sep 17 00:00:00 2001 From: Dan Helfman Date: Wed, 5 Jun 2024 11:21:51 -0700 Subject: [PATCH] Use (current) default action order whenever actions are mentioned (#873). --- docs/how-to/deal-with-very-large-backups.md | 2 +- docs/how-to/monitor-your-backups.md | 12 ++++++------ 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/how-to/deal-with-very-large-backups.md b/docs/how-to/deal-with-very-large-backups.md index 8850ef7..8e048e1 100644 --- a/docs/how-to/deal-with-very-large-backups.md +++ b/docs/how-to/deal-with-very-large-backups.md @@ -20,7 +20,7 @@ default action ordering was `prune`, `compact`, `create`, and `check`. ### A la carte actions If you find yourself wanting to customize the actions, you have some options. -First, you can run borgmatic's `prune`, `compact`, `create`, or `check` +First, you can run borgmatic's `create`, `prune`, `compact`, or `check` actions separately. For instance, the following optional actions are available (among others): diff --git a/docs/how-to/monitor-your-backups.md b/docs/how-to/monitor-your-backups.md index 3749714..8699b7b 100644 --- a/docs/how-to/monitor-your-backups.md +++ b/docs/how-to/monitor-your-backups.md @@ -208,8 +208,8 @@ cronitor: this option in the `hooks:` section of your configuration. With this configuration, borgmatic pings your Cronitor monitor when a backup -begins, ends, or errors, but only when any of the `prune`, `compact`, -`create`, or `check` actions are run. Then, if the actions complete +begins, ends, or errors, but only when any of the `create`, `prune`, +`compact`, or `check` actions are run. Then, if the actions complete successfully or errors, borgmatic notifies Cronitor accordingly. You can configure Cronitor to notify you by a [variety of @@ -235,8 +235,8 @@ cronhub: this option in the `hooks:` section of your configuration. With this configuration, borgmatic pings your Cronhub monitor when a backup -begins, ends, or errors, but only when any of the `prune`, `compact`, -`create`, or `check` actions are run. Then, if the actions complete +begins, ends, or errors, but only when any of the `create`, `prune`, +`compact`, or `check` actions are run. Then, if the actions complete successfully or errors, borgmatic notifies Cronhub accordingly. Note that even though you configure borgmatic with the "start" variant of the @@ -368,7 +368,7 @@ loki: ``` With this configuration, borgmatic sends its logs to your Loki instance as any -of the `prune`, `compact`, `create`, or `check` actions are run. Then, after +of the `create`, `prune`, `compact`, or `check` actions are run. Then, after the actions complete, borgmatic notifies Loki of success or failure. This hook supports sending arbitrary labels to Loki. For instance: @@ -444,7 +444,7 @@ apprise: With this configuration, borgmatic pings each of the configured Apprise services when a backup begins, ends, or errors, but only when any of the -`prune`, `compact`, `create`, or `check` actions are run. (By default, if +`create`, `prune`, `compact`, or `check` actions are run. (By default, if `states` is not specified, Apprise services are only pinged on error.) You can optionally customize the contents of the default messages sent to