v3.3.0: keep client.db in the XDG data dir, add -d/--data-dir

2 files changed, 11 insertions, 5 deletions

diff --git a/docs/SERVER_SETUP.md b/docs/SERVER_SETUP.md
index 9eac7a7..700a12e 100644
--- a/docs/SERVER_SETUP.md
+++ b/docs/SERVER_SETUP.md
@@ -79,7 +79,9 @@ last address for that key is forgotten.
 
 The server creates `server.db` in the current directory on first use. It holds
 users, balances, and the per-game `plays` audit. The client keeps its own
-`client.db` for host fingerprints and stored credentials. There are no schema
+`client.db` for host fingerprints and stored credentials in
+`$XDG_DATA_HOME/zagan-bet/` (usually `~/.local/share/zagan-bet/`); pass
+`-d <dir>` to keep it somewhere else. There are no schema
 migrations while the app is in alpha: a schema change means deleting both files.
 
 During development, delete both files to reset users, balances, history, and
diff --git a/docs/TESTING.md b/docs/TESTING.md
index ac07a3f..1a1d369 100644
--- a/docs/TESTING.md
+++ b/docs/TESTING.md
@@ -52,12 +52,16 @@ on a machine where the `openssl` CLI is available.
 
 ## Development resets
 
-The server creates `server.db` in its working directory; the client creates
-`client.db` for host trust and stored credentials. While the software is in
-testing, delete both after a schema or trust change:
+The server creates `server.db` in its working directory. The client keeps
+`client.db` (host trust, stored credentials) in the XDG data directory:
+`$XDG_DATA_HOME/zagan-bet/client.db`, usually
+`~/.local/share/zagan-bet/client.db`. Override it with `client -d <dir>`.
+
+While the software is in testing, delete both after a schema or trust change:
 
 ```sh
-rm -f server.db client.db
+rm -f server.db
+rm -rf ~/.local/share/zagan-bet
 ```
 
 The audit schema is not auto-migrated from the pre-2.0 slots-only `plays`