FAQ

Since Prisma 2 is released, will Prisma 1 still be maintained?

FAQ

Prisma 1 (Open Source) will be deprecated on September 1st, 2022. This means that we will archive the Prisma 1 GitHub repo and we will no longer provide fixes for critical bugs, develop new features, or provide support for user issues.

What is the difference between Prisma 1 (Open Source) and Prisma 1 Cloud?

Prisma 1 (Open Source) is the client, CLI, and server.

Prisma 1 Cloud was a service that complemented Prisma 1 (Open Source) by hosting the server and a data browser.

How can I check whether I'm using Prisma 1 Cloud?

  1. Open your project locally.
  2. Inspect prisma.yml and any environment variables your build process is using.
  3. If your project uses a PRISMA_MANAGEMENT_API_SECRET, you are not using Prisma 1 Cloud. You can verify this by using prisma1 logout from the command line, regenerating your Prisma 1 client, and attempting to deploy or access a service.

How can I log into Prisma 1 Cloud and retrieve my information?

  1. Visit app.prisma.io and log in with an email and password or through GitHub.
  2. After logging in, navigate to the Services tab at the top of the screen to access any currently active services, the Servers tab for any custom servers you may have added, and Settings in the top center of the screen to access billing and integration information.

Retrieving data

If you plan to upgrade to Prisma ORM, please email us using the email address on file with a list of the Services in your account that you would like us to export.

If you choose to self-host Prisma 1 (Open Source), use the CLI to export your data.

How can I delete custom servers?

Note: Deleting a server following the steps below will delete the custom server from the Prisma 1 Cloud UI and preserve the deployed service and data.

  1. Visit app.prisma.io and log in with an email and password or through GitHub.
  2. Navigate to the Servers tab at the top of your screen.
  3. Identify the server you wish to delete and click on it. Find the Endpoint property.
  4. Navigate to and log in to the provider hosting your server, such as Heroku, and find the managementApiSecret set as a Config Variable.
  5. Using the value found above, update your application to use a PRISMA_MANAGEMENT_API_SECRET environment variable. Consider using the -e flag or another method for setting environment variables.
  6. After confirming that your application works using the new environment variable, log back into app.prisma.io, the Servers tab, and confirm deletion of the custom server. Note: Deleting a server following these steps will delete the server and service from the Prisma 1 Cloud UI and preserve the deployed services and data.

How can I delete services?

Note: Deleting a service following the steps below will delete the service, data model, and data. To preserve data at a custom service, follow these steps.

  1. Visit app.prisma.io and log in with an email and password or through GitHub.
  2. Navigate to the Services tab at the top of your screen.
  3. Identify the service you wish to delete and click the Gear icon on the right-hand side.
  4. Confirm deletion. Note: Deleting a service following these steps will delete the service, data model, and data. To preserve data at a custom service, follow these steps.

I'm not ready to upgrade to Prisma ORM. Can I self-host?

Yes, you can self-host. However, we recommend upgrading to Prisma ORM as Prisma 1 will be deprecated on September 1st, 2022.

At a high level, these are the steps for migrating to a self-hosted version of Prisma 1 (Open Source):

  1. Log into your Prisma 1 Cloud account and document any running services in the Services tab at the top of the screen.
  2. Deploy a Prisma 1 Server to the hosting environment of your choice. Use the following tutorials as examples:

    1. Deploy to Kubernetes
    2. Deploy to Digital Ocean
    3. Deploy to Digital Ocean with Docker
    4. Deploy to Dokku
  3. Export your service data from Prisma 1 Cloud using prisma1 export.
  4. Update the connection strings in your local prisma.yml file to point to the Prisma 1 Server created in Step 2, and import your service data.
  5. Regression test your application in pre-production environments, then deploy the application with new connection strings to production.
  6. Close your Prisma 1 Cloud account (see below).

How can I close my Prisma 1 account?

  1. Log in to Prisma 1 Cloud.
  2. Verify that there are no production-facing services by visiting the Services tab.
  3. Click on the Account sphere in the upper right-hand corner and click and confirm Delete Account at the bottom of the page.
Content
FAQ