mirror of
https://github.com/kuhyx/wake-alarm.git
synced 2026-07-04 13:23:01 +02:00
Document the durable-clone editable-install requirement
A one-off `pip install "wake_alarm @ 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 ~/wake-alarm clone) so this doesn't drift again.
This commit is contained in:
parent
407d7cbf8f
commit
9e46bcd2a2
10
CLAUDE.md
10
CLAUDE.md
@ -70,6 +70,16 @@ site-packages:
|
|||||||
/usr/bin/python3 -m pip install --user --break-system-packages -e .
|
/usr/bin/python3 -m pip install --user --break-system-packages -e .
|
||||||
```
|
```
|
||||||
|
|
||||||
|
**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: `~/wake-alarm`, mirroring `~/screen-locker`
|
||||||
|
for the screen-locker package) — if you `pip install -e` from `/tmp/...` or
|
||||||
|
run `pip install "wake_alarm @ 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.
|
||||||
|
|
||||||
`install.sh` already does this. **If you add a dependency and only install it
|
`install.sh` already does this. **If you add a dependency and only install it
|
||||||
into a dev venv, the production service will silently fail with
|
into a dev venv, the production service will silently fail with
|
||||||
`ModuleNotFoundError` on its next run** — this exact gap caused a 3-day
|
`ModuleNotFoundError` on its next run** — this exact gap caused a 3-day
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user