Admin deployment boundaries
Solid relationships are source/configuration verified. The dashed edge is a supported possibility, not an inspected live target. Admin always builds node-server into .output/admin and is not deployed as the SAM Lambda. Host Nuxt dev exists for layer work with supplied configuration; Docker is the documented operational path. Compose waits for PostgreSQL health and DynamoDB/MinIO initialization. HTTP /admin healthchecks do not establish successful CRUD. Public web APIs still use admin-token gates independently of UI separation.
flowchart TB
Browser["Browser: default loopback port 4400"]
Build["Host build and docker-admin preparation"]
Out["Admin build and environment public outputs"]
subgraph Docker["Standalone admin Compose"]
Admin["Nitro node-server admin"]
SQL["SQLite on data mount"]
PG["PostgreSQL 16 and volume"]
DY["DynamoDB Local and volume"]
MI["MinIO configured bucket"]
DAM["Separate admin-media SQLite and blobs"]
end
Mount["Read-only output mount"]
Remote["Optional MEDIA_API_URL target"]
AWS["Separate public web AWS media endpoints"]
Browser -->|HTTP UI and APIs| Admin
Build -->|stage| Out
Out -->|Dockerfile copies admin output| Admin
Out -->|public files mounted| Mount
Admin -->|blog/messages| SQL
Admin -->|blog/messages| PG
Admin -->|blog/messages| DY
Admin -->|CDN operations| MI
Admin -->|read sync files| Mount
Admin -->|local DAM| DAM
Admin -->|configured forwarding| Remote
Remote -.->|possible target, not verified configuration| AWS
Source evidence
- core/admin/nuxt.config.ts:183 — preset: ‘node-server’
- docker/docker-compose.admin.yml:43 — depends_on:
- docker/Dockerfile.admin:31 — COPY –chown=node:node .output/admin
- scripts/docker-admin.mjs:16 — ensureAdminNitroOutput
- core/admin/server/utils/media-service.ts:42 — function mediaApiUrl
- core/web/nuxt.config.ts:42 — const adminToken
- infra/sam/template.yaml:305 — MediaWorkerFunction: