Developer guide
For engineers extending Appbricx, self-hosting, or calling the app runtime from generated apps.
Monorepo map
| Path | Role |
|---|---|
apps/web | Next.js marketing, dashboard, editor |
services/api | Hono API, app-runtime, v10 app generation, deploy |
packages/appkit | @app/kit: block layer + runtime kits generated apps are built on |
deployment/docker | Compose, Caddyfile, production rollout |
docs/ | Architecture markdown (repo). Product docs live at /docs |
Local / Docker
See repo docs/QUICKSTART.md and docs/ARCHITECTURE.md. Typical path: ./deployment/docker/setup.sh → site on localhost via Caddy.
Runtime paths in generated apps
- Data:
/__appbricx/data/* - Queries:
POST /__appbricx/queries/:name - REST:
/__appbricx/api/v1/:table - Topics SSE:
/__appbricx/topics/:name/subscribe - Webhooks:
POST /hooks/:projectId/:name - AI proxy:
/__appbricx/ai/*
Runtime source
Server implementation: services/api/src/app-runtime/. Spec notes: docs/FULLSTACK_RUNTIME.md.
CI/CD
Push to main runs CI then CD: bake images to GHCR, SCP compose + Caddyfile, run server-rollout.sh (force-recreates Caddy so config reloads).
Production secrets
Checklist: docs/PRODUCTION_SECRETS.md. Never commit .env with live keys.