prisma-compute

Deploy and manage TypeScript applications on Prisma Compute using the Prisma Platform CLI.

Updated Aug 20, 2026
One-click install
npx skills add https://github.com/rhorba/RestoLedger --skill prisma-compute-rhorba
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prisma-compute
Source: https://github.com/rhorba/RestoLedger/tree/main/api/.windsurf/skills/prisma-compute
Command: npx skills add https://github.com/rhorba/RestoLedger --skill prisma-compute-rhorba

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Deploying TypeScript apps to Prisma Compute involves many failure points: wrong CLI package, missing auth workspace selection, loopback-only host binding, port mismatches, and misconfigured prisma.compute.ts files. This Skill guides agents through the correct deploy, config, and troubleshooting workflow so apps actually become reachable on their public URL. ## Core Features & Use Cases - Deployment workflows: Deploy existing apps with @prisma/cli app deploy, scaffold new apps with create-prisma --deploy, and manage deployments, logs, domains, and promotions. - Typed Compute config: Create and validate prisma.compute.ts with defineComputeConfig for single apps, monorepos, and multi-app targets. - Framework readiness: Verify deploy requirements for Next.js, Nuxt, Astro, Hono, NestJS, TanStack Start, Bun, Elysia, and custom prebuilt artifacts, including 0.0.0.0 host binding and port alignment. - Use Case: A user merges a Hono API and asks to deploy it. The Skill checks auth workspaces, confirms the entrypoint and port 8080, runs app deploy --json --no-interactive, and verifies the public deployment URL with curl. ## Quick Start Ask the agent to deploy your existing app to Prisma Compute, for example: deploy this Hono API to Prisma Compute and verify the public URL.

Frequently Asked Questions about prisma-compute

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy an existing app to Prisma Compute?

Use the Prisma Platform CLI with bunx @prisma/cli@latest app deploy, passing flags like --framework, --entry, --http-port, and --env. If the project has a generated compute:deploy script or prisma.compute.ts config, prefer those over reconstructing flags manually.

Which frameworks can deploy to Prisma Compute?

The deploy command supports nextjs, nuxt, astro, hono, nestjs, tanstack-start, custom, and bun framework keys. Elysia and plain servers deploy through the bun key with an explicit entrypoint, while SvelteKit needs a Node adapter artifact deployed as custom.

Why is my Prisma Compute deployment unreachable after a successful deploy?

The most common cause is binding the server to localhost or 127.0.0.1 instead of 0.0.0.0, since Compute readiness only checks that the port is listening. Also confirm the app listens on the deployed HTTP port, typically via process.env.PORT or a matching --http-port flag.

Does prisma.compute.ts replace deploy flags?

No, prisma.compute.ts stores reusable app defaults like framework, entry, httpPort, root, and env files, but explicit flags such as --framework, --region, and --env override config values. It never selects workspace, project, branch, or production intent.

How do I authenticate Prisma Compute deploys in CI?

Set a non-empty PRISMA_SERVICE_TOKEN environment variable, which takes precedence over stored OAuth workspaces, and run deploys with --json --no-interactive. Never print the token value, and unset it if you need to switch local OAuth workspaces.

Does deploying to Prisma Compute run database migrations?

No, deploys never run migrations, seed data, or schema push. Create databases with database create, manage env vars with project env commands, and run your project's own Prisma migration scripts separately after setup.