923ab1cf58
Replaces v1 plan with locked architecture: - Hermes orchestrator: POST /ingest → Gemini Vision → MongoDB → event detection → Gemini Live 2.5 voice via LiveKit Agents - Four MongoDB collections: engineer_states, ownership_map, events, nudges - Continual learning via ownership_map persisting across sessions New files: docs/idea.md, docs/gemini.md, docs/livekit.md, docs/mongodb.md, docs/digitalocean.md, docs/demo-setup.md Updated: README.md, docs/PLAN.md (12-hour build plan), database/README.md, infra/README.md, .env.example Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FFbfi4Cmb7BY75Wtne7bZn
920 B
920 B
infra
Deploy targets for PodMan on DigitalOcean.
Dockerfile— builds the Hermes backend from the monorepo rootapp.yaml— DigitalOcean App Platform spec (Hermes web service + frontend static site)
Full deploy spec and env var reference in docs/digitalocean.md.
Local development
pnpm --filter backend dev # Hermes on :8787
pnpm --filter frontend dev # PWA on :5173
Local container
docker build -f infra/Dockerfile -t podman-hermes .
docker run --env-file .env -p 8787:8787 podman-hermes
DigitalOcean deploy
doctl apps create --spec infra/app.yaml
Set secret env vars (LiveKit, Gemini, MongoDB) in the DO dashboard after app creation.
Fallback (demo safety)
If DO deploy is flaky on stage, run Hermes locally. The PWA defaults to http://localhost:8787 via VITE_BACKEND_URL fallback — no code change needed.