build(confidence-engine): add production container packaging
This commit is contained in:
@@ -1,5 +1,19 @@
|
||||
# Current Project State — Confidence Engine
|
||||
|
||||
## v0.62d Production Docker Packaging
|
||||
|
||||
- `Dockerfile` created: multi-stage Alpine build (Node 22), Next.js standalone output, configurable port 3000, health-check boundary via `/api/health`
|
||||
- `.dockerignore` created: excludes `node_modules`, `.next`, secrets (`env.*.local`), docs, IDE, OS artefacts
|
||||
- `next.config.mjs`: added `output: 'standalone'` for lean production container (only config change required)
|
||||
- `.env.example`: reorganized; Ollama variables now tracked as deployment-relevant env vars
|
||||
- npm production build: PASS ✓
|
||||
- Docker image build: blocked — no Docker runtime on development machine (apparatus limitation, not product defect)
|
||||
- Production container start / `/api/health` smoke test: pending Docker availability
|
||||
- No persistent application volume required
|
||||
- Supabase remains external; Ollama remains private and server-reachable
|
||||
- Public `NEXT_PUBLIC_*` variables may require build-time injection via `--build-arg` (baked into browser bundle)
|
||||
- **No deployment performed**
|
||||
|
||||
> Created by Experiment 27. This document is the starting point for any fresh session working on the Confidence Engine. Read this first, then follow the routing table below to task-specific references.
|
||||
|
||||
## 1. What the Confidence Engine Is
|
||||
|
||||
Reference in New Issue
Block a user