db-packageLayout and boundaries of the packages/db workspace package in Nuvraxis monorepos — the only package that imports drizzle-orm or pg; what it exports (db, inferred types, query functions, valibot schemas) and never exports (the pool, tables, drizzle-kit); query functions in src/queries taking an Execu
drizzleWork across the Drizzle ecosystem — drizzle-orm schema and query code, drizzle-kit migrations, and related tooling. Load before reading or editing any Drizzle file (anything importing `drizzle-orm/*`), defining or editing `drizzle.config.ts`, generating migrations, applying schema changes to a datab
drizzle-postgresDrizzle ORM v1 (1.0.0-rc.5) rules for PostgreSQL 17 in Nuvraxis apps — schema files with snakeCase.table, uuid ids, timestamptz columns, pgEnum vs text, indexes and foreign keys, relations v2 with defineRelations, relational queries with object filters vs the select builder, transactions and savepoi
postgres-opsOperating PostgreSQL for Nuvraxis apps — local Postgres 17 with Docker Compose (pinned by digest, loopback only, named volume, healthcheck), .env.example with DATABASE_URL only, an external production database the chart never deploys, DATABASE_URL from an existing Kubernetes Secret, migrations as an
scaffold-fullstackAdds the PostgreSQL data layer (Drizzle ORM v1 in packages/db, local Postgres, the migrate Job, CI) to a repo created by nuvraxis-frontend's scaffold, from this plugin's tested templates, then proves it with migrations, tests, a build, a Docker image and the Helm chart.