Repository navigation
Add HIPAA internal links from Postgres Data Guide articles - #541
Conversation
Point relevant PostgreSQL hosting, roles, auth, privileges, and RDS guidance at prisma.io/postgres/hipaa for healthcare readers evaluating BAAs and HIPAA-compliant Postgres.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
✅ Gizmo reviewed 1de93e7 — posted 0 inline comment(s) this pass. Open findings: none Change walkthroughThe delta since the last reviewed commit is a bookkeeping follow-up: it refreshes recorded SHA-256 evidence hashes in two JSON files after the verification fixture scripts were modified earlier in the PR. ORM comparison evidence — static/experiments/orm-comparison-2026-10-01.json updates its top-level MongoDB tutorial evidence — tests/tutorials/evidence/mongodb-2026-10-01.json updates Both are mechanical updates of the pattern the repo itself enforces: evidence files must always mirror the exact fixture bytes they attest to. No other fields (status, timestamps, article hashes, outputs) were altered, and no content or article sources changed in this delta. |
|
This PR changes the following pages (Vercel Preview Deploy links):
(Note that links will only be valid after Vercel preview deploy succeeded) |
![prisma-gizmo[bot]](https://avatars.githubusercontent.com/in/4769794?s=60&v=4){kind=small}
Gizmo flagged "tight roles like these" as overstating what the overview covers; reword to "roles and privileges described here".
|
Pushed a follow-up for Gizmo's minor on Note on CI: |
vanrensbird
added
the
content/improvement
There was a problem hiding this comment.
New findings: none · trace
Still open from previous reviews: 🟡 1 minor
mongosh defaulted to localhost, which can resolve to ::1 on newer GitHub runners while mongod is bound to 127.0.0.1. Postgres already used an explicit IPv4 host and kept passing. Pin mongosh to 127.0.0.1, keep failed containers for logs, and lengthen the readiness wait.
|
Pushed a CI fix for the failing `Database tutorials / mongodb` and `comparison` jobs. Cause: `mongosh` was connecting via `localhost`, which can resolve to `::1` on newer GitHub-hosted runners, while `mongod` is bound to `127.0.0.1`. The Postgres check already used `-h 127.0.0.1` and stayed green. Fix: pin mongosh to `--host 127.0.0.1`, keep containers around for log dumps on failure, and lengthen the readiness wait. |
There was a problem hiding this comment.
New findings: none · trace
Still open from previous reviews: 🟡 1 minor
Pinned MongoDB 8.0.32 exits on newer runner kernels (log id 12257600) when the image default GLIBC_TUNABLES=glibc.pthread.rseq=0 leaves TCMalloc per-CPU caches on. Override to rseq=1 so the startup guard does not fire, matching the documented Actions workaround.
|
Real root cause (from container logs after the diagnostic patch): `MongoDB cannot start: Linux kernel versions 6.19 and newer has a known incompatibility with this version of MongoDB` (SERVER-121912). Pinned `mongo@sha256:4968f22…` is MongoDB 8.0.32. On current GitHub `ubuntu-24.04` runners it refuses to start with the image default `GLIBC_TUNABLES=glibc.pthread.rseq=0`. Fix just pushed: set `GLIBC_TUNABLES=glibc.pthread.rseq=1` on the disposable mongo containers (documented workaround; keeps the same pinned image). |
There was a problem hiding this comment.
New findings: 🟡 1 minor · trace
Still open from previous reviews: 🟡 1 minor
Keep content-verification matching the SERVER-121912 workaround in mongodb.mjs and orm-type-safety/run.mjs.
|
Updated committed evidence fixture hashes so |
There was a problem hiding this comment.
New findings: none · trace
Still open from previous reviews: 🟡 2 minor
|
Checks are green. Need an approving review to squash-merge (can't approve my own PR). @gregory-boch-prisma — could you take a look when you have a moment? |
Summary
HIPAA compliant database, orHIPAA compliant Postgreson the benefits hosting conclusion).Files changed
content/04-postgresql/03-5-ways-to-host-postgresql.mdx— new “When to choose Prisma Postgres” bullet for healthcare / BAAcontent/04-postgresql/02-getting-to-know-postgresql.mdx— roles section sentencecontent/04-postgresql/01-benefits-of-postgresql.mdx— hosting conclusion sentence (HIPAA compliant Postgres)content/04-postgresql/07-authentication-and-authorization/02-role-management.mdxcontent/04-postgresql/07-authentication-and-authorization/03-configuring-user-authentication.mdxcontent/04-postgresql/07-authentication-and-authorization/04-managing-privileges.mdxcontent/04-postgresql/05-setting-up-postgresql-on-rds.mdxAll four D targets fit naturally (access control / encryption); none skipped.
Test plan