Author the docker-compose service for the chosen proxy #14
Notifications
Due Date
No due date set.
Blocks
Depends on
#10 Which self-hosted AI gateway/proxy tool fits this effort's needs?
haylan/LLM-Server
#11 Reference cloud model/pricing for the shadow-cost estimate
haylan/LLM-Server
#12 How should per-workload API keys/accounts be provisioned, rotated, and documented?
haylan/LLM-Server
#13 Network/hostname plan for exposing the proxy (LAN + external)
haylan/LLM-Server
Reference: haylan/LLM-Server#14
Reference in New Issue
Block a user
Part of #9
Question
Add the proxy tool chosen in #10 to docker-compose.yml (new service + .env.example entries), wired in front of llama.cpp per the network plan from #13, with the key-provisioning workflow from #12 and the shadow-cost config from #11 in place. Document it (README.md / a new docs page), following the pattern of map #1's #4 and #6.
Resolved: authored the docker-compose service.
Added
litellm+litellm-db(Postgres) services to docker-compose.yml, a newlitellm-config.yamlwiring the local llama.cpp model with #11's shadow-cost pricing (Claude Sonnet 5 rate,model_info.input_cost_per_token/output_cost_per_token) and a priority-scheduling stub per #16, and requiredLITELLM_MASTER_KEY/LITELLM_SALT_KEY/LITELLM_DB_PASSWORDenv vars in .env.example. Documented in README.md.Untested on real hardware — split out as issue #17, which also carries #16's required priority-scheduler smoke test. Open WebUI/coding CLIs still hit llama.cpp directly — that migration is #15, unblocked by this.
Committed on main.