Files

T

Gan, Jimmy 76c10a6c07 fix: use compose-compatible env_file format

Switch env_file declarations back to string list syntax so Synology's docker compose parser accepts the LiteLLM and cc-connect compose files.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

2026-03-02 01:11:58 +08:00

config.example.toml

feat: add LiteLLM gateway scaffold and dashboard health probe

2026-03-02 01:08:12 +08:00

docker-compose.yml

fix: use compose-compatible env_file format

2026-03-02 01:11:58 +08:00

README.md

feat: add LiteLLM gateway scaffold and dashboard health probe

2026-03-02 01:08:12 +08:00

README.md

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)

Copy template and fill secrets locally:
- cp cc-connect/config.example.toml cc-connect/config.toml
- create cc-connect/.env with platform token(s)
Keep secrets local only (.env is gitignored).
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.