# Fly.io (/docs/guides/postgres/flyio) > For the complete Prisma documentation index, see [llms.txt](https://www.prisma.io/docs/llms.txt). A markdown version of any docs page is available by appending `.md` to its URL. Learn how to deploy applications using Prisma Postgres to Fly.io Location: Guides > Postgres > Fly.io > [!NOTE] > This guide uses Prisma ORM 7 > > The commands and code on this page target Prisma ORM 7, which remains fully supported. To start a new Prisma ORM 8 project, see [Create a new app with PostgreSQL](https://www.prisma.io/docs/prisma-orm/quickstart/postgresql); to add Prisma ORM 8 to an existing app, see [Add Prisma ORM to an existing PostgreSQL database](https://www.prisma.io/docs/prisma-orm/add-to-existing-project/postgresql). A Prisma ORM 8 version of this guide is planned. [Fly.io](https://fly.io/) is a cloud application platform that lets you deploy full-stack applications globally. This guide shows you how to deploy a Node.js application using Prisma Postgres to Fly.io. ## Prerequisites [#prerequisites] - A [Fly.io account](https://fly.io/docs/getting-started/launch/) - The [Fly CLI](https://fly.io/docs/flyctl/install/) installed - An existing application using [Prisma Postgres](https://www.prisma.io/docs/postgres) (see [Quickstart](https://www.prisma.io/docs/v7/prisma-postgres/quickstart/prisma-orm)) ## Deploy your application [#deploy-your-application] ### 1. Generate Prisma Client in `postinstall` [#1-generate-prisma-client-in-postinstall] Ensure your `package.json` includes a `postinstall` script to generate Prisma Client during deployment: ```json title="package.json" { // ... "scripts": { // ... "postinstall": "prisma generate" // [!code ++] } } ``` ### 2. Launch your app with Fly.io [#2-launch-your-app-with-flyio] From your project directory, run: ```bash fly launch ``` Follow the prompts to configure your application. Fly.io will auto-detect your Node.js application and create the necessary configuration. ### 3. Set your database connection string [#3-set-your-database-connection-string] Add your Prisma Postgres `DATABASE_URL` as a secret in Fly.io: ```bash fly secrets set DATABASE_URL="your-prisma-postgres-connection-string" ``` > [!NOTE] > You can find your `DATABASE_URL` in your `.env` file or in the [Prisma Console](https://console.prisma.io/?utm_source=docs\&utm_medium=content\&utm_content=guides). ### 4. Deploy [#4-deploy] If not already deployed during `fly launch`, deploy your application: ```bash fly deploy ``` Once the deployment completes, you'll see a success message with your app's URL: ``` 🎉 SUCCESS! Your app is live and ready to use! 🎉 Visit: https://your-app-name.fly.dev/ ``` > [!NOTE] > In the Fly.io dashboard, your app's status may show as "Pending" initially. It typically transitions to "Deployed" within a few minutes. ## Additional considerations [#additional-considerations] ### Ensure your project uses the correct environment variable [#ensure-your-project-uses-the-correct-environment-variable] Ensure that the data source in your `prisma.config.ts` file is configured to use the `DATABASE_URL` environment variable: ```ts title="prisma.config.ts" import "dotenv/config"; import { defineConfig, env } from "prisma/config"; export default defineConfig({ datasource: { url: env("DATABASE_URL"), }, schema: "prisma/schema.prisma", }); ``` ### Running migrations in production [#running-migrations-in-production] To run migrations on your deployed Fly.io app, you can use: ```bash fly ssh console -C "npx prisma migrate deploy" ``` Or add a release command to your `fly.toml`: ```toml title="fly.toml" [deploy] release_command = "npx prisma migrate deploy" ``` ### Scaling and regions [#scaling-and-regions] Fly.io lets you scale and place your application in [multiple regions](https://fly.io/docs/reference/regions/). To reduce latency, deploy your app in a region close to your Prisma Postgres database region. ```bash fly scale count 2 --region iad ``` ## Troubleshooting [#troubleshooting] ### Prisma schema not found or Client not generated correctly [#prisma-schema-not-found-or-client-not-generated-correctly] If you're using a custom Dockerfile and your build fails because the Prisma Client cannot be found, it's likely due to one of two reasons: 1. **Order of operations**: `npm install` (which runs `postinstall`) runs before the schema is copied. 2. **Incorrect copy path**: The schema is copied to the root instead of the `prisma` folder. **Solution:** In your Dockerfile, copy the `prisma/` directory to `./prisma` **before** running `npm install`: ```dockerfile # ❌ Wrong order or path COPY package*.json ./ COPY prisma . # Copies contents to root (wrong structure) RUN npm install # postinstall runs but might fail or generate in wrong place # ✅ Correct order and path COPY package*.json ./ COPY prisma ./prisma # Copies to ./prisma folder (preserves structure) RUN npm install # postinstall finds schema in expected location COPY . . ``` ## More information [#more-information] - [Fly.io Node.js documentation](https://fly.io/docs/languages-and-frameworks/node/) - [Fly.io Prisma documentation](https://fly.io/docs/js/prisma/) - [Prisma Postgres documentation](https://www.prisma.io/docs/postgres) ## Related pages - [Firebase Studio](https://www.prisma.io/docs/guides/postgres/idx): Learn how to use Prisma Postgres in the online Firebase Studio - [Netlify](https://www.prisma.io/docs/guides/postgres/netlify): Learn how to connect Prisma Postgres to your Netlify sites with the official Netlify extension and deploy your applications with it - [Vercel](https://www.prisma.io/docs/guides/postgres/vercel): Learn how to create Prisma Postgres databases via the Vercel Marketplace and deploy your Next.js, Nuxt, and SvelteKit applications. - [Viewing data](https://www.prisma.io/docs/guides/postgres/viewing-data): Viewing and editing data in Prisma Postgres via Prisma Studio or other database GUIs - [VS Code](https://www.prisma.io/docs/guides/postgres/vscode): The Prisma VS Code extension provides a management UI for Prisma Postgres and agent-mode support for GitHub Copilot