mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-08 04:32:42 +00:00
Marc-André Bombeck
9d18b8fd25
The badge read the enabled flag plus a DSN that parses. Neither says anything about the target accepting a report: a wrong public key, a wrong project id and a host that stopped answering all parse, and every one of them showed green with a line naming the host. That is the false reassurance an operator finds out about when they go looking for a crash that was never reported. Nothing in the tree recorded an outcome, so there was nothing to read. The sender now stamps one next to the DSN it used — instant on a success, a short classification on a failure. Never the response body: that is text from a remote host and has no business in this database or on this page. The badge is green only while a report has left inside the last fortnight, amber while a target is set and nothing has come back, and it names the reason underneath. The clock lives with the ledger, so the verdict is resolved in the route and the card paints what it is handed. A failure that a later success superseded is not shown at all. Pressing Test records like any other send, so the button proves the target on demand.
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).