haylanandClaude-Bot
b0e37b2f4c
One script to bring the running stack in sync after any change: git pull, validate compose config, rebuild the litellm-pgvector local build, re-pull images, recreate what changed. Documented in README's quickstart, and CLAUDE.md now tells agents to run it after touching compose/config/scripts rather than just describing a change as done. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
14 lines
826 B
Markdown
14 lines
826 B
Markdown
## Agent skills
|
|
|
|
### Issue tracker
|
|
|
|
Issues live as Gitea issues on `git.arthurerlich.de` (repo `haylan/LLM-Server`); use the `tea` CLI (already authenticated) for all operations. See `docs/agents/issue-tracker.md`.
|
|
|
|
### Domain docs
|
|
|
|
Single-context: `CONTEXT.md` + `docs/adr/` at the repo root. See `docs/agents/domain.md`.
|
|
|
|
### Deploying changes
|
|
|
|
The running stack lives on a separate box (the R9700 server), not wherever this repo is being edited. After **any** change to `docker-compose.yml`, `litellm-config.yaml`, `.env.example`, or a script under `scripts/`, commit/push it, then run `./scripts/update.sh` on the server to apply it — don't just describe the change as done. If this session doesn't have shell access to the server, say so explicitly and tell the user to run it themselves rather than leaving it unsaid.
|