3 Commits

Author SHA1 Message Date
86d399a04b fix: use npm i instead of npm ci in Docker build, expose on port 5656
- Dockerfile: drop package-lock.json copy, use npm i instead of npm ci
  so install works even if lock file is slightly out of sync
- docker-compose: map host port 5656 → container port 3000
2026-04-13 00:43:19 -04:00
ca583ea6c9 fix: Dockerfile uses npm prune instead of npm ci for production deps
The run stage no longer runs npm ci --omit=dev (which fails when
package-lock.json and the Docker environment's resolved deps are
out of sync, e.g. @emnapi/* transitive deps from adapter-node).

Instead, the build stage runs npm prune --omit=dev after building,
and the run stage copies the already-pruned node_modules. This
avoids any lock file sync issues across different environments.
2026-04-13 00:36:12 -04:00
792fafc661 feat: containerize with Docker Compose + Ollama
Add full Docker setup so the app runs with a single 'docker compose up':

- Dockerfile: multi-stage build (node:22-alpine) for the SvelteKit app
- docker-compose.yml: three services:
  1. ollama: runs Ollama server with persistent volume for models
  2. model-init: one-shot container that pulls the configured model
     after Ollama is healthy, then exits
  3. app: the SvelteKit app, starts only after model-init succeeds
- .env.docker: set OLLAMA_MODEL to control which model is pulled
- .dockerignore: keeps image lean
- Switched adapter-auto to adapter-node (required for Docker/Node hosting)
- Updated README with Docker and local dev instructions

Usage:
  docker compose up              # default: llama3
  OLLAMA_MODEL=gemma2 docker compose up  # any Ollama model
2026-04-13 00:22:19 -04:00