@digo-labs/backend

The one Hono backend shared by every digo app — deployed as a container on ECS behind api.digo-labs.com.

Layout

• src/routes/ — one Hono route chain per domain (bedrock, database, storage, dmx, proxy, auth, admin), all mounted at /.
• src/services/ — the Services aggregate: one services-<domain>.ts instance class per domain, reached as Services.database.getAll(...).
• src/middleware/ — CORS, app inference, auth session loading.
• src/db/ — Postgres pool, drizzle client, and the schema registry.

Patterns are documented in the design system: Backend Patterns and Backend Architecture.

Develop locally

npm run dev   # tsx watch on port 3000

Requires env vars (DATABASE_URL_MONOREPO at minimum; FAL_KEY for the fal proxy) — the usual workflow is developing apps against the deployed backend instead, which needs nothing locally. See Environment and Local Backend.

Build

npm run build   # tsup → dist/index.cjs + dist/index.d.cts

The published @digo-labs/backend package ships types only (dist/index.d.cts) — packages/services imports the router types from it for its typed client. After changing any exported router type, rebuild and republish or dependent packages resolve stale types.

Deploy

From the repo root:

npm run deploy:backend

Docker build → ECR push → ECS rollout. Details, task-definition/secrets model, and verification steps: Deploying to AWS.