Gan, Jimmy
ed4090a910
Deploy Dashboard (Dev) / deploy-dev (push) Successful in 2m11s
Introduce a localhost-only LiteLLM service template and expose a protected dashboard health endpoint for operational visibility, while adding cc-connect mobile bridge templates with conservative defaults. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
31 lines
1.1 KiB
Markdown
31 lines
1.1 KiB
Markdown
# cc-connect (Phase 1)
|
|
|
|
Mobile bridge service for interacting with coding agents through chat, with LiteLLM as model gateway.
|
|
|
|
## Scope
|
|
- LiteLLM remains the unified cloud-model endpoint.
|
|
- cc-connect remains the chat/mobile bridge.
|
|
- Start with a single platform (Discord) for lower operational risk.
|
|
|
|
## Files
|
|
- `config.example.toml`: non-secret template.
|
|
- `docker-compose.yml`: optional always-on service shape.
|
|
|
|
## Setup (NAS)
|
|
1. Copy template and fill secrets locally:
|
|
- `cp cc-connect/config.example.toml cc-connect/config.toml`
|
|
- create `cc-connect/.env` with platform token(s)
|
|
2. Keep secrets local only (`.env` is gitignored).
|
|
3. Start service:
|
|
- `docker compose -f cc-connect/docker-compose.yml up -d`
|
|
|
|
## Security defaults
|
|
- Single platform enabled.
|
|
- Confirm/permission-gated command mode.
|
|
- Keep shell/file-write capabilities disabled initially.
|
|
- Restrict users/channels with explicit allowlists.
|
|
|
|
## Notes
|
|
- This repo only includes templates and orchestration shape.
|
|
- Exact runtime keys/fields can vary by cc-connect release; adjust `config.toml` to your installed version.
|