Merge feat/install-4-backup into feat/install-5-native

docs/content/Deploying/Docker-Deploying.mdx

@@ -89,6 +89,12 @@ docsgpt backup                      # into <stack>/backups
 docsgpt backup --out /mnt/backups   # somewhere else, e.g. a mounted disk
 ```
 
+While the archive is made, the backend and the worker stop and start again, so
+the database dump and the files in the volumes describe the same moment; Postgres
+itself keeps running. On a small install that pause is seconds, but count on it
+if you run `docsgpt backup` from cron. The archive is written readable only by
+the user who took it.
+
 The archive does **not** include `.env`, because that file holds the install's
 secrets. `docsgpt backup --with-settings` puts it in, for when the archive
 itself is stored somewhere private. Keep `.env` safe separately otherwise: the

docs/content/changelog.mdx

@@ -26,7 +26,8 @@ the same way they do on a Docker one, and never touch the database or Redis. See
 `docsgpt backup` writes a dump of the database and a tar of each data volume into one archive, and
 `docsgpt restore <archive>` puts them back. The settings file is left out unless
 `--with-settings` asks for it, since it holds the install's secrets, and a backup from a newer
-DocsGPT is refused unless you pass `--force`. See
+DocsGPT is refused unless you pass `--force`. The archive is written readable only by its owner,
+and the backend and the worker pause while it is made so the dump and the volume tars match. See
 [Backups](/Deploying/Docker-Deploying#backups).
 
 ## 0.21.0