mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-08 12:32:43 +00:00
Marc-André Bombeck
5e253313fc
Index a document for content search automatically the moment it is stored, instead of requiring a manual index action. A fire-and-forget per-document job runs an AI-first decision tree: when a vision-capable provider is configured and consented, transcribe the stored original (rich, handles scanned PDFs and images), budget-reserved exactly like the interactive index route; otherwise fall back to server-side text-layer extraction via pdf-parse (no provider, no egress, milliseconds) so content search works at a baseline even with no AI. Budget exhaustion, a provider that cannot read the file (a text-layer PDF on a non-Anthropic account), and provider errors all fall through to the free local path rather than leave a document unsearchable. Both paths write the same blind, encrypted content index (AES-256-GCM text + opaque HMAC token tags) — nothing readable at rest. The local path adds the 'local-pdf' / 'local-ocr' source values (free String column, no migration). Server-side OCR for scanned images and scanned PDFs is left as a documented seam. Pin pdf-parse + pdfjs-dist into the standalone trace so the wasm text extractor ships in the runtime image.
prisma/
The database layer. HealthLog runs PostgreSQL 16 via Prisma 7. This directory holds the single schema file and the forward-only migration history; the generated client is emitted elsewhere.
Contents
schema.prisma— 61 models, one file.cuid()primary keys,snake_casecolumns via@map(...), encrypted columns mostly suffixed*Encrypted(search the file; there are 24 encrypted column references). Thegenerator clientblock emits to../src/generated/prisma(imported as@/generated/prisma).migrations/— numbered, forward-only SQL migrations (0001_…upward).migration_lock.tomlpins the provider topostgresql.
Migration workflow
# author a migration from a schema edit
pnpm dlx prisma migrate dev --name <short_snake_case_name>
# regenerate the client after any schema change
pnpm dlx prisma generate
Number a new migration with the next free prefix. The production entrypoint runs prisma migrate deploy on boot, so every migration must apply cleanly forward — there is no down-migration path. Always include the migration file in the same change as the schema edit.
Conventions
- Encryption is fail-closed:
*Encryptedcolumns are written through@/lib/crypto(AES-256-GCM, versioned key ids); never store plaintext in an encrypted column. Key rotation isscripts/rotate-encryption-key.ts+docs/ops/encryption-key-rotation.md. - The generated client under
src/generated/prismais build output — do not edit it. - Schema-touching changes that affect the API surface must regenerate
docs/api/openapi.yaml(see../CLAUDE.md).
Related: ../src/lib/README.md (db.ts, rollups/), ../docs/ops/ (migrations + backup runbooks).