Codex BaaS scaffolding
Codex is the API and metadata SSOT on Turso. Large blobs (exports, weights, attachments) use an object storage trait (S3/R2-compatible), not a second relational engine.
Components (target)
- Codex API — Query/mutation routes, auth/tenant boundary, schema digest sync.
- Reactive layer —
codex_change_log+ subscriptions (SSE/WebSocket); included in baseline DDL (manifest fragmentv8). - Skills registry — Backed by
skill_manifests+ CAS objects. - Workflow runtime API — Journal from
execution_log/ future dedicated workflow tables. - Object storage adapter — Metadata in Turso; bytes in R2/S3.
Deployment
- Compose hub (profiles, CI, Docker vs Podman): Deployment compose SSOT.
- Coolify / compose:
infra/coolify/docker-compose.yml— template; setVOX_DB_URL,VOX_DB_TOKEN,VOX_DB_PATH(or embedded replica trio) per ADR 004. - Static frontends: GitHub Pages or CDN; point to hosted Codex API.
Environment (canonical)
| Variable | Role |
|---|---|
VOX_DB_URL | Turso / libSQL remote URL |
VOX_DB_TOKEN | Auth token (env only) |
VOX_DB_PATH | Local file or replica local path |
Optional object storage: R2_ACCOUNT_ID, R2_ACCESS_KEY_ID, R2_SECRET_ACCESS_KEY, R2_BUCKET_NAME, R2_PUBLIC_URL (documented when adapter lands).
HTTP contract
- OpenAPI:
contracts/codex-api.openapi.yaml - Human reference: Codex HTTP API
Related
- Environment variables (SSOT) — full
VOX_*/ Turso precedence - Codex vNext schema
- Roadmap tasks:
.cursor/plans/vox_context_baas_deployment_roadmap.md(internal backlog)