Skip to content

Fix typo in environment variables reference #7193

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Fix typo in environment variables reference #7193

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
be7859c
Fix typo in environment variables reference
B1F030 Oct 16, 2025
e98c99f
remove duplicate can be
B1F030 Oct 21, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions content/200-orm/500-reference/300-environment-variables-reference.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -167,7 +167,7 @@ This environment variable is available since version `4.16.0`

</Admonition>

`PRISMA_ENGINES_CHECKSUM_IGNORE_MISSING` can be can be set to a truthy value to ignore problems around downloading & verifying the integrity (via a checksum file) of the Prisma ORM engines.
`PRISMA_ENGINES_CHECKSUM_IGNORE_MISSING` can be set to a truthy value to ignore problems around downloading & verifying the integrity (via a checksum file) of the Prisma ORM engines.
This is particularly useful when deploying to an offline system environment where the checksum file cannot be downloaded.

```env
Expand All @@ -192,7 +192,7 @@ PRISMA_QUERY_ENGINE_BINARY=custom/query-engine-<target>
For Prisma CLI it allows you to define the query engine file to be used.
For Prisma Client, on build time (during `prisma generate`), it defines where the query engine file will be copied from into Prisma Client. At run time (when using the generated Client) it can be used to define the specific query engine file to be used instead of the included one.

Note: This can only have an effect if the engine type of CLI or Client are set to `binary`. If the engine type is `library` (the default), use PRISMA_QUERY_ENGINE_LIBARY instead.
Note: This can only have an effect if the engine type of CLI or Client are set to `binary`. If the engine type is `library` (the default), use PRISMA_QUERY_ENGINE_LIBRARY instead.

#### `PRISMA_QUERY_ENGINE_LIBRARY`

Expand Down