Fix documentation referring to "archive_name_format" in wrong configuration section.
This commit is contained in:
parent
a9a65ebe54
commit
080c3afa0d
1 changed files with 3 additions and 3 deletions
|
@ -70,7 +70,7 @@ and borgmatic uses that format to name any new archive it creates. For
|
||||||
instance:
|
instance:
|
||||||
|
|
||||||
```yaml
|
```yaml
|
||||||
location:
|
storage:
|
||||||
...
|
...
|
||||||
archive_name_format: home-directories-{now}
|
archive_name_format: home-directories-{now}
|
||||||
```
|
```
|
||||||
|
@ -96,7 +96,7 @@ to filter archives when running supported actions.
|
||||||
For instance, let's say that you have this in your configuration:
|
For instance, let's say that you have this in your configuration:
|
||||||
|
|
||||||
```yaml
|
```yaml
|
||||||
location:
|
storage:
|
||||||
...
|
...
|
||||||
archive_name_format: {hostname}-user-data-{now}
|
archive_name_format: {hostname}-user-data-{now}
|
||||||
```
|
```
|
||||||
|
@ -116,7 +116,7 @@ If this behavior isn't quite smart enough for your needs, you can use the
|
||||||
filtering archives. For example:
|
filtering archives. For example:
|
||||||
|
|
||||||
```yaml
|
```yaml
|
||||||
location:
|
storage:
|
||||||
...
|
...
|
||||||
archive_name_format: {hostname}-user-data-{now}
|
archive_name_format: {hostname}-user-data-{now}
|
||||||
match_archives: sh:myhost-user-data-*
|
match_archives: sh:myhost-user-data-*
|
||||||
|
|
Loading…
Reference in a new issue