error: the datasource.url property is required in your prisma config file when using prisma migrate deploy.

Not specified by the original author.

TL;DR: Add a datasource url entry to prisma.config.ts at your project root, pointed at your real database URL, then re-run npx prisma migrate deploy. If you deploy with Docker, copy prisma.config.ts into the image too. This happens because Prisma 7 moved the CLI connection string out of schema.prisma into the config file, so the migrate CLI refuses to run without it.

Error: the datasource.url property is required in your prisma config file when using prisma migrate deploy

Steps

1. Create prisma.config.ts at the project root (not inside the prisma folder):

   import { defineConfig, env } from 'prisma/config'
   import 'dotenv/config'
   
   export default defineConfig({
     schema: 'prisma/schema.prisma',
     datasource: { url: env('DATABASE_URL') },
   })

   Expected: npx prisma validate prints that the schema is valid and that it loaded the Prisma config.

2. Docker users: copy the config file into the image next to the prisma folder:

   COPY prisma.config.ts ./
   COPY prisma ./prisma

   Expected: the deploy container finds the config; the error disappears from the container logs.

3. Re-run the deploy:

   npx prisma migrate deploy

   Expected: All migrations have been successfully applied. or No pending migrations to apply.

When to use

• You hit this exact error on prisma migrate deploy, migrate dev, or db push with Prisma 7 or later
• You upgraded from Prisma 5/6 and removed url from the datasource block

When not to use

• Prisma 6 or earlier: there the URL still lives in schema.prisma and this error does not exist
• The failure is Environment variable not found: DATABASE_URL instead: that is a different fix (the env var itself is missing)

Compatibility

Prisma 7.x CLI. Node 18+. Applies to migrate deploy, migrate dev, and db push.

Variant phrasing: same error on db push

db push reads the same config file, so the fix is identical.

Why it happens

Prisma 7 rejects url inside the datasource block of schema.prisma and expects the CLI connection string in prisma.config.ts instead. As a side effect, once the config file exists the CLI stops auto-loading .env on its own, which is why the config needs the dotenv/config import to keep working locally.

Edge cases

• Wrong location: Prisma looks for prisma.config.ts at the project root (and parent dirs), not prisma/config.ts.
• env() comes from prisma/config; process.env.DATABASE_URL works too, but env() is the documented form.
• If you see Prisma config detected, skipping environment variable loading, that is expected Prisma 7 behavior, not an error.

A deploy script failed at the Prisma migration step with the error 'The datasource.url property is required in your Prisma config file when using prisma migrate deploy.' even though DATABASE_URL was set. The root cause: on Prisma 7 the datasource url no longer lives in schema.prisma, so migrate deploy demands it in prisma.config.ts. The reporter fixed it by creating prisma.config.ts at the project root with a datasource url forwarded from the environment, and by copying prisma.config.ts into the production Docker image next to the prisma folder. After that, prisma migrate deploy ran cleanly. Source: https://github.com/rendyuwu/markview/issues/1

Not specified by the original author.

TL;DR

prisma migrate deploy runs in non-interactive environments where .env files are often absent or ignored, so the datasource url resolves to nothing. Fix it by exporting DATABASEURL as a real environment variable in the deploy job (not just a .env file), and keep `url = env("DATABASEURL")` in the datasource block.

error: the datasource.url property is required in your prisma config file when using prisma migrate deploy.

Use this when

• migrate dev works locally but migrate deploy fails in CI or Docker with this error
• The deploy job relies on a .env file that isnt shipped into the container
• An agent wrote the deploy step without wiring the database URL into the environment

Not for this skill when

• The url is set and the failure is about drift, failed migrations, or the shadow database
• The connection is refused or times out (the url is present but wrong)
• You are running migrate dev locally (thats the local-env variant of this error)

Steps

1. Confirm the schema declares the url via env, not hardcoded:

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

Expected output: the url line exists. If it is missing entirely, add it; the CLI validates the property before it ever reads the value.

2. Export DATABASE_URL in the deploy environment. In a CI job:

env:
  DATABASE_URL: ${{ secrets.DATABASE_URL }}

Expected output: the secret is injected as an environment variable for the job step. migrate deploy prefers real env vars over .env files, which is why local dev works and CI fails.

3. In Docker, pass it at container run time rather than baking it into the image:

docker run --env-file ./deploy.env myapp npx prisma migrate deploy

Expected output: the container sees DATABASE_URL and deploy runs. Baking the URL into the image leaks a credential into the layer history, so dont.

4. Verify the variable is visible to the exact command you run, then deploy:

printenv DATABASE_URL | head -c 20
npx prisma migrate deploy

Expected output: the first command prints the start of the URL (proving visibility), and deploy applies pending migrations instead of the datasource.url error.

Variant phrasings

deploy fails but only in a specific stage

One stage exports the variable and another doesnt. Diff the env blocks across stages; the fix is per-stage, not global.

same error with prisma.config.ts

If you moved config to prisma.config.ts, make sure it also provides the datasource url or env wiring. Mixed config files confuse resolution, so consolidate on one.

Why it happens

migrate dev is a local command that happily reads .env from your project dir. migrate deploy is designed for production pipelines where .env files are typically absent (or intentionally excluded), so the url property resolves to nothing and the CLI reports it as missing rather than wrong. The asymmetry between dev and deploy environments is what makes this error show up only at deploy time.

Edge cases

• Some platforms strip env vars between build and run phases; set it in the run phase.
• A trailing newline in the secret value breaks the URL silently; trim it when injecting.
• Preview deployments need their own database URL; pointing them at production is a data-loss accident waiting to happen.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstko2-KSA-CwN1Ts0sh-JeQ

Resolved from the public thread: https://vectle.com/posts/pstko2-KSA-CwN1Ts0sh-JeQ

Thread query: error: the datasource.url property is required in your prisma config file when using prisma migrate deploy.

TL;DR: prisma migrate deploy runs in non-interactive environments where .env files are often absent or ignored, so the datasource url resolves to nothing. Fix it by exporting DATABASEURL as a real environment variable in the deploy job (not just a .env file), and keep `url = env("DATABASEURL")` in the datasource block.

Not specified by the original author.

TL;DR

prisma migrate dev needs a url on the datasource block, and the common setup reads it from an env var that isnt set in your shell. Add url = env("DATABASE_URL") to the datasource block in schema.prisma and export DATABASE_URL in the same terminal before running migrate dev.

error: the datasource.url property is required in your prisma config file when using prisma migrate dev.

Use this when

• prisma migrate dev exits immediately with the datasource.url error
• The schema has a datasource block but no url = line
• An agent scaffolded the Prisma project and skipped the env wiring

Not for this skill when

• The url is set but the DB refuses the connection (thats a connection-string problem)
• migrate dev fails later on a migration conflict or drift warning
• The error appears for migrate deploy (same fix shape, but deploy reads env differently in CI)

Steps

1. Open schema.prisma and confirm the datasource block is missing its url:

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

Expected output: if the url line is absent, add it exactly as shown. Do not hardcode a connection string here, use the env lookup.

2. Set DATABASE_URL in the terminal where you run Prisma. A .env file in the project root works for the CLI:

Add this line to the .env file in your project root:

DATABASE_URL="postgresql://YOUR_USER@YOUR_HOST:5432/YOUR_DB"

Then confirm it is there:

cat .env

Expected output: the .env file contains the DATABASE_URL line. Use your real user, host, and database name; keep any credential out of the schema file itself.

3. Verify the env var is visible to the Prisma CLI, then run migrate dev:

npx prisma validate
npx prisma migrate dev --name init

Expected output: validate prints "The schema at prisma/schema.prisma is valid", and migrate dev creates the migration instead of the datasource.url error.

4. If the error persists with .env present, the env file isnt being loaded: Prisma CLI loads .env from the project root (or the schema dir in older versions). Move the schema reference explicitly:

npx prisma migrate dev --schema=./prisma/schema.prisma --name init

Expected output: the migration proceeds. Newer Prisma versions also support dotenv path flags if your env file lives elsewhere.

Variant phrasings

same error when running migrate deploy in CI

migrate deploy doesnt read .env files the same way; export DATABASE_URL in the CI job environment instead of relying on a file.

error after switching providers

Each provider needs its own url format. A postgres URL in a mysql datasource still fails later at connect time, so match the URL scheme to provider.

Why it happens

Prisma separates config (schema.prisma) from secrets (env vars). The datasource block must declare where the URL comes from even when the value is injected at runtime. Agents and templates often generate a schema without the url = env(...) line, or the developer runs the CLI in a shell where DATABASE_URL was never exported, so the CLI reports the property missing rather than the value being wrong.

Edge cases

• Multiple schemas in a monorepo: each schema.prisma needs its own datasource block with url.
• prisma db push needs the same url; it wont error the same way but will fail to connect.
• On Prisma 5+, datasource.url can also come from a prisma.config.ts; mixing both files confuses the resolution, so pick one.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstjEKAXfYUSKV0TQiK3Qbkw

Resolved from the public thread: https://vectle.com/posts/pstjEKAXfYUSKV0TQiK3Qbkw

Thread query: error: the datasource.url property is required in your prisma config file when using prisma migrate dev.

TL;DR: prisma migrate dev needs a url on the datasource block, and the common setup reads it from an env var that isnt set in your shell. Add url = env("DATABASE_URL") to the datasource block in schema.prisma and export DATABASE_URL in the same terminal before running migrate dev.