Configurable binary asset download (source) location

This feature request originated here https://github.com/prisma/prisma2/issues/916

and is not covered via https://github.com/prisma/prisma2/issues/506

Prisma CLI, tries to download binaries from Prisma’s S3 bucket. In some environments, this download fails.

This requires spec work but a potential solution can be to have a configurable CDN URL via an env var like PRISMA_CDN_URL.

The responsibility of maintaining a mirror would be on the users.

An alternative is to link binaries to a release: https://github.com/prisma/prisma2/releases

[game7]

I’ve also been having proxy/firewall issues but after digging around the code I’ve discovered that the binary asset locations are already configurable via environment variables. In my case I’m able to wget the binaries down to my container via our corporate proxy and simply point to them locally using these environment variables:

const binaryToEnvVar = {
  'migration-engine': 'PRISMA_MIGRATION_ENGINE_BINARY',
  'query-engine': 'PRISMA_QUERY_ENGINE_BINARY',
  'introspection-engine': 'PRISMA_INTROSPECTION_ENGINE_BINARY',
}

[timsuchanek]

Support for the env var PRISMA_BINARIES_MIRROR is now implemented. A valid example URL is: https://binaries.prisma.sh

You can try it out in the latest alpha: @prisma/cli@alpha & @prisma/client@alpha