Skip to content

chore: update env var references #4502

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

Merged
ruheni merged 1 commit into from
Feb 8, 2023
Merged

chore: update env var references #4502

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
8 changes: 7 additions & 1 deletion content/400-reference/200-api-reference/300-environment-variables-reference.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -186,7 +186,11 @@ PRISMA_MIGRATION_ENGINE_BINARY=custom/my-migration-engine-unix
PRISMA_INTROSPECTION_ENGINE_BINARY=custom/my-introspection-engine-unix
```

### CLI Binary Targets
<Admonition type="warning">

- The Introspection Engine is served by the Migration Engine from [4.9.0](https://github.com/prisma/prisma/releases/tag/4.9.0). Therefore, the `PRISMA_INTROSPECTION_ENGINE` environment variable will not be used.

</Admonition>

#### <inlinecode>PRISMA_FMT_BINARY</inlinecode>

Expand All @@ -202,6 +206,8 @@ The `PRISMA_FMT_BINARY` variable is used in versions [4.2.0](https://github.com/

</Admonition>

### CLI Binary Targets

#### <inlinecode>PRISMA_CLI_BINARY_TARGETS</inlinecode>

`PRISMA_CLI_BINARY_TARGETS` can be used to specify one or more binary targets that Prisma CLI will download during installation (so it must be provided during `npm install` of Prisma CLI and does not affect runtime of Prisma CLI or Prisma Client).
Expand Down