Deploys service definition changes. Every time you're making a local change to any file in the service configuration (including the data model), you need to synchronize these changes with the remote service using this command.
Upon the very first deploy of a service, the command will perform initial data seeding if the
seed property in
prisma.yml is provided. You can prevent this by passing the
endpoint property is specifed in
prisma.yml, the command will prompt you to interactively select a Prisma server as a deployment target. After you selected the server, it will write it to
prisma.yml as the default deployment target for future deploys. To bring up the interactive prompt again, simply remove the
endpoint property from
prisma deploy [flags]
-d, --dry-run Perform a dry-run of the deployment -e, --env-file ENV-FILE Path to .env file to inject env vars -f, --force Accept data loss caused by schema changes -j, --json JSON Output -w, --watch Watch for changes --no-seed Disable seed on initial service deploy
prisma deploy --interactive
prisma deploy --env-file .env.prod
Was this page helpful?