mirror of
https://github.com/hanzoai/chat.git
synced 2026-09-30 20:51:17 +00:00
zeekayandHanzo Dev
5960df513a
266 files of upstream residue, none of it reachable from anything that builds
or runs. chat is a Node application that reaches models through api.hanzo.ai;
what came out is a Python proxy's build system, test suite and CI:
docker/ every image in it CMDs `litellm`, one is FROM ghcr.io/berriai/litellm
— the upstream vendor's own image — and Dockerfile.dev is
python:3.11-slim + pip install litellm[proxy]
tests/ 231 files, 181 of them .py, including an enterprise/ tree; wired to
no suite in this repo
ci_cd/ Prisma migration scripts for schema.prisma, which declares
LiteLLM_BudgetTable and friends while no package.json anywhere
depends on prisma
deploy/ the migrations those scripts generate
config.yaml, the proxy's model_list; compose.dev.yml, whose `command: npm run
dev` was aimed at that Python image and could never have run; docker-compose.yml,
a near-identical twin of compose.yml; .pre-commit-config.yaml, whose hooks
filter on litellm/, litellm_proxy_extras/ and enterprise/.
The Makefile is the part that was actively wrong rather than merely dead:
`build-prod` ran `docker build -f docker/Dockerfile -t hanzoai/chat:latest`,
which builds the LiteLLM image and tags it as chat. `dev` and `dev-full` drove
compose.dev.yml and a with-router profile pointing at hanzoai/llm:latest. dev
now runs the two watch commands this repo actually has, build-prod builds
Dockerfile.multi — the image deploy.yml ships — and dev-full and logs-router are
gone with the router they logged.
Verified before cutting: nothing under Dockerfile.multi, Dockerfile.static,
compose.yml, hanzo.yml, package.json or .hanzo/workflows/ reaches any deleted
path. The `docker/` hits in deploy.yml are docker/setup-buildx-action, an action
namespace. `.do/gitnexus` copies its own entrypoint.sh, not the one in docker/.
Co-authored-by: Hanzo Dev <[email protected]>