Sulkta-OSS/skald
3
0
Fork 0
Code Issues 1 Pull requests 5 Projects Releases Packages Wiki Activity Actions

Public-flip audit: env-driven paths, scrub audit-ticket prefixes, terser README

Browse source 
the host bind paths + LAN host pins replaced with env defaults. Repository URLs
→ git.sulkta.com. Audit-changelog scaffolding stripped from inline comments
(technical reasoning preserved). README sheds marketing scaffolding. AI-speak
in load-bearing prompts/SOULs left alone — that IS the product.
This commit is contained in:
Sulkta 2026-05-27 11:42:58 -07:00
parent 566ca05ea8
commit 564233cbff
20 changed files with 233 additions and 258 deletions
Download patch file Download diff file Expand all files Collapse all files

19
engines/README.md
View file

@ -40,19 +40,18 @@ generalise. Examples:
all three at once), preset choice ergonomics, character→tortoise-
voice seed assignments.
When deploying an engine to the host, the build dir at
`/srv/appdata/<engine>/build/` tracks the engine's branch:
To deploy a tuned engine, check out the engine's branch in the build
dir and `docker compose up -d --build`:
```bash
cd /srv/appdata/kokoro/build
git fetch && git checkout engine/kokoro
docker compose -p <name> up -d --build
docker compose up -d --build
```
## GPU coordination (2070 Super)
## GPU coordination
The 8GB card is the bottleneck. F5 + Kokoro can co-reside (~5GB +
~1GB). Tortoise pushes the budget over and needs the GPU largely
to itself — the `engine/tortoise` branch will carry the script
that stops kokoro + f5 before a tortoise run and restarts them
after. Replace with proper coordination once we have more VRAM.
On an 8GB card F5 + Kokoro can co-reside (~5GB + ~1GB). Tortoise
pushes the budget over and needs the GPU largely to itself — the
`engine/tortoise` branch carries a script to stop kokoro + f5
before a Tortoise run and restart them after. Replace with proper
coordination once more VRAM is available.