docs(frank-tts): what makes a locally built voice image stale, and what the warm text must survive
Three pages, all from faults found this session: - `LLM/deployment.md` gains "Locally built images": which images have no registry digest, what the `cfhash` skip is for, why it must cover every COPY'd file (the silent shape: build skipped, /health green, old code serving), and the base-image half of the law — the engine's `useradd`, because the pinned ubuntu:24.04 has no `adduser`. - `Dankclaw/Frank TTS Engine.md` troubleshooting gains the two lines an operator actually needs: every voice cold on a fresh boot with a hand-run hook succeeding (= `WARM_TEXT` arrived quoted, `podman exec … env | grep WARM_TEXT` proves it), and a 502 from the façade beside a 200 `/health` from the engine (model loaded ≠ voices registered). The stale-warmer row is re-keyed to the new rebuild rule. - `Dankclaw/Voice Packs.md` step 4 was wrong: it told the next agent to restart the engine *instead of* the warm hook because the hook "only registers packs it has not seen". It registers every pack on every run and the engine replaces a name it already holds — `tools/tts-server.cpp:148` at the pinned commit: "Re-registering a name replaces the previous entry." A restart is what an engine bump needs (the registry is memory-only), never worse, only slower. - `Dankclaw/Frank TTS.md` deploy command re-keyed to `./scripts/deploy.sh dankclaw --service frank-tts`, the way it is actually deployed; the raw `deploy-remote.sh` form is plumbing.
This commit is contained in:
1 parent
59e021da2c
commit
7178e1c789
4 files changed
+44
-8
No files matched your search
@@ -115,7 +115,7 @@ shows up as a failed synthesis, never as a down probe.
|
||||
|
||||
## Deploying it
|
||||
|
||||
`scripts/deploy-remote.sh dankclaw frank-tts` (or `frank-tts-engine frank-tts`):
|
||||
`./scripts/deploy.sh dankclaw --service frank-tts` (or `--service frank-tts-engine --service frank-tts` for the pair):
|
||||
builds the façade image, installs **both** Quadlet units — including the
|
||||
engine's `.network` file, because a referenced `Network=` file the generator
|
||||
cannot find means the façade unit is not produced at all — creates
|
||||
|
||||
Reference in new issue
Block a user