From 79164e3de0c3d52f3b821b2d6493a0f39e855f06 Mon Sep 17 00:00:00 2001 From: ninjabenji <76439609+ninjabenji@users.noreply.github.com> Date: Wed, 6 Apr 2022 21:28:25 +0100 Subject: [PATCH 1/3] Add lower case warning for backend name If uppercase characters are used in a backend name a check (and I assume other actions) will fail. --- docs/markdown/backend/overview.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/markdown/backend/overview.md b/docs/markdown/backend/overview.md index 0c2092a..ca7de86 100644 --- a/docs/markdown/backend/overview.md +++ b/docs/markdown/backend/overview.md @@ -1,6 +1,7 @@ # 💽 Backends Backends are the outputs of the backup process. Each location needs at least one. +Note: names of backends MUST be lower case! ```yaml | .autorestic.yml version: 2 From a3e539b0b7d69df7d4b3f4dbc299b46baaafd292 Mon Sep 17 00:00:00 2001 From: ninjabenji <76439609+ninjabenji@users.noreply.github.com> Date: Thu, 7 Apr 2022 10:00:28 +0100 Subject: [PATCH 2/3] Add line break in documentation --- docs/markdown/backend/overview.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/markdown/backend/overview.md b/docs/markdown/backend/overview.md index ca7de86..35714cc 100644 --- a/docs/markdown/backend/overview.md +++ b/docs/markdown/backend/overview.md @@ -1,6 +1,7 @@ # 💽 Backends Backends are the outputs of the backup process. Each location needs at least one. + Note: names of backends MUST be lower case! ```yaml | .autorestic.yml From b4cc0f0ab1dc5d106f4cce80275286f8e1f3307e Mon Sep 17 00:00:00 2001 From: ninjabenji <76439609+ninjabenji@users.noreply.github.com> Date: Thu, 7 Apr 2022 10:32:17 +0100 Subject: [PATCH 3/3] Add warning about location names. Location names need to be lower case in order to work properly. --- docs/markdown/location/overview.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/markdown/location/overview.md b/docs/markdown/location/overview.md index 1b3dd96..ccde261 100644 --- a/docs/markdown/location/overview.md +++ b/docs/markdown/location/overview.md @@ -3,6 +3,7 @@ Locations can be seen as the input to the backup process. Generally this is simply a folder. The paths can be relative from the config file. A location can have multiple backends, so that the data is secured across multiple servers. +Note: names of locations MUST be lower case! ```yaml | .autorestic.yml version: 2