docs(config): state data directory behavior positively

Documentation should describe what the software does, not enumerate
what it does not do. Rephrase the data-directory wording around the
positive facts (each directory is independent; a new root starts with
empty state) and drop the "never moves or copies" constructions from
config.md, the config.html env table, and the changeset.
This commit is contained in:
Federico Jaramillo Martinez
2026-07-28 19:43:22 +02:00
parent 5c3461d508
commit 5b717ed542
3 changed files with 3 additions and 3 deletions
@@ -2,6 +2,6 @@
"@jmfederico/pi-web": patch
---
Remove the legacy session archive migration from session daemon startup. Setting `PI_WEB_DATA_DIR` only selects where PI WEB-managed state lives; it never moves or copies existing state, and each data directory is independent.
Remove the legacy session archive migration from session daemon startup. Each `PI_WEB_DATA_DIR` data directory is independent: pointing PI WEB at a new data directory starts there with empty registries and no session archives.
You are only affected if you have session archives created before July 2026 in the default `~/.pi-web` data directory and you newly set a custom `PI_WEB_DATA_DIR`. To carry those archives over, stop PI WEB, then copy `archived-sessions.json` and the `archived-sessions/` directory from the old data directory into the new one.