mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-15 23:12:04 +00:00
docs(backup): say what account copies and the JSON import can do
Several surfaces promised more than the per-account copies deliver: - The full-backup export card said it had the same shape as the weekly copy. It is a portable export with documents as metadata only; it now says so, and that it cannot recreate an account on another server. - The export page offered to "import from a backup". The JSON import adds measurements and mood entries; it is now named that way, and its help states the 16 MB and 10,000-entries-per-list limits from the constants the route enforces. - The weekly copy is labelled an account rollback on this server, and the backups page says a copy cannot rebuild a lost server. The upload says the account must exist here. Two restore refusals pointed to a "disaster-recovery" copy; they now name the copies that exist. - The instance-settings restore option was described as being for rebuilding a host. docs/ops/backup-restore.md is rewritten short and accurate: what each copy is, the deletion grace window, that database dumps keep a deleted account until they age out, how to restore one account, and a link to the disaster-recovery procedure for a lost server.
This commit is contained in:
1 parent
63574b98a6
commit
0c5f29303b
17 files changed
+258
-571
No files matched your search
@@ -64,7 +64,7 @@ describe("RestoreRefusalNotice", () => {
|
||||
const html = render(["documents"]);
|
||||
|
||||
expect(html).toContain("Nothing was changed");
|
||||
expect(html).toContain("disaster-recovery snapshot");
|
||||
expect(html).toContain("account copies or an off-host copy");
|
||||
});
|
||||
|
||||
it("renders nothing when no section was missing", () => {
|
||||
|
||||
Reference in new issue
Block a user