Resultado de búsqueda
The Docker CLI and Docker Compose CLI are used to manage the Prisma servers. Here's a quick rundown of the most important commands: docker-compose up -d: Start a new Prisma server to which you can deploy your Prisma services. docker-compose stop: Stops the Prisma server. docker-compose pull: Downloads the latest Prisma images from Docker Hub.
Running prisma1 generate in the directory where that prisma.yml is located generates a Prisma client in TypeScript and stores the generated files in a directory called prisma-client. The generated Prisma client is configured to target the endpoint specified in prisma.yml. It also knows the secret so that it can authenticate against your Prisma ...
Prisma Cloud is an application (used through a CLI & web interface) that provides tools and services around Prisma. When you're using Prisma, usage of Prisma Cloud is optional. The goal of Prisma Cloud is to ease the workflows in Prisma projects. It features a data browser, a deployment history (soon with automatic rollbacks), various team ...
This is why you have to set the PRISMA_MANAGEMENT_API_SECRET environment variable when using the Prisma CLI. The CLI reads the secret from the PRISMA_MANAGEMENT_API_SECRET environment variable and uses it to generate the JWT which it then attaches to the API request. Depending on your shell, the syntax for setting environment variables might ...
prisma.yml specifies a number of properties about the Prisma service, e.g.: the service's endpoint (includes name and stage of the service) the database type (relational or document database) how and where the Prisma client should be generated. the service secret used to authenticate requests made to the service's API.
Data export with the CLI. The Prisma CLI offers the prisma1 export command. It accepts one option: --export-path (short: -e): A file path to a .zip-directory which will be created by the CLI and where the exported data is stored. Under the hood, the CLI uses the export API that's described in the next section.
The Prisma server is currently unprotected, meaning everyone with access to its endpoint can send arbitrary requests to it. To secure the Prisma server, you need to set the managementApiSecret property in your Docker Compose file when deploying the server.
To bootstrap the configuration files for your Prisma setup, create a new directory and initalize it using the prisma1 init command: mkdir hello-world. cd hello-world. prisma1 init. Copy. After running prisma1 init, the Prisma CLI prompts you to select how you want to deploy Prisma: Select Demo server from the list.
JavaScript. Result. const user = await prisma.user({ email: 'ada@prisma.io' }) Copy. In this case, the returned user record will have four properties (that correspond to the scalar fields of the User model): id, name, email and role. The posts and comments fields are both relation fields and are therefore not included in the response.
For each model type in your datamodel, the Prisma client exposes one function on this property named after the model (but lowercased). Subscribing to this function means you're interested in write -events (i.e. create, update, delete) for that model. You can provide a filter object that lets you further constrain the kind of events you want to ...
