From 9d85aba8719a37f6806e6875b740ff6999acd206 Mon Sep 17 00:00:00 2001 From: Alexander Date: Mon, 1 Apr 2024 19:35:16 +0300 Subject: [PATCH] Update prisma.mdx --- docs/pages/repo/docs/handbook/tools/prisma.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/repo/docs/handbook/tools/prisma.mdx b/docs/pages/repo/docs/handbook/tools/prisma.mdx index 5aa611d776e25..1f66d4981c5c9 100644 --- a/docs/pages/repo/docs/handbook/tools/prisma.mdx +++ b/docs/pages/repo/docs/handbook/tools/prisma.mdx @@ -207,6 +207,6 @@ However, Prisma behaves differently with different package managers. This can le You may wish to experiment with this yourself. If you find a solution that you feel works, feel free to [add an issue](https://github.com/vercel/turbo/issues/new/choose) and we can update this section. -8. Going to production +### 8. Going to production Now that you've made it this far, you're ready to deploy your application. Depending on where your database lives, you'll want to design your deployment pipeline according to the documentation for your database's setup. There are many factors to take into consideration from this point on, so we can't provide a one-size-fits-all solution. You likely want to visit the documentation for your database and its deployment platform to learn more.