Name the API credential in the README's Backup (closes #4)
check / check (push) Successful in 1m15s

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
This commit is contained in:
clawbot
2026-09-29 02:42:39 +00:00
parent 1ba65da071
commit b56d8714a7
+7 -5
View File
@@ -273,11 +273,13 @@ container.
## Operating it ## Operating it
**Backup.** Everything durable is the SimpleX database on the volume: **Backup.** Everything durable is on the volume: the SimpleX database,
`simplex_chat.db` and `simplex_agent.db`. Stop the container before `simplex_chat.db` and `simplex_agent.db`, and the API credential,
copying them, since a copy taken from under the running client can be `api-token`. Stop the container before copying the database, since a
inconsistent. The database holds the bot's keys, so a copy lets its copy taken from under the running client can be inconsistent. The
holder answer as the bot; keep it as private as the running instance. 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 **Upgrade.** Rebuild the image and recreate the container with the same
volume. The chat client migrates its database on start. A newer volume. The chat client migrates its database on start. A newer