-
Notifications
You must be signed in to change notification settings - Fork 0
CLI
Jobin Lawrance edited this page Jul 2, 2026
·
1 revision
One binary, tinyraven, serves both the HTTP server and the command line.
| Command | What it does |
|---|---|
tinyraven serve |
run the HTTP server |
tinyraven deploy |
validate + apply .datasource/.pipe files to ClickHouse (--check dry-run, --branch) |
tinyraven local start |
bring up the dev stack (ClickHouse + Redis + TinyRaven) via Docker Compose |
tinyraven local stop |
tear it down |
tinyraven token create / ls / rm |
manage scoped bearer tokens |
tinyraven login |
save API host + token to ~/.tinyraven/config.yml
|
tinyraven status |
show resolved config + server reachability |
tinyraven completion |
shell completion (bash/zsh/fish) |
No Docker daemon running? tinyraven local start finds one instead of hanging: live daemon → colima → Docker Desktop → offer to brew install colima. Add -y to auto-confirm the install (CI). Run it from the repo root (it needs docker-compose.yml).
Scopes: ADMIN, APPEND:<datasource>, READ:<pipe>. Create one, then point clients at it:
tinyraven token create --scope ADMIN
tinyraven login --host http://localhost:8000 --token <tok>TinyRaven is git-first: edit files, tinyraven deploy. Tinybird's tb is imperative (push/pull/append). So there's no pull (git is truth), and datasource ls / pipe ls / sql live on the API rather than as CLI verbs. Full map: migrate-from-tinybird.