From 8ed2082854debd1c9d8b942abf139a77d5a5a8e1 Mon Sep 17 00:00:00 2001 From: Krzysztof kuhy Rudnicki Date: Mon, 22 Jun 2026 12:54:10 +0200 Subject: [PATCH] Document the durable-clone editable-install requirement A one-off `pip install "diet_guard @ git+..."` from a scratch directory was used during the original cutover; that's a non-editable snapshot that a later git push silently never reaches. Document the correct deployment convention (install.sh from a durable ~/diet-guard clone) so this doesn't drift again. --- CLAUDE.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/CLAUDE.md b/CLAUDE.md index b5aad1c..d668551 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -48,6 +48,16 @@ added but only `pip install`-ed into `.venv`. Always verify against `/usr/bin/python3 -c "import "`, not just the dev venv, before considering a dependency change done. +**Always run `install.sh` (or `pip install -e`) from a durable clone, not a +scratch directory.** `install.sh` does `pip install -e "$REPO_DIR"` — +editable, so a later `git pull` in that same clone updates the running +production code with no reinstall needed. The clone must live somewhere +permanent (this repo's convention: `~/diet-guard`, mirroring `~/screen-locker` +for the screen-locker package) — if you `pip install -e` from `/tmp/...` or +run `pip install "diet_guard @ git+https://..."` as a one-off, you get a +non-editable snapshot frozen at that commit, and the next `git push` here +silently does **not** reach the running service. + ## Operational gotchas - **The budget file is sealed immutable.** `~/.local/share/diet_guard/.budget`