mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-08 12:32:43 +00:00
Marc-André Bombeck
1ea14e9100
While two pdf.js versions broke each other, a local text read after a page render failed and was recorded as decrypt-error, and a scanned PDF that had to be rasterized for the provider was recorded as raster-failed. Neither has a content index, and on an instance without an AI provider nothing offers to index it again. Migration 0479 clears the attempt time of exactly those PDFs and keeps their reason, a state no index attempt leaves behind. A new boot discovery, document-index-retry, enqueues the upload's auto-index job for each such row, so it runs the same provider-first, local-fallback decision under the same consent rules; a deferred import stays local because its row says so. The attempt writes its time back, so every document drops out after one try, and one that really cannot be read records its reason again and stays settled. An account with the documents module off keeps its marks until the module is on. An integration test seeds both kinds of damage, runs each migration's statement and only what a boot runs on its own, and sees a preview and an index appear, while a blank page, a broken ciphertext and a file that is not a PDF settle after one retry and are not found by the next boot. Refs #1277
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).