Files
narl-workspace/migrations/0004_backup_layout.sql
T
nvrlandClaude Opus 5 7646ecc397 fix: keep the mirror out of the device root
Proton refuses a file directly in a device's root folder — 422 "Cannot
create file at the root of a device" — so the first real backup died on
RESTORE.txt, before it had written anything. The mirror now lives in a
`data/` folder on the device, which is both what Proton permits and the
honest name for what it holds: the contents of DIARY_DATA_DIR.

Every remote path changed with it, so the bookkeeping describing the old
layout is dropped and rebuilt on the next run. A device root that
already collected an empty `uploads/` folder from the failed attempt
keeps it; it is not ours to guess about, and deleting it is one click.

Also quiet rPGP's packet-header warnings by default. They fire on every
key Proton wrote slightly differently to how rPGP re-serialises it —
cosmetic, once per unlock, and loud enough to bury the backup's own log.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01D5Gk8FPkRXu1e6Nj2BCRE1
2026-09-05 13:39:41 +02:00

9 lines
425 B
SQL

-- A device's root folder rejects files: Proton answers 422 "Cannot create file
-- at the root of a device". Everything therefore moved one level down, into a
-- `data/` folder, which changed every remote path. The bookkeeping describes a
-- layout that no longer exists, so it is dropped and the mirror rebuilds itself
-- on the next run — an upload again, not a loss.
DELETE FROM backup_files;
DELETE FROM backup_state;