Files

T

vh 62672c9850 refactor(dots-tts): extract TTS stack to tts-stack repo; pointer stub + move voices out

TTS development moves to a dedicated repo (~/development/tts-stack) so a separate
agent can own tuning/dev. Mirrors the chatterbox-fast extraction:

- stacks/dots-tts/ reduced to a pointer README (code/Dockerfile/compose/tests/env
  now canonical in tts-stack).
- voices/ canonical corpus moved out to tts-stack/voices/. Blast-radius checked:
  no eshpfi playbook/script reads the corpus (other voices/ refs are unrelated
  host paths under /worktank/...).
- persistent-memory updated: TTS dev extracted + stood down; reverses the earlier
  "corpus home = eshpfi voices/" call.

The ~15 experimental TTS compose wrappers stay here as reference (catalogued in
tts-stack/KNOWLEDGE.md). Live service on irv-ml1:8198 is unaffected (runs from a
copy on the host).

2026-08-11 07:46:11 -07:00

README.md

refactor(dots-tts): extract TTS stack to tts-stack repo; pointer stub + move voices out

2026-08-11 07:46:11 -07:00

README.md

dots-tts — moved to its own repository

The dots.tts serving stack now lives in the dedicated tts-stack repo:

~/development/tts-stack → stacks/dots-tts/ (gitea vh/tts-stack on gitea.phasefinal.com once pushed)

Extracted from this workspace on 2026-08-11 so a dedicated agent can drive all TTS tuning / development. Like chatterbox-fast, dots-tts is authored software with a test suite, so it follows the sister-repo pattern rather than staying a thin compose wrapper here. The new repo owns the code, Dockerfile, tests, the voice corpus (formerly voices/ here), the deploy runbook, and the running TTS knowledge base.

Deployed service

Live on irv-ml1:8198 (local/dots-tts:v3, OpenAI /v1/audio/speech). The host stack dir is /opt/docker/compose/dots-tts/. Deploy + rollback runbook and all engine knowledge live in tts-stack (docs/infrastructure.md, KNOWLEDGE.md).

Voice corpus

The canonical voice corpus (was eshpfi-management/voices/) moved to tts-stack/voices/.

Other TTS engines

The experimental TTS compose wrappers evaluated along the way (cosyvoice, dia, kokoro, vibevoice, zonos, …) remain under stacks/ here as reference; their verdicts are catalogued in tts-stack/KNOWLEDGE.md.