From b56d8714a751c6e28fa5d7c5a17b6cb5c709ded2 Mon Sep 17 00:00:00 2001 From: clawbot Date: Tue, 29 Sep 2026 02:42:39 +0000 Subject: [PATCH] Name the API credential in the README's Backup (closes #4) Getting Started writes the credential to api-token on the volume, so a backup that copies only the SimpleX database leaves it out, and the documented docker run aborts after a restore. The Backup paragraph now names api-token as the other durable file and says it is secret. Model: opus-5-5 --- README.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index e8eac27..b877771 100644 --- a/README.md +++ b/README.md @@ -273,11 +273,13 @@ container. ## Operating it -**Backup.** Everything durable is the SimpleX database on the volume: -`simplex_chat.db` and `simplex_agent.db`. Stop the container before -copying them, since a copy taken from under the running client can be -inconsistent. The database holds the bot's keys, so a copy lets its -holder answer as the bot; keep it as private as the running instance. +**Backup.** Everything durable is on the volume: the SimpleX database, +`simplex_chat.db` and `simplex_agent.db`, and the API credential, +`api-token`. Stop the container before copying the database, since a +copy taken from under the running client can be inconsistent. The +database holds the bot's keys, so a copy lets its holder answer as the +bot, and the credential lets its holder use the API; keep both as +private as the running instance. **Upgrade.** Rebuild the image and recreate the container with the same volume. The chat client migrates its database on start. A newer