From 4e5028f4d735ed8f4fafeab9cb4931b6055deff1 Mon Sep 17 00:00:00 2001 From: gabe Date: Sun, 2 Aug 2026 15:12:42 -0400 Subject: [PATCH] Use expected komodo database name in example restore compose --- docsite/docs/setup/backup.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docsite/docs/setup/backup.md b/docsite/docs/setup/backup.md index 4c110b90fe..08279c4294 100644 --- a/docsite/docs/setup/backup.md +++ b/docsite/docs/setup/backup.md @@ -102,7 +102,7 @@ services: KOMODO_CLI_DATABASE_TARGET_ADDRESS: komodo.example.com:27017 KOMODO_CLI_DATABASE_TARGET_USERNAME: KOMODO_CLI_DATABASE_TARGET_PASSWORD: - KOMODO_CLI_DATABASE_TARGET_DB_NAME: komodo-restore + KOMODO_CLI_DATABASE_TARGET_DB_NAME: komodo ``` :::warning @@ -123,4 +123,4 @@ While it should be rare that this causes any kind of issue when it comes to rest Komodo undergoes a lot of usage at all hours and you are worried about consistency, you could consider [locking](https://www.mongodb.com/docs/manual/reference/method/db.fsyncLock/#mongodb-method-db.fsyncLock) Mongo before the backup. Just make sure to [unlock](https://www.mongodb.com/docs/manual/reference/method/db.fsyncUnlock/) -the database afterwards. \ No newline at end of file +the database afterwards.