From c1ea5c799068f852a010d5bfde7bfdc2576a9cf5 Mon Sep 17 00:00:00 2001 From: peter Date: Wed, 2 Sep 2026 12:59:14 +0100 Subject: [PATCH] Note the permanent test/testpwd fixture user for LLM API testing AGENT_DAYBOOK__LLM_TEST (a sibling project) always uses this account to test the API. Documenting it here so a future reset of the local dev database gets it recreated instead of silently breaking that project. Co-Authored-By: Claude Sonnet 5 --- CLAUDE.md | 1 + 1 file changed, 1 insertion(+) diff --git a/CLAUDE.md b/CLAUDE.md index 4c73bda..0203418 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -44,6 +44,7 @@ The core product principle is: agents publish content, not files. The server own - Run the local development server on `127.0.0.1:8001`. Port `8000` may be reserved or blocked on this workstation. - Always use this same fixed port for the dev server. Never start a second instance on a different port; if `8001` is already serving, reuse it rather than starting another. - All artifact-posting tools (`skills/daybook-posting/scripts/daybook_post.py`, `scripts/seed_demo_artifacts.py`, and any future posting skill) must default `DAYBOOK_URL` to `http://127.0.0.1:8001` to match. +- A regular (non-superuser) user `test` / password `testpwd` must always exist in the local dev database — it's the permanent account a sibling project (`AGENT_DAYBOOK__LLM_TEST`) uses for API testing. If the local `db.sqlite3` is ever reset, recreate this exact user (e.g. via Settings → Users) before assuming that project is broken. - Do not deploy to the Proxmox NUC during routine code iteration. - Treat the NUC container as the local live/staging target. Deploy there only at explicit stable checkpoints, such as an end-of-day build. - Before any NUC deployment, preserve `/opt/daybook/deploy/.env` and `/opt/daybook/deploy/data`.