You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,8 +33,8 @@ Compatibility-first REST API for Tanzania location data backed by PostgreSQL and
33
33
3. Start PostgreSQL and update your connection strings if needed.
34
34
35
35
- Local and test environments use a direct PostgreSQL `DATABASE_URL`.
36
-
- Production uses a Prisma Accelerate `DATABASE_URL`.
37
-
- If you run `pnpm db:migrate` against an Accelerate-backed environment, also provide `DIRECT_DATABASE_URL` so the migration bootstrap can talk to Postgres directly.
36
+
- Production can use either a direct PostgreSQL `DATABASE_URL` or a Prisma Accelerate `DATABASE_URL`.
37
+
- If `DATABASE_URL` points at Prisma Accelerate, also provide `DIRECT_DATABASE_URL` so migrations can talk to Postgres directly.
38
38
39
39
4. Apply the checked-in schema and seed deterministic fixture data.
40
40
@@ -70,7 +70,8 @@ pnpm openapi:json
70
70
- On a fresh database it bootstraps the historical `init` migration, marks that baseline as applied, and then deploys later migrations
71
71
- On an existing database that already has the older Prisma migration history, it only applies the new additive migrations
72
72
- Prefer `pnpm db:migrate` over calling `prisma migrate deploy` directly
73
-
-`DATABASE_URL` may point at Prisma Accelerate in production, but `pnpm db:migrate` still requires a direct Postgres URL in `DIRECT_DATABASE_URL`
73
+
-`DATABASE_URL` may point at direct Postgres or Prisma Accelerate
74
+
- If `DATABASE_URL` points at Prisma Accelerate, `pnpm db:migrate` still requires a direct Postgres URL in `DIRECT_DATABASE_URL`
0 commit comments