[harsHdokyc]

Closes #17

Summary

Set DATABASE_URL=file:/data/dossier.db to run Dossier on a single SQLite file in one container. PostgreSQL stays the default and is unchanged.

Changes

• Schema: prisma/sqlite/schema.prisma is generated from prisma/schema.prisma (yarn sqlite-schema; a test fails if it's stale), with its own migrations in prisma/sqlite/migrations. prisma7.config.ts picks the schema and migrations by DATABASE_URL.
• Client: src/lib/database.ts → createPrismaClient() picks the Postgres or SQLite client and adapter (@prisma/adapter-better-sqlite3). The app stays typed with the Postgres client.
• Single connection: better-sqlite3 has one connection, so a query from another request ran inside whatever transaction was open and was lost if it rolled back. Such queries now wait for the transaction to end; queries made from inside a transaction's own callback still run at once. A regression test covers this; it fails without the fix.
• Postgres-only features:
  • FOR UPDATE → ${forUpdate()}, which is empty on SQLite.
  • skipDuplicates → upserts with update: {}, or removing duplicates first.
  • SQLite sorts enums alphabetically, so the PDF zip sorts its documents in code.
  • citext → COLLATE NOCASE.
  • The built-in-theme trigger is ported to SQLite.
  • Settings → About shows the SQLite file size.
• Config: DATABASE_URL accepts file: with an absolute path.
• Docker/CI: yarn generate builds both clients. The seed bundle leaves better-sqlite3 external. CI runs the database tests on SQLite too.
• Docs: README (single-container setup), DEVELOPMENT.md (SQLite workflow and caveats), .env.example.

Testing

• yarn lint, yarn typecheck: pass
• yarn test:coverage on PostgreSQL: 1686 passed, 26 skipped (unchanged), thresholds met
• yarn vitest run --project db on SQLite: 436 passed, 1 skipped (a race that SQLite's one-at-a-time transactions rule out)
• yarn build + standalone server on SQLite: migrate, seed (incl. --demo), sign-in, failed-login throttle, main pages, Settings → About
• Not tested: Docker image build (left to CI); e2e still runs on PostgreSQL only

Known limitations

• SQLite allows one writer at a time, which is fine for a single user.
• No automatic migration between databases: export, then import.
• A later schema change needs a migration for both databases (see DEVELOPMENT.md).

AI assistance (Claude Code) was used; I reviewed every change and ran the tests above.

[AienTech]

Hi, thanks for the PR. This one however is already being implemented and quite differs from the current implementation made by Claude.

Thank you anyway for taking the time