Skip to content

fixed borgmatic errors when following docs #844

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

fixed borgmatic errors when following docs #844

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions docs/third_party/borgmatic/third_party-borgmatic.de.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -87,9 +87,9 @@ keep_weekly: 4
keep_monthly: 6

mariadb_databases:
- name: ${DBNAME}
username: ${DBUSER}
password: ${DBPASS}
- name: \${DBNAME}
username: \${DBUSER}
password: \${DBPASS}
options: "--default-character-set=utf8mb4 --skip-ssl"
list_options: "--skip-ssl"
restore_options: "--skip-ssl"
Expand Down Expand Up @@ -213,8 +213,8 @@ keine benutzerdefinierten Daten in ihrem maildir oder ihrer mailcow-Datenbank ha
SELinux wird (berechtigterweise) jeden anderen Container, wie z.B. den borgmatic Container, daran hindern, auf
dieses Volume zu schreiben.

Bevor Sie eine Wiederherstellung durchführen, müssen Sie das vmail-Volume in `docker-compose.override.yml` beschreibbar machen, indem Sie
das `ro`-Flag aus dem Volume entfernen.
Bevor Sie eine Wiederherstellung durchführen, müssen Sie die Volumes in `docker-compose.override.yml` beschreibbar machen, indem Sie
das `ro`-Flag der mit `ro` eingebundenen Volumes entfernen.
Dann können Sie den folgenden Befehl verwenden, um das Maildir aus einem Backup wiederherzustellen:

=== "docker compose (Plugin)"
Expand Down
10 changes: 5 additions & 5 deletions docs/third_party/borgmatic/third_party-borgmatic.en.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -88,9 +88,9 @@ keep_weekly: 4
keep_monthly: 6

mariadb_databases:
- name: ${DBNAME}
username: ${DBUSER}
password: ${DBPASS}
- name: \${DBNAME}
username: \${DBUSER}
password: \${DBPASS}
options: "--default-character-set=utf8mb4 --skip-ssl"
list_options: "--skip-ssl"
restore_options: "--skip-ssl"
Expand Down Expand Up @@ -218,8 +218,8 @@ any custom data in your maildir or your mailcow database.
exclusively. SELinux will (rightfully) prevent any other container, such as the borgmatic container, from writing to
this volume.

Before running a restore you must make the vmail volume writeable in `docker-compose.override.yml` by removing
the `ro` flag from the volume.
Before running a restore you must make the read-only volumes writeable in `docker-compose.override.yml` by removing
the `ro` flag from the `ro` mounted volumes.
Then you can use the following command to restore the maildir from a backup:

=== "docker compose (Plugin)"
Expand Down