diff options
| -rw-r--r-- | CLAUDE.md | 14 |
1 files changed, 12 insertions, 2 deletions
@@ -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. |
