From ba165797799be062e697e2d5d72fd417791a4ff1 Mon Sep 17 00:00:00 2001 From: "Danilo M." Date: Wed, 8 Jul 2026 16:50:27 +0200 Subject: Document ~/bin deploy step for the wrapper Co-Authored-By: Claude Opus 4.8 --- CLAUDE.md | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) (limited to 'CLAUDE.md') diff --git a/CLAUDE.md b/CLAUDE.md index d1d4970..1356340 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -23,8 +23,18 @@ cp .env.example .env # set real IMGGEN_OUT / IMGGEN_CACHE / IMG ``` The wrapper lives in the repo and `cd`s to `$IMGGEN_DIR` (default `$HOME/Programming/GIT/imggen`) -so it can find `compose.yaml` and `.env`. It is not copied to `~/bin`; symlink it onto PATH if -convenient, it still operates on the repo via `IMGGEN_DIR`. +so it can find `compose.yaml` and `.env` no matter where it is invoked from. + +**Deploy after finishing work.** All wrapper edits happen on the repo copy `./imggen`. Once a +change is done, tested, and committed, deploy it to PATH so the user gets it globally: + +``` +cp ./imggen ~/bin/imggen && chmod +x ~/bin/imggen # ~/bin is on the user's PATH +``` + +`~/bin/imggen` is a plain copy, not a symlink, so it must be re-copied after every wrapper change. +It still operates on the repo via `IMGGEN_DIR`. Only the wrapper is deployed this way; the other +source files run inside the container. Do this as the last step, not mid-work. `test_generate.py` covers pure logic (model registry, resolve_model) with no GPU needed. Beyond that, no lint config; verification is running `imggen` end to end and checking the PNG. -- cgit v1.2.3