From a491937f67647cb9c46fa30acea2c377f907012d Mon Sep 17 00:00:00 2001 From: ArthurGamby Date: Wed, 15 Apr 2026 13:14:19 +0300 Subject: [PATCH 01/15] feat(docs): add Prisma Compute EA section Adds a new top-level Compute section under apps/docs covering the EA release: overview, Next.js and Bun quickstarts, dual-CLI reference for @looma/prisma-cli and @prisma/compute-cli (incl. env var management), log streaming with the 10-min / single-stream EA limits, and a consolidated limitations page. Also wires the Compute tab into the v7 top navbar. Co-Authored-By: Claude Opus 4.6 (1M context) --- apps/docs/content/docs/compute/cli.mdx | 167 ++++++++++++++++++ apps/docs/content/docs/compute/index.mdx | 54 ++++++ .../docs/content/docs/compute/limitations.mdx | 42 +++++ apps/docs/content/docs/compute/logs.mdx | 88 +++++++++ apps/docs/content/docs/compute/meta.json | 17 ++ .../content/docs/compute/quickstart-bun.mdx | 95 ++++++++++ .../docs/compute/quickstart-nextjs.mdx | 93 ++++++++++ apps/docs/content/docs/meta.json | 1 + apps/docs/src/lib/layout.shared.tsx | 5 + 9 files changed, 562 insertions(+) create mode 100644 apps/docs/content/docs/compute/cli.mdx create mode 100644 apps/docs/content/docs/compute/index.mdx create mode 100644 apps/docs/content/docs/compute/limitations.mdx create mode 100644 apps/docs/content/docs/compute/logs.mdx create mode 100644 apps/docs/content/docs/compute/meta.json create mode 100644 apps/docs/content/docs/compute/quickstart-bun.mdx create mode 100644 apps/docs/content/docs/compute/quickstart-nextjs.mdx diff --git a/apps/docs/content/docs/compute/cli.mdx b/apps/docs/content/docs/compute/cli.mdx new file mode 100644 index 0000000000..aec441ad34 --- /dev/null +++ b/apps/docs/content/docs/compute/cli.mdx @@ -0,0 +1,167 @@ +--- +title: CLI reference +description: Authenticate, deploy, and manage environment variables for Prisma Compute from the CLI. +badge: early-access +url: /compute/cli +metaTitle: CLI reference | Prisma Compute +metaDescription: Reference for the Prisma Compute CLIs. Authentication, deploy, and environment variable commands for @looma/prisma-cli and @prisma/compute-cli. +--- + +Two CLIs currently target Prisma Compute during Early Access. This page documents the commands needed day-to-day: install, authenticate, deploy, and manage environment variables. + +| Package | Binary | Typical invocation | +|---|---|---| +| [`@looma/prisma-cli`](https://www.npmjs.com/package/@looma/prisma-cli) | `prisma` | `npx @looma/prisma-cli …` | +| [`@prisma/compute-cli`](https://www.npmjs.com/package/@prisma/compute-cli) | `compute` | `bunx @prisma/compute-cli …` | + +## Authentication + +Run an interactive browser flow once per machine. Credentials are stored locally. + +### Using `@looma/prisma-cli` + +```bash +npx @looma/prisma-cli auth login +npx @looma/prisma-cli auth whoami +npx @looma/prisma-cli auth logout +``` + +### Using `@prisma/compute-cli` + +```bash +bunx @prisma/compute-cli login +bunx @prisma/compute-cli logout +``` + +For CI, scripts, and agents, set `PRISMA_API_TOKEN` in the environment instead of running the interactive flow. + +## Deploy + +### Using `@looma/prisma-cli` + +```bash +npx @looma/prisma-cli app deploy [options] +``` + +| Option | Description | +|---|---| +| `--app ` | App name | +| `--entry ` | Entry point path for Bun or auto-detected deploys | +| `--build-type ` | `auto`, `bun`, or `nextjs` (default: `auto`) | +| `--http-port ` | HTTP port the deployed app listens on | +| `--env ` | Environment variable (repeat for multiple) | +| `--json` | Emit structured JSON output | + +### Using `@prisma/compute-cli` + +```bash +bunx @prisma/compute-cli deploy [options] +``` + +| Option | Description | +|---|---| +| `--project ` | Project ID | +| `--service ` | Compute service ID | +| `--service-name ` | Name for a new compute service | +| `--region ` | Region for a new compute service | +| `--path ` | App directory (default: `.`) | +| `--entrypoint ` | File to run at startup (falls back to `package.json` `main`) | +| `--build-type ` | `auto`, `bun`, or `nextjs` (default: `auto`) | +| `--http-port ` | HTTP port the app listens on (default: `8080`) | +| `--env ` | Environment variable (repeat for multiple) | +| `--unset-env ` | Remove an environment variable (repeat for multiple) | +| `--skip-build` | Deploy a pre-built artifact | +| `--skip-promote` | Deploy without promoting to the service endpoint | +| `--destroy-old-version` | Delete the previous version after stopping it | +| `--json` | Output JSON | + +## Environment variables + +You can set environment variables two ways: inline with `deploy`, or with a dedicated update command that creates a new version without rebuilding source. + +### Set variables during a deploy + +Repeat `--env` for each variable. Values are stored on the platform and injected into the running version. + +#### Using `@looma/prisma-cli` + +```bash +npx @looma/prisma-cli app deploy \ + --app my-app \ + --env DATABASE_URL=postgresql://example \ + --env NODE_ENV=production +``` + +#### Using `@prisma/compute-cli` + +```bash +bunx @prisma/compute-cli deploy \ + --env DATABASE_URL=postgresql://example \ + --env NODE_ENV=production +``` + +### Update variables without rebuilding + +Use this when you only need to rotate or add a secret. Both commands cut a **new compute version** — the previous version stays live until the new one is healthy. + +#### Using `@looma/prisma-cli` + +```bash +npx @looma/prisma-cli app update-env --env DATABASE_URL=postgresql://example +npx @looma/prisma-cli app update-env --app my-app --env STRIPE_KEY=sk_live_… +``` + +List the current values: + +```bash +npx @looma/prisma-cli app list-env +npx @looma/prisma-cli app list-env --app my-app +``` + +#### Using `@prisma/compute-cli` + +```bash +bunx @prisma/compute-cli env update --env DATABASE_URL=postgresql://example +bunx @prisma/compute-cli env update \ + --env STRIPE_KEY=sk_live_… \ + --env NODE_ENV=production +``` + +### Remove variables + +Pass `--unset-env KEY` (repeat for multiple) on either `deploy` or `env update` with `@prisma/compute-cli`: + +```bash +bunx @prisma/compute-cli env update --unset-env LEGACY_FLAG --unset-env DEBUG +``` + +## Versions and services + +`@prisma/compute-cli` exposes primitives for managing versions and services directly: + +```bash +bunx @prisma/compute-cli versions list +bunx @prisma/compute-cli versions show +bunx @prisma/compute-cli versions start +bunx @prisma/compute-cli versions stop +bunx @prisma/compute-cli versions promote +bunx @prisma/compute-cli versions delete + +bunx @prisma/compute-cli services list +bunx @prisma/compute-cli projects list +``` + +With `@looma/prisma-cli`, equivalent operations live under `app`: + +```bash +npx @looma/prisma-cli app list-deploys +npx @looma/prisma-cli app show-deploy +npx @looma/prisma-cli app promote +npx @looma/prisma-cli app rollback +npx @looma/prisma-cli app remove +``` + +## See also + +- [Stream logs](/compute/logs) — tail logs for a compute version or deployment. +- [Known limitations](/compute/limitations) — what's still in flight during EA. diff --git a/apps/docs/content/docs/compute/index.mdx b/apps/docs/content/docs/compute/index.mdx new file mode 100644 index 0000000000..fef21b81c7 --- /dev/null +++ b/apps/docs/content/docs/compute/index.mdx @@ -0,0 +1,54 @@ +--- +title: Prisma Compute +description: Deploy Next.js and Bun applications to Prisma Compute from the CLI. +badge: early-access +url: /compute +metaTitle: Prisma Compute +metaDescription: Prisma Compute is a simple, reliable app hosting runtime tightly integrated with Prisma Postgres. Deploy, observe, and manage apps from the terminal. +--- + +Prisma Compute is a simple, reliable app hosting runtime for Next.js and Bun applications, built with tight integration to Prisma Postgres and designed for a CLI-first, AI-native workflow. + +## What you get + +- **One-command deploys** for Next.js and Bun apps. +- **Two CLIs** currently coexist during EA: + - [`@looma/prisma-cli`](https://www.npmjs.com/package/@looma/prisma-cli) — the new unified Prisma CLI (`prisma app …`). + - [`@prisma/compute-cli`](https://www.npmjs.com/package/@prisma/compute-cli) — the original compute CLI (`compute …`). +- **Environment variables** managed from the CLI on every deploy or as a standalone update. +- **Log streaming** for any compute version. +- **Tight Prisma Postgres integration** — build against a managed Postgres without leaving the Prisma toolchain. + +## Getting started + + + + Create a Next.js app and ship it to Compute in a few commands. + + + Deploy a minimal Bun HTTP server to Compute. + + + +## Reference + + + + Install, authenticate, deploy, and manage environment variables from the terminal. + + + Tail logs for a specific compute version or deployment. + + + What is and isn't supported during the EA window. + + + +## Which CLI should I use? + +Both CLIs target the same platform. For EA: + +- Start with **`@looma/prisma-cli`** if you want the unified `prisma app` experience that we are standardizing on for Prisma 8. +- Fall back to **`@prisma/compute-cli`** if you hit an edge case, or for features that have only landed on the original CLI yet. + +Every quickstart and reference page on this site shows the equivalent command in both CLIs side by side. diff --git a/apps/docs/content/docs/compute/limitations.mdx b/apps/docs/content/docs/compute/limitations.mdx new file mode 100644 index 0000000000..d5ae569649 --- /dev/null +++ b/apps/docs/content/docs/compute/limitations.mdx @@ -0,0 +1,42 @@ +--- +title: Known limitations +description: What is and isn't supported in Prisma Compute during Early Access. +badge: early-access +url: /compute/limitations +metaTitle: Known limitations | Prisma Compute +metaDescription: A running list of known limitations in Prisma Compute during the Early Access window. +--- + +Prisma Compute is moving fast during Early Access. This page is the running list of known limitations — keep it close while you're building. + +## Runtime + +- **Next.js apps require `output: "standalone"`.** Set this in `next.config.ts` / `next.config.mjs` before your first deploy. See the [Next.js quickstart](/compute/quickstart-nextjs#2-enable-standalone-output). +- **First-class framework support** for this release covers **Next.js** and **Bun/Hono** only. + +## CLI + +- **Two CLIs coexist.** `@looma/prisma-cli` (unified `prisma app …`) is the direction of travel; `@prisma/compute-cli` (original `compute …`) is the fallback for features or fixes that haven't reached the new CLI yet. +- **First deploy bootstraps local project context** automatically when no project is linked. Subsequent deploys reuse the saved selection, so the scaffolding flags aren't required each time. + +## Log streaming + +- **10-minute stream cap.** A single log stream disconnects after ~10 minutes — reconnect, optionally with `--cursor`, to continue. +- **One concurrent stream per version.** Only one client can stream a given compute version at a time. + +See [Stream logs](/compute/logs) for reconnection patterns. + +## Environment variables + +- `env update` (or `app update-env`) **cuts a new compute version**. The old version stays live until the new one is healthy. +- There is no bulk import from a `.env` file yet — pass `--env KEY=VALUE` for each variable, or repeat the flag. + +## Out of scope for EA + +These are intentionally deferred until after the EA window closes: + +- Canary / traffic-split deploys. +- Multi-region routing controls. +- Console UI parity with the CLI (some actions are CLI-only today — the Console may offer a "copy this command" affordance instead). + +If you hit something that isn't listed here and isn't documented elsewhere, share it in `#product-compute` so we can fold it in. diff --git a/apps/docs/content/docs/compute/logs.mdx b/apps/docs/content/docs/compute/logs.mdx new file mode 100644 index 0000000000..c5c211fc68 --- /dev/null +++ b/apps/docs/content/docs/compute/logs.mdx @@ -0,0 +1,88 @@ +--- +title: Stream logs +description: Tail logs for a Prisma Compute version or deployment. +badge: early-access +url: /compute/logs +metaTitle: Stream logs | Prisma Compute +metaDescription: Stream logs from Prisma Compute versions and deployments using the Prisma CLI. Tail, replay, and resume log streams during Early Access. +--- + +Prisma Compute can stream logs for any compute version directly to your terminal. + +## Stream logs for a compute version + +### Using `@prisma/compute-cli` + +```bash +bunx @prisma/compute-cli logs +``` + +| Option | Description | +|---|---| +| `--tail ` | Number of recent lines to show (default: `100`) | +| `--from-start` | Start from the beginning of the log buffer instead of tailing | +| `--cursor ` | Resume from a byte-offset cursor returned by a previous stream | +| `--json` | Output each log record as a JSON line | + +Examples: + +```bash +# Tail the last 200 lines and follow +bunx @prisma/compute-cli logs v_042 --tail 200 + +# Replay from the start of the available buffer +bunx @prisma/compute-cli logs v_042 --from-start + +# Resume from where an earlier stream left off +bunx @prisma/compute-cli logs v_042 --cursor 104857600 + +# Emit structured JSON for pipelines or agents +bunx @prisma/compute-cli logs v_042 --json +``` + +### Using `@looma/prisma-cli` + +```bash +npx @looma/prisma-cli app logs +npx @looma/prisma-cli app logs --deployment +npx @looma/prisma-cli app logs --tail 200 +``` + +| Option | Description | +|---|---| +| `--app ` | App name | +| `--deployment ` | Specific deployment to stream | +| `--tail ` | Number of recent lines to show | +| `--from-start` | Start from the beginning of the log buffer | +| `--cursor ` | Resume from a prior log cursor | +| `--json` | Emit structured JSON output | + +## Find a compute version ID + +If you don't know the ID to pass to `logs`: + +```bash +# With @prisma/compute-cli +bunx @prisma/compute-cli versions list + +# With @looma/prisma-cli +npx @looma/prisma-cli app list-deploys +``` + +## Limitations during Early Access + +:::warning + +Log streaming has hard limits in the EA build. Plan around them when debugging: + +- **10-minute stream cap** — a single `logs` stream disconnects after ~10 minutes. Reconnect (optionally with `--cursor`) to continue. +- **One concurrent stream per version** — only one client can stream a given compute version at a time. A second stream will fail or bump the first. + +::: + +These limits will be relaxed after EA. For now, prefer short, targeted log sessions and reach for `--tail` to grab a bounded recent window instead of long-lived streams. + +## See also + +- [CLI reference](/compute/cli) +- [Known limitations](/compute/limitations) diff --git a/apps/docs/content/docs/compute/meta.json b/apps/docs/content/docs/compute/meta.json new file mode 100644 index 0000000000..351e58360d --- /dev/null +++ b/apps/docs/content/docs/compute/meta.json @@ -0,0 +1,17 @@ +{ + "title": "Compute", + "root": true, + "icon": "Cpu", + "pages": [ + "---Introduction---", + "index", + "---Quickstart---", + "quickstart-nextjs", + "quickstart-bun", + "---CLI---", + "cli", + "logs", + "---More---", + "limitations" + ] +} diff --git a/apps/docs/content/docs/compute/quickstart-bun.mdx b/apps/docs/content/docs/compute/quickstart-bun.mdx new file mode 100644 index 0000000000..15c511130e --- /dev/null +++ b/apps/docs/content/docs/compute/quickstart-bun.mdx @@ -0,0 +1,95 @@ +--- +title: Bun quickstart +description: Deploy a minimal Bun HTTP server to Prisma Compute. +badge: early-access +url: /compute/quickstart-bun +metaTitle: Bun quickstart | Prisma Compute +metaDescription: Scaffold a minimal Bun HTTP server and deploy it to Prisma Compute with the Prisma CLI. +--- + +This quickstart walks through deploying a minimal Bun HTTP server to Prisma Compute. Commands are shown for both CLIs that are usable during Early Access. + +## 1. Create the app + +```bash +mkdir my-bun-app +cd my-bun-app +bun init --yes +``` + +## 2. Write a minimal server + +Replace the contents of `index.ts` with: + +```typescript +Bun.serve({ + port: Number(process.env.PORT ?? 3000), + fetch() { + return new Response("Hello from Compute"); + }, +}); +``` + +## 3. Authenticate + +### Using `@looma/prisma-cli` + +```bash +npx @looma/prisma-cli auth login +``` + +### Using `@prisma/compute-cli` + +```bash +bunx @prisma/compute-cli login +``` + +:::note + +In CI or non-interactive environments, set `PRISMA_API_TOKEN` instead of running `auth login`. + +::: + +## 4. Deploy + +### Using `@looma/prisma-cli` + +```bash +npx @looma/prisma-cli app deploy --app my-bun-app --http-port 3000 +``` + +### Using `@prisma/compute-cli` + +```bash +bunx @prisma/compute-cli deploy --service-name my-bun-app --build-type bun --entrypoint index.ts --http-port 3000 +``` + +Once the project is linked, subsequent deploys don't need the scaffolding flags: + +```bash +npx @looma/prisma-cli app deploy --http-port 3000 +# or +bunx @prisma/compute-cli deploy --http-port 3000 +``` + +## 5. Inspect the deployment + +### Using `@looma/prisma-cli` + +```bash +npx @looma/prisma-cli app list-deploys +npx @looma/prisma-cli app show-deploy +``` + +### Using `@prisma/compute-cli` + +```bash +bunx @prisma/compute-cli versions list +bunx @prisma/compute-cli versions show +``` + +## Next steps + +- [Manage environment variables](/compute/cli#environment-variables) +- [Stream logs from your deployment](/compute/logs) +- [Known limitations](/compute/limitations) diff --git a/apps/docs/content/docs/compute/quickstart-nextjs.mdx b/apps/docs/content/docs/compute/quickstart-nextjs.mdx new file mode 100644 index 0000000000..e2afa031b7 --- /dev/null +++ b/apps/docs/content/docs/compute/quickstart-nextjs.mdx @@ -0,0 +1,93 @@ +--- +title: Next.js quickstart +description: Create a Next.js app and deploy it to Prisma Compute. +badge: early-access +url: /compute/quickstart-nextjs +metaTitle: Next.js quickstart | Prisma Compute +metaDescription: Create a Next.js app, configure standalone output, and deploy it to Prisma Compute with the Prisma CLI. +--- + +This quickstart walks through creating a fresh Next.js app and deploying it to Prisma Compute. Commands are shown for both CLIs that are usable during Early Access. + +## 1. Create the app + +```bash +pnpm create next-app@latest my-next-app --yes +cd my-next-app +``` + +## 2. Enable standalone output + +Prisma Compute currently requires Next.js's standalone build output. Update `next.config.ts` (or `next.config.mjs`): + +```typescript +const nextConfig = { + output: "standalone", +}; + +export default nextConfig; +``` + +## 3. Authenticate + +### Using `@looma/prisma-cli` + +```bash +npx @looma/prisma-cli auth login +``` + +### Using `@prisma/compute-cli` + +```bash +bunx @prisma/compute-cli login +``` + +:::note + +In CI or non-interactive environments, set `PRISMA_API_TOKEN` instead of running `auth login`. + +::: + +## 4. Deploy + +### Using `@looma/prisma-cli` + +```bash +npx @looma/prisma-cli app deploy --app my-next-app --build-type nextjs --http-port 3000 +``` + +### Using `@prisma/compute-cli` + +```bash +bunx @prisma/compute-cli deploy --service-name my-next-app --build-type nextjs --http-port 3000 +``` + +The first deploy bootstraps the local project context when no project is linked yet. After that, redeploys reuse the saved selection: + +```bash +npx @looma/prisma-cli app deploy --http-port 3000 +# or +bunx @prisma/compute-cli deploy --http-port 3000 +``` + +## 5. Inspect the deployment + +### Using `@looma/prisma-cli` + +```bash +npx @looma/prisma-cli app list-deploys +npx @looma/prisma-cli app show-deploy +``` + +### Using `@prisma/compute-cli` + +```bash +bunx @prisma/compute-cli versions list +bunx @prisma/compute-cli versions show +``` + +## Next steps + +- [Manage environment variables](/compute/cli#environment-variables) +- [Stream logs from your deployment](/compute/logs) +- [Known limitations](/compute/limitations) diff --git a/apps/docs/content/docs/meta.json b/apps/docs/content/docs/meta.json index 6b7db11405..746bdf60b1 100644 --- a/apps/docs/content/docs/meta.json +++ b/apps/docs/content/docs/meta.json @@ -5,6 +5,7 @@ "(index)", "orm", "postgres", + "compute", "cli", "guides", "studio", diff --git a/apps/docs/src/lib/layout.shared.tsx b/apps/docs/src/lib/layout.shared.tsx index ecad3a97cc..f0884dfadb 100644 --- a/apps/docs/src/lib/layout.shared.tsx +++ b/apps/docs/src/lib/layout.shared.tsx @@ -33,6 +33,11 @@ export const links: LinkItemTypeWithActivePaths[] = [ url: "/postgres", active: "nested-url", }, + { + text: "Compute", + url: "/compute", + active: "nested-url", + }, { text: "CLI", url: "/cli", From 99ed136b2535527e5d1e408f0a1120f62121576b Mon Sep 17 00:00:00 2001 From: ArthurGamby Date: Wed, 15 Apr 2026 14:15:29 +0300 Subject: [PATCH 02/15] refactor(docs): collapse Compute into a single internal reference page MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Merges the six sub-pages (quickstarts, CLI, logs, limitations) into one page at /docs/v7/compute, using Tabs for the Next.js|Bun choice and CodeBlockTabs for the @looma|@prisma/compute-cli choice — same ergonomic as npm|pnpm|yarn|bun code switching. Simpler for internal EA users who want everything in one place. Co-Authored-By: Claude Opus 4.6 (1M context) --- apps/docs/content/docs/compute/cli.mdx | 167 ----------- apps/docs/content/docs/compute/index.mdx | 266 +++++++++++++++--- .../docs/content/docs/compute/limitations.mdx | 42 --- apps/docs/content/docs/compute/logs.mdx | 88 ------ apps/docs/content/docs/compute/meta.json | 13 +- .../content/docs/compute/quickstart-bun.mdx | 95 ------- .../docs/compute/quickstart-nextjs.mdx | 93 ------ 7 files changed, 230 insertions(+), 534 deletions(-) delete mode 100644 apps/docs/content/docs/compute/cli.mdx delete mode 100644 apps/docs/content/docs/compute/limitations.mdx delete mode 100644 apps/docs/content/docs/compute/logs.mdx delete mode 100644 apps/docs/content/docs/compute/quickstart-bun.mdx delete mode 100644 apps/docs/content/docs/compute/quickstart-nextjs.mdx diff --git a/apps/docs/content/docs/compute/cli.mdx b/apps/docs/content/docs/compute/cli.mdx deleted file mode 100644 index aec441ad34..0000000000 --- a/apps/docs/content/docs/compute/cli.mdx +++ /dev/null @@ -1,167 +0,0 @@ ---- -title: CLI reference -description: Authenticate, deploy, and manage environment variables for Prisma Compute from the CLI. -badge: early-access -url: /compute/cli -metaTitle: CLI reference | Prisma Compute -metaDescription: Reference for the Prisma Compute CLIs. Authentication, deploy, and environment variable commands for @looma/prisma-cli and @prisma/compute-cli. ---- - -Two CLIs currently target Prisma Compute during Early Access. This page documents the commands needed day-to-day: install, authenticate, deploy, and manage environment variables. - -| Package | Binary | Typical invocation | -|---|---|---| -| [`@looma/prisma-cli`](https://www.npmjs.com/package/@looma/prisma-cli) | `prisma` | `npx @looma/prisma-cli …` | -| [`@prisma/compute-cli`](https://www.npmjs.com/package/@prisma/compute-cli) | `compute` | `bunx @prisma/compute-cli …` | - -## Authentication - -Run an interactive browser flow once per machine. Credentials are stored locally. - -### Using `@looma/prisma-cli` - -```bash -npx @looma/prisma-cli auth login -npx @looma/prisma-cli auth whoami -npx @looma/prisma-cli auth logout -``` - -### Using `@prisma/compute-cli` - -```bash -bunx @prisma/compute-cli login -bunx @prisma/compute-cli logout -``` - -For CI, scripts, and agents, set `PRISMA_API_TOKEN` in the environment instead of running the interactive flow. - -## Deploy - -### Using `@looma/prisma-cli` - -```bash -npx @looma/prisma-cli app deploy [options] -``` - -| Option | Description | -|---|---| -| `--app ` | App name | -| `--entry ` | Entry point path for Bun or auto-detected deploys | -| `--build-type ` | `auto`, `bun`, or `nextjs` (default: `auto`) | -| `--http-port ` | HTTP port the deployed app listens on | -| `--env ` | Environment variable (repeat for multiple) | -| `--json` | Emit structured JSON output | - -### Using `@prisma/compute-cli` - -```bash -bunx @prisma/compute-cli deploy [options] -``` - -| Option | Description | -|---|---| -| `--project ` | Project ID | -| `--service ` | Compute service ID | -| `--service-name ` | Name for a new compute service | -| `--region ` | Region for a new compute service | -| `--path ` | App directory (default: `.`) | -| `--entrypoint ` | File to run at startup (falls back to `package.json` `main`) | -| `--build-type ` | `auto`, `bun`, or `nextjs` (default: `auto`) | -| `--http-port ` | HTTP port the app listens on (default: `8080`) | -| `--env ` | Environment variable (repeat for multiple) | -| `--unset-env ` | Remove an environment variable (repeat for multiple) | -| `--skip-build` | Deploy a pre-built artifact | -| `--skip-promote` | Deploy without promoting to the service endpoint | -| `--destroy-old-version` | Delete the previous version after stopping it | -| `--json` | Output JSON | - -## Environment variables - -You can set environment variables two ways: inline with `deploy`, or with a dedicated update command that creates a new version without rebuilding source. - -### Set variables during a deploy - -Repeat `--env` for each variable. Values are stored on the platform and injected into the running version. - -#### Using `@looma/prisma-cli` - -```bash -npx @looma/prisma-cli app deploy \ - --app my-app \ - --env DATABASE_URL=postgresql://example \ - --env NODE_ENV=production -``` - -#### Using `@prisma/compute-cli` - -```bash -bunx @prisma/compute-cli deploy \ - --env DATABASE_URL=postgresql://example \ - --env NODE_ENV=production -``` - -### Update variables without rebuilding - -Use this when you only need to rotate or add a secret. Both commands cut a **new compute version** — the previous version stays live until the new one is healthy. - -#### Using `@looma/prisma-cli` - -```bash -npx @looma/prisma-cli app update-env --env DATABASE_URL=postgresql://example -npx @looma/prisma-cli app update-env --app my-app --env STRIPE_KEY=sk_live_… -``` - -List the current values: - -```bash -npx @looma/prisma-cli app list-env -npx @looma/prisma-cli app list-env --app my-app -``` - -#### Using `@prisma/compute-cli` - -```bash -bunx @prisma/compute-cli env update --env DATABASE_URL=postgresql://example -bunx @prisma/compute-cli env update \ - --env STRIPE_KEY=sk_live_… \ - --env NODE_ENV=production -``` - -### Remove variables - -Pass `--unset-env KEY` (repeat for multiple) on either `deploy` or `env update` with `@prisma/compute-cli`: - -```bash -bunx @prisma/compute-cli env update --unset-env LEGACY_FLAG --unset-env DEBUG -``` - -## Versions and services - -`@prisma/compute-cli` exposes primitives for managing versions and services directly: - -```bash -bunx @prisma/compute-cli versions list -bunx @prisma/compute-cli versions show -bunx @prisma/compute-cli versions start -bunx @prisma/compute-cli versions stop -bunx @prisma/compute-cli versions promote -bunx @prisma/compute-cli versions delete - -bunx @prisma/compute-cli services list -bunx @prisma/compute-cli projects list -``` - -With `@looma/prisma-cli`, equivalent operations live under `app`: - -```bash -npx @looma/prisma-cli app list-deploys -npx @looma/prisma-cli app show-deploy -npx @looma/prisma-cli app promote -npx @looma/prisma-cli app rollback -npx @looma/prisma-cli app remove -``` - -## See also - -- [Stream logs](/compute/logs) — tail logs for a compute version or deployment. -- [Known limitations](/compute/limitations) — what's still in flight during EA. diff --git a/apps/docs/content/docs/compute/index.mdx b/apps/docs/content/docs/compute/index.mdx index fef21b81c7..406e1261d5 100644 --- a/apps/docs/content/docs/compute/index.mdx +++ b/apps/docs/content/docs/compute/index.mdx @@ -1,54 +1,246 @@ --- title: Prisma Compute -description: Deploy Next.js and Bun applications to Prisma Compute from the CLI. +description: One-page internal reference for deploying apps to Prisma Compute during EA. badge: early-access url: /compute metaTitle: Prisma Compute -metaDescription: Prisma Compute is a simple, reliable app hosting runtime tightly integrated with Prisma Postgres. Deploy, observe, and manage apps from the terminal. +metaDescription: Internal one-page reference for deploying Next.js and Bun apps to Prisma Compute, managing environment variables, and streaming logs. --- -Prisma Compute is a simple, reliable app hosting runtime for Next.js and Bun applications, built with tight integration to Prisma Postgres and designed for a CLI-first, AI-native workflow. +App hosting for Next.js and Bun, driven from the CLI. Two CLIs are usable today — pick whichever you prefer: -## What you get +- [`@looma/prisma-cli`](https://www.npmjs.com/package/@looma/prisma-cli) — new unified `prisma app …` surface. +- [`@prisma/compute-cli`](https://www.npmjs.com/package/@prisma/compute-cli) — original `compute …` surface. -- **One-command deploys** for Next.js and Bun apps. -- **Two CLIs** currently coexist during EA: - - [`@looma/prisma-cli`](https://www.npmjs.com/package/@looma/prisma-cli) — the new unified Prisma CLI (`prisma app …`). - - [`@prisma/compute-cli`](https://www.npmjs.com/package/@prisma/compute-cli) — the original compute CLI (`compute …`). -- **Environment variables** managed from the CLI on every deploy or as a standalone update. -- **Log streaming** for any compute version. -- **Tight Prisma Postgres integration** — build against a managed Postgres without leaving the Prisma toolchain. +## Quickstart -## Getting started +Pick your starter and run the steps below. - - - Create a Next.js app and ship it to Compute in a few commands. - - - Deploy a minimal Bun HTTP server to Compute. - - + -## Reference + - - - Install, authenticate, deploy, and manage environment variables from the terminal. - - - Tail logs for a specific compute version or deployment. - - - What is and isn't supported during the EA window. - - +```bash +pnpm create next-app@latest my-app --yes +cd my-app +``` -## Which CLI should I use? +Enable standalone output in `next.config.ts`: -Both CLIs target the same platform. For EA: +```typescript +const nextConfig = { output: "standalone" }; +export default nextConfig; +``` -- Start with **`@looma/prisma-cli`** if you want the unified `prisma app` experience that we are standardizing on for Prisma 8. -- Fall back to **`@prisma/compute-cli`** if you hit an edge case, or for features that have only landed on the original CLI yet. + -Every quickstart and reference page on this site shows the equivalent command in both CLIs side by side. + + +```bash +mkdir my-app && cd my-app && bun init --yes +``` + +Replace `index.ts`: + +```typescript +Bun.serve({ + port: Number(process.env.PORT ?? 3000), + fetch() { + return new Response("Hello from Compute"); + }, +}); +``` + + + + + +Authenticate, then deploy: + + + + @looma/prisma-cli + @prisma/compute-cli + + + +```bash +npx @looma/prisma-cli auth login +npx @looma/prisma-cli app deploy --app my-app --http-port 3000 +``` + + + + +```bash +bunx @prisma/compute-cli login +bunx @prisma/compute-cli deploy --service-name my-app --http-port 3000 +``` + + + + +The first deploy bootstraps project context. Re-deploys reuse the saved selection — `app deploy` (or `deploy`) is enough. + +In CI, set `PRISMA_API_TOKEN` instead of running `auth login`. + +## Inspect a deployment + + + + @looma/prisma-cli + @prisma/compute-cli + + + +```bash +npx @looma/prisma-cli app list-deploys +npx @looma/prisma-cli app show-deploy +``` + + + + +```bash +bunx @prisma/compute-cli versions list +bunx @prisma/compute-cli versions show +``` + + + + +## Environment variables + +Set them inline on a deploy, or update without rebuilding (cuts a new version). + +**During a deploy** — repeat `--env` per variable: + + + + @looma/prisma-cli + @prisma/compute-cli + + + +```bash +npx @looma/prisma-cli app deploy \ + --env DATABASE_URL=postgresql://example \ + --env NODE_ENV=production +``` + + + + +```bash +bunx @prisma/compute-cli deploy \ + --env DATABASE_URL=postgresql://example \ + --env NODE_ENV=production +``` + + + + +**Without rebuilding** — same flag shape, dedicated command. Old version stays live until the new one is healthy: + + + + @looma/prisma-cli + @prisma/compute-cli + + + +```bash +npx @looma/prisma-cli app update-env --env STRIPE_KEY=sk_live_… +npx @looma/prisma-cli app list-env +``` + + + + +```bash +bunx @prisma/compute-cli env update --env STRIPE_KEY=sk_live_… +bunx @prisma/compute-cli env update --unset-env LEGACY_FLAG +``` + + + + +## Logs + +Stream logs for a specific compute version (or deployment): + + + + @prisma/compute-cli + @looma/prisma-cli + + + +```bash +bunx @prisma/compute-cli logs +bunx @prisma/compute-cli logs --tail 200 +bunx @prisma/compute-cli logs --from-start +bunx @prisma/compute-cli logs --cursor +``` + + + + +```bash +npx @looma/prisma-cli app logs +npx @looma/prisma-cli app logs --deployment +npx @looma/prisma-cli app logs --tail 200 +``` + + + + +EA log limits: ~10-min stream cap (reconnect with `--cursor`), one concurrent stream per version. + +## Limitations + +- Next.js apps must use `output: "standalone"`. +- First-class support for **Next.js** and **Bun/Hono** only. +- `env update` / `app update-env` cuts a new compute version — old version stays live until the new one is healthy. +- No bulk `.env` import yet — repeat `--env KEY=VALUE`. +- Logs: 10-min stream cap, one concurrent stream per version. + +## Useful CLI inventory + + + + @looma/prisma-cli + @prisma/compute-cli + + + +```bash +prisma auth login | logout | whoami +prisma project ... +prisma app build | run | deploy | update-env | list-env +prisma app show | open | logs +prisma app list-deploys | show-deploy | promote | rollback | remove +``` + + + + +```bash +compute login | logout +compute deploy [--project --service --service-name --region --path + --entrypoint --build-type auto|bun|nextjs --http-port + --env KEY=VALUE --unset-env KEY + --skip-build --skip-promote --destroy-old-version --json] +compute logs [--tail --from-start --cursor --json] +compute env update [--env --unset-env --http-port] +compute versions list | show | start | stop | promote | delete | destroy +compute services list +compute projects list +``` + + + + +Need a flag that isn't here? Run `--help` on the relevant command — both CLIs have stable, browsable help output. + +Questions or breakage during EA: `#product-compute`. diff --git a/apps/docs/content/docs/compute/limitations.mdx b/apps/docs/content/docs/compute/limitations.mdx deleted file mode 100644 index d5ae569649..0000000000 --- a/apps/docs/content/docs/compute/limitations.mdx +++ /dev/null @@ -1,42 +0,0 @@ ---- -title: Known limitations -description: What is and isn't supported in Prisma Compute during Early Access. -badge: early-access -url: /compute/limitations -metaTitle: Known limitations | Prisma Compute -metaDescription: A running list of known limitations in Prisma Compute during the Early Access window. ---- - -Prisma Compute is moving fast during Early Access. This page is the running list of known limitations — keep it close while you're building. - -## Runtime - -- **Next.js apps require `output: "standalone"`.** Set this in `next.config.ts` / `next.config.mjs` before your first deploy. See the [Next.js quickstart](/compute/quickstart-nextjs#2-enable-standalone-output). -- **First-class framework support** for this release covers **Next.js** and **Bun/Hono** only. - -## CLI - -- **Two CLIs coexist.** `@looma/prisma-cli` (unified `prisma app …`) is the direction of travel; `@prisma/compute-cli` (original `compute …`) is the fallback for features or fixes that haven't reached the new CLI yet. -- **First deploy bootstraps local project context** automatically when no project is linked. Subsequent deploys reuse the saved selection, so the scaffolding flags aren't required each time. - -## Log streaming - -- **10-minute stream cap.** A single log stream disconnects after ~10 minutes — reconnect, optionally with `--cursor`, to continue. -- **One concurrent stream per version.** Only one client can stream a given compute version at a time. - -See [Stream logs](/compute/logs) for reconnection patterns. - -## Environment variables - -- `env update` (or `app update-env`) **cuts a new compute version**. The old version stays live until the new one is healthy. -- There is no bulk import from a `.env` file yet — pass `--env KEY=VALUE` for each variable, or repeat the flag. - -## Out of scope for EA - -These are intentionally deferred until after the EA window closes: - -- Canary / traffic-split deploys. -- Multi-region routing controls. -- Console UI parity with the CLI (some actions are CLI-only today — the Console may offer a "copy this command" affordance instead). - -If you hit something that isn't listed here and isn't documented elsewhere, share it in `#product-compute` so we can fold it in. diff --git a/apps/docs/content/docs/compute/logs.mdx b/apps/docs/content/docs/compute/logs.mdx deleted file mode 100644 index c5c211fc68..0000000000 --- a/apps/docs/content/docs/compute/logs.mdx +++ /dev/null @@ -1,88 +0,0 @@ ---- -title: Stream logs -description: Tail logs for a Prisma Compute version or deployment. -badge: early-access -url: /compute/logs -metaTitle: Stream logs | Prisma Compute -metaDescription: Stream logs from Prisma Compute versions and deployments using the Prisma CLI. Tail, replay, and resume log streams during Early Access. ---- - -Prisma Compute can stream logs for any compute version directly to your terminal. - -## Stream logs for a compute version - -### Using `@prisma/compute-cli` - -```bash -bunx @prisma/compute-cli logs -``` - -| Option | Description | -|---|---| -| `--tail ` | Number of recent lines to show (default: `100`) | -| `--from-start` | Start from the beginning of the log buffer instead of tailing | -| `--cursor ` | Resume from a byte-offset cursor returned by a previous stream | -| `--json` | Output each log record as a JSON line | - -Examples: - -```bash -# Tail the last 200 lines and follow -bunx @prisma/compute-cli logs v_042 --tail 200 - -# Replay from the start of the available buffer -bunx @prisma/compute-cli logs v_042 --from-start - -# Resume from where an earlier stream left off -bunx @prisma/compute-cli logs v_042 --cursor 104857600 - -# Emit structured JSON for pipelines or agents -bunx @prisma/compute-cli logs v_042 --json -``` - -### Using `@looma/prisma-cli` - -```bash -npx @looma/prisma-cli app logs -npx @looma/prisma-cli app logs --deployment -npx @looma/prisma-cli app logs --tail 200 -``` - -| Option | Description | -|---|---| -| `--app ` | App name | -| `--deployment ` | Specific deployment to stream | -| `--tail ` | Number of recent lines to show | -| `--from-start` | Start from the beginning of the log buffer | -| `--cursor ` | Resume from a prior log cursor | -| `--json` | Emit structured JSON output | - -## Find a compute version ID - -If you don't know the ID to pass to `logs`: - -```bash -# With @prisma/compute-cli -bunx @prisma/compute-cli versions list - -# With @looma/prisma-cli -npx @looma/prisma-cli app list-deploys -``` - -## Limitations during Early Access - -:::warning - -Log streaming has hard limits in the EA build. Plan around them when debugging: - -- **10-minute stream cap** — a single `logs` stream disconnects after ~10 minutes. Reconnect (optionally with `--cursor`) to continue. -- **One concurrent stream per version** — only one client can stream a given compute version at a time. A second stream will fail or bump the first. - -::: - -These limits will be relaxed after EA. For now, prefer short, targeted log sessions and reach for `--tail` to grab a bounded recent window instead of long-lived streams. - -## See also - -- [CLI reference](/compute/cli) -- [Known limitations](/compute/limitations) diff --git a/apps/docs/content/docs/compute/meta.json b/apps/docs/content/docs/compute/meta.json index 351e58360d..4babcd75f0 100644 --- a/apps/docs/content/docs/compute/meta.json +++ b/apps/docs/content/docs/compute/meta.json @@ -2,16 +2,5 @@ "title": "Compute", "root": true, "icon": "Cpu", - "pages": [ - "---Introduction---", - "index", - "---Quickstart---", - "quickstart-nextjs", - "quickstart-bun", - "---CLI---", - "cli", - "logs", - "---More---", - "limitations" - ] + "pages": ["index"] } diff --git a/apps/docs/content/docs/compute/quickstart-bun.mdx b/apps/docs/content/docs/compute/quickstart-bun.mdx deleted file mode 100644 index 15c511130e..0000000000 --- a/apps/docs/content/docs/compute/quickstart-bun.mdx +++ /dev/null @@ -1,95 +0,0 @@ ---- -title: Bun quickstart -description: Deploy a minimal Bun HTTP server to Prisma Compute. -badge: early-access -url: /compute/quickstart-bun -metaTitle: Bun quickstart | Prisma Compute -metaDescription: Scaffold a minimal Bun HTTP server and deploy it to Prisma Compute with the Prisma CLI. ---- - -This quickstart walks through deploying a minimal Bun HTTP server to Prisma Compute. Commands are shown for both CLIs that are usable during Early Access. - -## 1. Create the app - -```bash -mkdir my-bun-app -cd my-bun-app -bun init --yes -``` - -## 2. Write a minimal server - -Replace the contents of `index.ts` with: - -```typescript -Bun.serve({ - port: Number(process.env.PORT ?? 3000), - fetch() { - return new Response("Hello from Compute"); - }, -}); -``` - -## 3. Authenticate - -### Using `@looma/prisma-cli` - -```bash -npx @looma/prisma-cli auth login -``` - -### Using `@prisma/compute-cli` - -```bash -bunx @prisma/compute-cli login -``` - -:::note - -In CI or non-interactive environments, set `PRISMA_API_TOKEN` instead of running `auth login`. - -::: - -## 4. Deploy - -### Using `@looma/prisma-cli` - -```bash -npx @looma/prisma-cli app deploy --app my-bun-app --http-port 3000 -``` - -### Using `@prisma/compute-cli` - -```bash -bunx @prisma/compute-cli deploy --service-name my-bun-app --build-type bun --entrypoint index.ts --http-port 3000 -``` - -Once the project is linked, subsequent deploys don't need the scaffolding flags: - -```bash -npx @looma/prisma-cli app deploy --http-port 3000 -# or -bunx @prisma/compute-cli deploy --http-port 3000 -``` - -## 5. Inspect the deployment - -### Using `@looma/prisma-cli` - -```bash -npx @looma/prisma-cli app list-deploys -npx @looma/prisma-cli app show-deploy -``` - -### Using `@prisma/compute-cli` - -```bash -bunx @prisma/compute-cli versions list -bunx @prisma/compute-cli versions show -``` - -## Next steps - -- [Manage environment variables](/compute/cli#environment-variables) -- [Stream logs from your deployment](/compute/logs) -- [Known limitations](/compute/limitations) diff --git a/apps/docs/content/docs/compute/quickstart-nextjs.mdx b/apps/docs/content/docs/compute/quickstart-nextjs.mdx deleted file mode 100644 index e2afa031b7..0000000000 --- a/apps/docs/content/docs/compute/quickstart-nextjs.mdx +++ /dev/null @@ -1,93 +0,0 @@ ---- -title: Next.js quickstart -description: Create a Next.js app and deploy it to Prisma Compute. -badge: early-access -url: /compute/quickstart-nextjs -metaTitle: Next.js quickstart | Prisma Compute -metaDescription: Create a Next.js app, configure standalone output, and deploy it to Prisma Compute with the Prisma CLI. ---- - -This quickstart walks through creating a fresh Next.js app and deploying it to Prisma Compute. Commands are shown for both CLIs that are usable during Early Access. - -## 1. Create the app - -```bash -pnpm create next-app@latest my-next-app --yes -cd my-next-app -``` - -## 2. Enable standalone output - -Prisma Compute currently requires Next.js's standalone build output. Update `next.config.ts` (or `next.config.mjs`): - -```typescript -const nextConfig = { - output: "standalone", -}; - -export default nextConfig; -``` - -## 3. Authenticate - -### Using `@looma/prisma-cli` - -```bash -npx @looma/prisma-cli auth login -``` - -### Using `@prisma/compute-cli` - -```bash -bunx @prisma/compute-cli login -``` - -:::note - -In CI or non-interactive environments, set `PRISMA_API_TOKEN` instead of running `auth login`. - -::: - -## 4. Deploy - -### Using `@looma/prisma-cli` - -```bash -npx @looma/prisma-cli app deploy --app my-next-app --build-type nextjs --http-port 3000 -``` - -### Using `@prisma/compute-cli` - -```bash -bunx @prisma/compute-cli deploy --service-name my-next-app --build-type nextjs --http-port 3000 -``` - -The first deploy bootstraps the local project context when no project is linked yet. After that, redeploys reuse the saved selection: - -```bash -npx @looma/prisma-cli app deploy --http-port 3000 -# or -bunx @prisma/compute-cli deploy --http-port 3000 -``` - -## 5. Inspect the deployment - -### Using `@looma/prisma-cli` - -```bash -npx @looma/prisma-cli app list-deploys -npx @looma/prisma-cli app show-deploy -``` - -### Using `@prisma/compute-cli` - -```bash -bunx @prisma/compute-cli versions list -bunx @prisma/compute-cli versions show -``` - -## Next steps - -- [Manage environment variables](/compute/cli#environment-variables) -- [Stream logs from your deployment](/compute/logs) -- [Known limitations](/compute/limitations) From 6426dd1a274b83241cc5de6e48741a7f3ad0ca6d Mon Sep 17 00:00:00 2001 From: ArthurGamby Date: Wed, 15 Apr 2026 14:20:35 +0300 Subject: [PATCH 03/15] docs(compute): drop em dashes and ellipses from prose Co-Authored-By: Claude Opus 4.6 (1M context) --- apps/docs/content/docs/compute/index.mdx | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/apps/docs/content/docs/compute/index.mdx b/apps/docs/content/docs/compute/index.mdx index 406e1261d5..5f659896ab 100644 --- a/apps/docs/content/docs/compute/index.mdx +++ b/apps/docs/content/docs/compute/index.mdx @@ -7,10 +7,10 @@ metaTitle: Prisma Compute metaDescription: Internal one-page reference for deploying Next.js and Bun apps to Prisma Compute, managing environment variables, and streaming logs. --- -App hosting for Next.js and Bun, driven from the CLI. Two CLIs are usable today — pick whichever you prefer: +App hosting for Next.js and Bun, driven from the CLI. Two CLIs are usable today, pick whichever you prefer: -- [`@looma/prisma-cli`](https://www.npmjs.com/package/@looma/prisma-cli) — new unified `prisma app …` surface. -- [`@prisma/compute-cli`](https://www.npmjs.com/package/@prisma/compute-cli) — original `compute …` surface. +- [`@looma/prisma-cli`](https://www.npmjs.com/package/@looma/prisma-cli): new unified `prisma app` surface. +- [`@prisma/compute-cli`](https://www.npmjs.com/package/@prisma/compute-cli): original `compute` surface. ## Quickstart @@ -80,7 +80,7 @@ bunx @prisma/compute-cli deploy --service-name my-app --http-port 3000 -The first deploy bootstraps project context. Re-deploys reuse the saved selection — `app deploy` (or `deploy`) is enough. +The first deploy bootstraps project context. Re-deploys reuse the saved selection, so `app deploy` (or `deploy`) is enough. In CI, set `PRISMA_API_TOKEN` instead of running `auth login`. @@ -113,7 +113,7 @@ bunx @prisma/compute-cli versions show Set them inline on a deploy, or update without rebuilding (cuts a new version). -**During a deploy** — repeat `--env` per variable: +**During a deploy**, repeat `--env` per variable: @@ -140,7 +140,7 @@ bunx @prisma/compute-cli deploy \ -**Without rebuilding** — same flag shape, dedicated command. Old version stays live until the new one is healthy: +**Without rebuilding**: same flag shape, dedicated command. Old version stays live until the new one is healthy. @@ -150,7 +150,7 @@ bunx @prisma/compute-cli deploy \ ```bash -npx @looma/prisma-cli app update-env --env STRIPE_KEY=sk_live_… +npx @looma/prisma-cli app update-env --env STRIPE_KEY=sk_live_xxx npx @looma/prisma-cli app list-env ``` @@ -158,7 +158,7 @@ npx @looma/prisma-cli app list-env ```bash -bunx @prisma/compute-cli env update --env STRIPE_KEY=sk_live_… +bunx @prisma/compute-cli env update --env STRIPE_KEY=sk_live_xxx bunx @prisma/compute-cli env update --unset-env LEGACY_FLAG ``` @@ -201,8 +201,8 @@ EA log limits: ~10-min stream cap (reconnect with `--cursor`), one concurrent st - Next.js apps must use `output: "standalone"`. - First-class support for **Next.js** and **Bun/Hono** only. -- `env update` / `app update-env` cuts a new compute version — old version stays live until the new one is healthy. -- No bulk `.env` import yet — repeat `--env KEY=VALUE`. +- `env update` / `app update-env` cuts a new compute version. The old version stays live until the new one is healthy. +- No bulk `.env` import yet, repeat `--env KEY=VALUE` for each variable. - Logs: 10-min stream cap, one concurrent stream per version. ## Useful CLI inventory @@ -241,6 +241,6 @@ compute projects list -Need a flag that isn't here? Run `--help` on the relevant command — both CLIs have stable, browsable help output. +Need a flag that isn't here? Run `--help` on the relevant command. Both CLIs have stable, browsable help output. Questions or breakage during EA: `#product-compute`. From ac6d693a401319e8132296bf5514fd83f0706cc1 Mon Sep 17 00:00:00 2001 From: ArthurGamby Date: Thu, 23 Apr 2026 12:28:58 +0200 Subject: [PATCH 04/15] docs(compute): add Astro, Nuxt, and TanStack Start to quickstart Reflect the new SDK build strategies (prisma/project-compute#67) in the internal Compute docs. Adds framework-specific scaffolding tabs and updates the limitations list to replace "Next.js and Bun/Hono only". Deploys stay zero-flag; the SDK auto-detects the framework. Refs: PTL-1391 --- apps/docs/content/docs/compute/index.mdx | 58 ++++++++++++++++++++++-- 1 file changed, 54 insertions(+), 4 deletions(-) diff --git a/apps/docs/content/docs/compute/index.mdx b/apps/docs/content/docs/compute/index.mdx index 5f659896ab..9669a9ea8d 100644 --- a/apps/docs/content/docs/compute/index.mdx +++ b/apps/docs/content/docs/compute/index.mdx @@ -4,10 +4,12 @@ description: One-page internal reference for deploying apps to Prisma Compute du badge: early-access url: /compute metaTitle: Prisma Compute -metaDescription: Internal one-page reference for deploying Next.js and Bun apps to Prisma Compute, managing environment variables, and streaming logs. +metaDescription: Internal one-page reference for deploying Next.js, Astro, Nuxt, TanStack Start, and Bun apps to Prisma Compute, managing environment variables, and streaming logs. --- -App hosting for Next.js and Bun, driven from the CLI. Two CLIs are usable today, pick whichever you prefer: +App hosting for Node.js and Bun apps, driven from the CLI. First-class support for Next.js, Astro, Nuxt, TanStack Start, and Bun. Deploys are zero-flag: the SDK auto-detects the framework from your `package.json` and config. + +Two CLIs are usable today, pick whichever you prefer: - [`@looma/prisma-cli`](https://www.npmjs.com/package/@looma/prisma-cli): new unified `prisma app` surface. - [`@prisma/compute-cli`](https://www.npmjs.com/package/@prisma/compute-cli): original `compute` surface. @@ -16,7 +18,7 @@ App hosting for Next.js and Bun, driven from the CLI. Two CLIs are usable today, Pick your starter and run the steps below. - + @@ -34,6 +36,53 @@ export default nextConfig; + + +```bash +pnpm create astro@latest my-app +cd my-app +pnpm add @astrojs/node +``` + +Enable SSR with the Node adapter in standalone mode in `astro.config.mjs`: + +```typescript +import { defineConfig } from "astro/config"; +import node from "@astrojs/node"; + +export default defineConfig({ + output: "server", + adapter: node({ mode: "standalone" }), +}); +``` + +Default port: `4321`. + + + + + +```bash +pnpm create nuxt my-app +cd my-app +``` + +No extra config. Nuxt builds with the Nitro `node-server` preset by default. + +Default port: `3000`. + + + + + +Scaffold from the official TanStack Start starter (Vite + Nitro `node` preset) and `cd` into the project. + +No extra config. Ensure `vite.config.ts` includes the `tanstackStart()` and `nitro()` plugins. + +Default port: `3000`. + + + ```bash @@ -199,8 +248,9 @@ EA log limits: ~10-min stream cap (reconnect with `--cursor`), one concurrent st ## Limitations +- Framework support: **Next.js**, **Astro**, **Nuxt**, **TanStack Start**, and **Bun**. - Next.js apps must use `output: "standalone"`. -- First-class support for **Next.js** and **Bun/Hono** only. +- Astro apps need `@astrojs/node` in standalone mode. - `env update` / `app update-env` cuts a new compute version. The old version stays live until the new one is healthy. - No bulk `.env` import yet, repeat `--env KEY=VALUE` for each variable. - Logs: 10-min stream cap, one concurrent stream per version. From 8353ddf862b53b055b7ee5263536b8b7136b2904 Mon Sep 17 00:00:00 2001 From: ArthurGamby Date: Thu, 23 Apr 2026 12:40:12 +0200 Subject: [PATCH 05/15] docs(compute): clarify Quickstart tab scope and fix port note - Drop the redundant `description` frontmatter field (metaDescription covers SEO). - Reframe the Quickstart intro so it explicitly says the tab choice updates the scaffold and config below. - Restructure each framework tab panel as a numbered list so the multi-step nature is visually obvious. - Add a transition line after the Tabs block to mark the start of framework-agnostic content. - Add a port-defaults note under the deploy block (Astro uses 4321, others 3000). --- apps/docs/content/docs/compute/index.mdx | 104 +++++++++++++---------- 1 file changed, 61 insertions(+), 43 deletions(-) diff --git a/apps/docs/content/docs/compute/index.mdx b/apps/docs/content/docs/compute/index.mdx index 9669a9ea8d..b06d93a59a 100644 --- a/apps/docs/content/docs/compute/index.mdx +++ b/apps/docs/content/docs/compute/index.mdx @@ -1,6 +1,5 @@ --- title: Prisma Compute -description: One-page internal reference for deploying apps to Prisma Compute during EA. badge: early-access url: /compute metaTitle: Prisma Compute @@ -16,45 +15,56 @@ Two CLIs are usable today, pick whichever you prefer: ## Quickstart -Pick your starter and run the steps below. +Pick your framework below. The scaffold command and any required config in this section update to match your selection. -```bash -pnpm create next-app@latest my-app --yes -cd my-app -``` +1. Scaffold the app: -Enable standalone output in `next.config.ts`: + ```bash + pnpm create next-app@latest my-app --yes + cd my-app + ``` -```typescript -const nextConfig = { output: "standalone" }; -export default nextConfig; -``` +2. Enable standalone output in `next.config.ts`: + + ```typescript + const nextConfig = { output: "standalone" }; + export default nextConfig; + ``` + +Default port: `3000`. -```bash -pnpm create astro@latest my-app -cd my-app -pnpm add @astrojs/node -``` +1. Scaffold the app: -Enable SSR with the Node adapter in standalone mode in `astro.config.mjs`: + ```bash + pnpm create astro@latest my-app + cd my-app + ``` -```typescript -import { defineConfig } from "astro/config"; -import node from "@astrojs/node"; +2. Add the Node adapter: -export default defineConfig({ - output: "server", - adapter: node({ mode: "standalone" }), -}); -``` + ```bash + pnpm add @astrojs/node + ``` + +3. Enable SSR with the Node adapter in standalone mode in `astro.config.mjs`: + + ```typescript + import { defineConfig } from "astro/config"; + import node from "@astrojs/node"; + + export default defineConfig({ + output: "server", + adapter: node({ mode: "standalone" }), + }); + ``` Default port: `4321`. @@ -62,10 +72,12 @@ Default port: `4321`. -```bash -pnpm create nuxt my-app -cd my-app -``` +1. Scaffold the app: + + ```bash + pnpm create nuxt my-app + cd my-app + ``` No extra config. Nuxt builds with the Nitro `node-server` preset by default. @@ -75,7 +87,7 @@ Default port: `3000`. -Scaffold from the official TanStack Start starter (Vite + Nitro `node` preset) and `cd` into the project. +1. Scaffold from the official TanStack Start starter (Vite + Nitro `node` preset) and `cd` into the project. No extra config. Ensure `vite.config.ts` includes the `tanstackStart()` and `nitro()` plugins. @@ -85,26 +97,30 @@ Default port: `3000`. -```bash -mkdir my-app && cd my-app && bun init --yes -``` +1. Initialize the app: -Replace `index.ts`: + ```bash + mkdir my-app && cd my-app && bun init --yes + ``` -```typescript -Bun.serve({ - port: Number(process.env.PORT ?? 3000), - fetch() { - return new Response("Hello from Compute"); - }, -}); -``` +2. Replace `index.ts`: + + ```typescript + Bun.serve({ + port: Number(process.env.PORT ?? 3000), + fetch() { + return new Response("Hello from Compute"); + }, + }); + ``` + +Default port: `3000`. -Authenticate, then deploy: +With the app scaffolded, authenticate and deploy. The steps below are the same across frameworks. @@ -129,6 +145,8 @@ bunx @prisma/compute-cli deploy --service-name my-app --http-port 3000 +Port defaults by framework: Next.js, Nuxt, TanStack Start, and Bun use `3000`; Astro uses `4321`. Pass `--http-port ` on the first deploy to match. + The first deploy bootstraps project context. Re-deploys reuse the saved selection, so `app deploy` (or `deploy`) is enough. In CI, set `PRISMA_API_TOKEN` instead of running `auth login`. From 18936fa50d4a7929ea9b35757892b254082a7670 Mon Sep 17 00:00:00 2001 From: ArthurGamby Date: Thu, 23 Apr 2026 12:48:52 +0200 Subject: [PATCH 06/15] docs(compute): split into landing + per-framework quickstarts + reference pages Replaces the single-page tab layout with a multi-page structure modeled on the Prisma Postgres docs: - `compute/index.mdx` becomes a landing page with a Cards grid linking to framework-specific quickstarts and reference pages. - `compute/quickstart/` holds one self-contained page per framework (Next.js, Astro, Nuxt, TanStack Start, Bun), each walking from scaffold through first deploy with the correct `--http-port` for that framework. - Reference material splits into focused pages: `environment-variables`, `logs`, `cli`, and `limitations`. - `meta.json` is updated with `---Introduction---`, `---Quickstart---`, `---Reference---`, and `---More---` section separators to match the Postgres sidebar pattern. Rationale: the previous Tabs-inside-one-page layout visually signalled that tab selection only affected the code block immediately below, when in practice it changed multiple sections. Sub-pages give each framework its own dedicated space and make the deploy command's framework-specific port (Astro 4321 vs 3000 elsewhere) legible without inline notes. Refs: PTL-1391 --- apps/docs/content/docs/compute/cli.mdx | 75 ++++ .../docs/compute/environment-variables.mdx | 69 ++++ apps/docs/content/docs/compute/index.mdx | 347 +++--------------- .../docs/content/docs/compute/limitations.mdx | 33 ++ apps/docs/content/docs/compute/logs.mdx | 42 +++ apps/docs/content/docs/compute/meta.json | 13 +- .../content/docs/compute/quickstart/astro.mdx | 79 ++++ .../content/docs/compute/quickstart/bun.mdx | 69 ++++ .../content/docs/compute/quickstart/meta.json | 4 + .../docs/compute/quickstart/nextjs.mdx | 68 ++++ .../content/docs/compute/quickstart/nuxt.mdx | 59 +++ .../compute/quickstart/tanstack-start.mdx | 72 ++++ 12 files changed, 629 insertions(+), 301 deletions(-) create mode 100644 apps/docs/content/docs/compute/cli.mdx create mode 100644 apps/docs/content/docs/compute/environment-variables.mdx create mode 100644 apps/docs/content/docs/compute/limitations.mdx create mode 100644 apps/docs/content/docs/compute/logs.mdx create mode 100644 apps/docs/content/docs/compute/quickstart/astro.mdx create mode 100644 apps/docs/content/docs/compute/quickstart/bun.mdx create mode 100644 apps/docs/content/docs/compute/quickstart/meta.json create mode 100644 apps/docs/content/docs/compute/quickstart/nextjs.mdx create mode 100644 apps/docs/content/docs/compute/quickstart/nuxt.mdx create mode 100644 apps/docs/content/docs/compute/quickstart/tanstack-start.mdx diff --git a/apps/docs/content/docs/compute/cli.mdx b/apps/docs/content/docs/compute/cli.mdx new file mode 100644 index 0000000000..35dcda6dbc --- /dev/null +++ b/apps/docs/content/docs/compute/cli.mdx @@ -0,0 +1,75 @@ +--- +title: CLI reference +badge: early-access +url: /compute/cli +metaTitle: CLI reference | Prisma Compute +metaDescription: Command inventory for deploying and managing Prisma Compute apps with @looma/prisma-cli or @prisma/compute-cli. +--- + +Two CLIs are usable today. Pick whichever fits your workflow. Both authenticate the same way and target the same backend. + +- [`@looma/prisma-cli`](https://www.npmjs.com/package/@looma/prisma-cli): unified `prisma app` surface. +- [`@prisma/compute-cli`](https://www.npmjs.com/package/@prisma/compute-cli): original `compute` surface. + +## Inspect a deployment + + + + @looma/prisma-cli + @prisma/compute-cli + + + +```bash +npx @looma/prisma-cli app list-deploys +npx @looma/prisma-cli app show-deploy +``` + + + + +```bash +bunx @prisma/compute-cli versions list +bunx @prisma/compute-cli versions show +``` + + + + +## Command inventory + + + + @looma/prisma-cli + @prisma/compute-cli + + + +```bash +prisma auth login | logout | whoami +prisma project ... +prisma app build | run | deploy | update-env | list-env +prisma app show | open | logs +prisma app list-deploys | show-deploy | promote | rollback | remove +``` + + + + +```bash +compute login | logout +compute deploy [--project --service --service-name --region --path + --entrypoint --build-type auto|bun|nextjs --http-port + --env KEY=VALUE --unset-env KEY + --skip-build --skip-promote --destroy-old-version --json] +compute logs [--tail --from-start --cursor --json] +compute env update [--env --unset-env --http-port] +compute versions list | show | start | stop | promote | delete | destroy +compute services list +compute projects list +``` + + + + +Need a flag that is not listed here? Run `--help` on the relevant command. Both CLIs have stable, browsable help output. diff --git a/apps/docs/content/docs/compute/environment-variables.mdx b/apps/docs/content/docs/compute/environment-variables.mdx new file mode 100644 index 0000000000..11f2db6991 --- /dev/null +++ b/apps/docs/content/docs/compute/environment-variables.mdx @@ -0,0 +1,69 @@ +--- +title: Environment variables +badge: early-access +url: /compute/environment-variables +metaTitle: Environment variables | Prisma Compute +metaDescription: Set environment variables on a Prisma Compute deployment, either inline on deploy or without rebuilding. +--- + +Set environment variables inline when deploying, or update them later without rebuilding. Either path cuts a new compute version. The old version stays live until the new one is healthy. + +## During a deploy + +Repeat `--env` per variable: + + + + @looma/prisma-cli + @prisma/compute-cli + + + +```bash +npx @looma/prisma-cli app deploy \ + --env DATABASE_URL=postgresql://example \ + --env NODE_ENV=production +``` + + + + +```bash +bunx @prisma/compute-cli deploy \ + --env DATABASE_URL=postgresql://example \ + --env NODE_ENV=production +``` + + + + +## Without rebuilding + +Same flag shape, dedicated command: + + + + @looma/prisma-cli + @prisma/compute-cli + + + +```bash +npx @looma/prisma-cli app update-env --env STRIPE_KEY=sk_live_xxx +npx @looma/prisma-cli app list-env +``` + + + + +```bash +bunx @prisma/compute-cli env update --env STRIPE_KEY=sk_live_xxx +bunx @prisma/compute-cli env update --unset-env LEGACY_FLAG +``` + + + + +:::note +No bulk `.env` import yet. Repeat `--env KEY=VALUE` for each variable. +::: diff --git a/apps/docs/content/docs/compute/index.mdx b/apps/docs/content/docs/compute/index.mdx index b06d93a59a..ff8669242d 100644 --- a/apps/docs/content/docs/compute/index.mdx +++ b/apps/docs/content/docs/compute/index.mdx @@ -3,312 +3,59 @@ title: Prisma Compute badge: early-access url: /compute metaTitle: Prisma Compute -metaDescription: Internal one-page reference for deploying Next.js, Astro, Nuxt, TanStack Start, and Bun apps to Prisma Compute, managing environment variables, and streaming logs. +metaDescription: Internal one-stop reference for deploying Next.js, Astro, Nuxt, TanStack Start, and Bun apps to Prisma Compute, managing environment variables, and streaming logs. --- -App hosting for Node.js and Bun apps, driven from the CLI. First-class support for Next.js, Astro, Nuxt, TanStack Start, and Bun. Deploys are zero-flag: the SDK auto-detects the framework from your `package.json` and config. +Prisma Compute is app hosting for Node.js and Bun apps, driven from the CLI. First-class support for Next.js, Astro, Nuxt, TanStack Start, and Bun. Deploys are zero-flag on the SDK side: the framework is auto-detected from your `package.json` and config. Two CLIs are usable today, pick whichever you prefer: -- [`@looma/prisma-cli`](https://www.npmjs.com/package/@looma/prisma-cli): new unified `prisma app` surface. +- [`@looma/prisma-cli`](https://www.npmjs.com/package/@looma/prisma-cli): unified `prisma app` surface. - [`@prisma/compute-cli`](https://www.npmjs.com/package/@prisma/compute-cli): original `compute` surface. -## Quickstart - -Pick your framework below. The scaffold command and any required config in this section update to match your selection. - - - - - -1. Scaffold the app: - - ```bash - pnpm create next-app@latest my-app --yes - cd my-app - ``` - -2. Enable standalone output in `next.config.ts`: - - ```typescript - const nextConfig = { output: "standalone" }; - export default nextConfig; - ``` - -Default port: `3000`. - - - - - -1. Scaffold the app: - - ```bash - pnpm create astro@latest my-app - cd my-app - ``` - -2. Add the Node adapter: - - ```bash - pnpm add @astrojs/node - ``` - -3. Enable SSR with the Node adapter in standalone mode in `astro.config.mjs`: - - ```typescript - import { defineConfig } from "astro/config"; - import node from "@astrojs/node"; - - export default defineConfig({ - output: "server", - adapter: node({ mode: "standalone" }), - }); - ``` - -Default port: `4321`. - - - - - -1. Scaffold the app: - - ```bash - pnpm create nuxt my-app - cd my-app - ``` - -No extra config. Nuxt builds with the Nitro `node-server` preset by default. - -Default port: `3000`. - - - - - -1. Scaffold from the official TanStack Start starter (Vite + Nitro `node` preset) and `cd` into the project. - -No extra config. Ensure `vite.config.ts` includes the `tanstackStart()` and `nitro()` plugins. - -Default port: `3000`. - - - - - -1. Initialize the app: - - ```bash - mkdir my-app && cd my-app && bun init --yes - ``` - -2. Replace `index.ts`: - - ```typescript - Bun.serve({ - port: Number(process.env.PORT ?? 3000), - fetch() { - return new Response("Hello from Compute"); - }, - }); - ``` - -Default port: `3000`. - - - - - -With the app scaffolded, authenticate and deploy. The steps below are the same across frameworks. - - - - @looma/prisma-cli - @prisma/compute-cli - - - -```bash -npx @looma/prisma-cli auth login -npx @looma/prisma-cli app deploy --app my-app --http-port 3000 -``` - - - - -```bash -bunx @prisma/compute-cli login -bunx @prisma/compute-cli deploy --service-name my-app --http-port 3000 -``` - - - - -Port defaults by framework: Next.js, Nuxt, TanStack Start, and Bun use `3000`; Astro uses `4321`. Pass `--http-port ` on the first deploy to match. - -The first deploy bootstraps project context. Re-deploys reuse the saved selection, so `app deploy` (or `deploy`) is enough. - -In CI, set `PRISMA_API_TOKEN` instead of running `auth login`. - -## Inspect a deployment - - - - @looma/prisma-cli - @prisma/compute-cli - - - -```bash -npx @looma/prisma-cli app list-deploys -npx @looma/prisma-cli app show-deploy -``` - - - - -```bash -bunx @prisma/compute-cli versions list -bunx @prisma/compute-cli versions show -``` - - - - -## Environment variables - -Set them inline on a deploy, or update without rebuilding (cuts a new version). - -**During a deploy**, repeat `--env` per variable: - - - - @looma/prisma-cli - @prisma/compute-cli - - - -```bash -npx @looma/prisma-cli app deploy \ - --env DATABASE_URL=postgresql://example \ - --env NODE_ENV=production -``` - - - - -```bash -bunx @prisma/compute-cli deploy \ - --env DATABASE_URL=postgresql://example \ - --env NODE_ENV=production -``` - - - - -**Without rebuilding**: same flag shape, dedicated command. Old version stays live until the new one is healthy. - - - - @looma/prisma-cli - @prisma/compute-cli - - - -```bash -npx @looma/prisma-cli app update-env --env STRIPE_KEY=sk_live_xxx -npx @looma/prisma-cli app list-env -``` - - - - -```bash -bunx @prisma/compute-cli env update --env STRIPE_KEY=sk_live_xxx -bunx @prisma/compute-cli env update --unset-env LEGACY_FLAG -``` - - - - -## Logs - -Stream logs for a specific compute version (or deployment): - - - - @prisma/compute-cli - @looma/prisma-cli - - - -```bash -bunx @prisma/compute-cli logs -bunx @prisma/compute-cli logs --tail 200 -bunx @prisma/compute-cli logs --from-start -bunx @prisma/compute-cli logs --cursor -``` - - - - -```bash -npx @looma/prisma-cli app logs -npx @looma/prisma-cli app logs --deployment -npx @looma/prisma-cli app logs --tail 200 -``` - - - - -EA log limits: ~10-min stream cap (reconnect with `--cursor`), one concurrent stream per version. - -## Limitations - -- Framework support: **Next.js**, **Astro**, **Nuxt**, **TanStack Start**, and **Bun**. -- Next.js apps must use `output: "standalone"`. -- Astro apps need `@astrojs/node` in standalone mode. -- `env update` / `app update-env` cuts a new compute version. The old version stays live until the new one is healthy. -- No bulk `.env` import yet, repeat `--env KEY=VALUE` for each variable. -- Logs: 10-min stream cap, one concurrent stream per version. - -## Useful CLI inventory - - - - @looma/prisma-cli - @prisma/compute-cli - - - -```bash -prisma auth login | logout | whoami -prisma project ... -prisma app build | run | deploy | update-env | list-env -prisma app show | open | logs -prisma app list-deploys | show-deploy | promote | rollback | remove -``` - - - - -```bash -compute login | logout -compute deploy [--project --service --service-name --region --path - --entrypoint --build-type auto|bun|nextjs --http-port - --env KEY=VALUE --unset-env KEY - --skip-build --skip-promote --destroy-old-version --json] -compute logs [--tail --from-start --cursor --json] -compute env update [--env --unset-env --http-port] -compute versions list | show | start | stop | promote | delete | destroy -compute services list -compute projects list -``` - - - - -Need a flag that isn't here? Run `--help` on the relevant command. Both CLIs have stable, browsable help output. +See the full [CLI reference](/compute/cli) for both. + +## Pick a quickstart + +Each quickstart walks you from a fresh app to a live deployment. Pick the one that matches your stack. + + + + Scaffold, enable standalone output, and deploy. + + + Set up the Node adapter in standalone mode and deploy on port 4321. + + + Scaffold and deploy with the default Nitro node-server preset. + + + Deploy the official Vite plus Nitro starter. + + + Deploy a Bun.serve HTTP server directly. + + + +## Manage a deployment + +After the first deploy, use these references day-to-day. + + + + Set secrets and config inline on deploy, or update later without rebuilding. + + + Stream runtime logs per compute version or deployment. + + + Full command inventory for both `@looma/prisma-cli` and `@prisma/compute-cli`. + + + Known EA caveats around framework support, env updates, and log streaming. + + + +## Support Questions or breakage during EA: `#product-compute`. diff --git a/apps/docs/content/docs/compute/limitations.mdx b/apps/docs/content/docs/compute/limitations.mdx new file mode 100644 index 0000000000..bbc056a8d2 --- /dev/null +++ b/apps/docs/content/docs/compute/limitations.mdx @@ -0,0 +1,33 @@ +--- +title: Limitations +badge: early-access +url: /compute/limitations +metaTitle: Limitations | Prisma Compute +metaDescription: Known Prisma Compute limitations during Early Access, covering framework support, env updates, and log streaming. +--- + +Known caveats while Compute is in Early Access. + +## Framework support + +First-class support: **Next.js**, **Astro**, **Nuxt**, **TanStack Start**, and **Bun**. Other Node.js frameworks may build via auto-detection, but are not explicitly tested. + +Framework-specific requirements: + +- **Next.js**: must use `output: "standalone"` in `next.config.ts`. +- **Astro**: needs `@astrojs/node` in standalone mode via the adapter. + +## Environment updates + +`env update` (compute) and `app update-env` (looma) each cut a new compute version. The old version stays live until the new one is healthy. + +No bulk `.env` import yet. Repeat `--env KEY=VALUE` for each variable. + +## Logs + +- Stream caps at around 10 minutes. Reconnect with `--cursor `. +- One concurrent log stream per compute version. + +## Support + +Questions or breakage during EA: `#product-compute`. diff --git a/apps/docs/content/docs/compute/logs.mdx b/apps/docs/content/docs/compute/logs.mdx new file mode 100644 index 0000000000..7530fc4edb --- /dev/null +++ b/apps/docs/content/docs/compute/logs.mdx @@ -0,0 +1,42 @@ +--- +title: Logs +badge: early-access +url: /compute/logs +metaTitle: Logs | Prisma Compute +metaDescription: Stream runtime logs from a Prisma Compute deployment, with EA limits documented. +--- + +Stream logs for a specific compute version or deployment. + +## Stream logs + + + + @prisma/compute-cli + @looma/prisma-cli + + + +```bash +bunx @prisma/compute-cli logs +bunx @prisma/compute-cli logs --tail 200 +bunx @prisma/compute-cli logs --from-start +bunx @prisma/compute-cli logs --cursor +``` + + + + +```bash +npx @looma/prisma-cli app logs +npx @looma/prisma-cli app logs --deployment +npx @looma/prisma-cli app logs --tail 200 +``` + + + + +## EA limits + +- Stream caps at around 10 minutes. Reconnect with `--cursor ` to resume from where the last stream ended. +- Only one concurrent log stream per compute version. diff --git a/apps/docs/content/docs/compute/meta.json b/apps/docs/content/docs/compute/meta.json index 4babcd75f0..450fa47106 100644 --- a/apps/docs/content/docs/compute/meta.json +++ b/apps/docs/content/docs/compute/meta.json @@ -2,5 +2,16 @@ "title": "Compute", "root": true, "icon": "Cpu", - "pages": ["index"] + "pages": [ + "---Introduction---", + "index", + "---Quickstart---", + "...quickstart", + "---Reference---", + "environment-variables", + "logs", + "cli", + "---More---", + "limitations" + ] } diff --git a/apps/docs/content/docs/compute/quickstart/astro.mdx b/apps/docs/content/docs/compute/quickstart/astro.mdx new file mode 100644 index 0000000000..1d76d2a2db --- /dev/null +++ b/apps/docs/content/docs/compute/quickstart/astro.mdx @@ -0,0 +1,79 @@ +--- +title: Astro +badge: early-access +url: /compute/quickstart/astro +metaTitle: "Quickstart: Deploy an Astro app to Prisma Compute" +metaDescription: Scaffold an Astro app with the Node adapter in standalone mode and deploy it to Prisma Compute during EA. +--- + +Deploy an Astro app to Prisma Compute using the `@astrojs/node` adapter in standalone mode. Astro serves on port `4321` by default, so the first deploy command sets `--http-port 4321`. + +## Prerequisites + +- Node.js 20+ +- A Prisma account logged in via CLI (covered in step 4) + +## 1. Scaffold the app + +```bash +pnpm create astro@latest my-app +cd my-app +``` + +## 2. Add the Node adapter + +```bash +pnpm add @astrojs/node +``` + +## 3. Enable SSR with the Node adapter + +Edit `astro.config.mjs`: + +```typescript title="astro.config.mjs" +import { defineConfig } from "astro/config"; +import node from "@astrojs/node"; + +export default defineConfig({ + output: "server", + adapter: node({ mode: "standalone" }), +}); +``` + +Compute deploys Astro apps in standalone mode. Without this adapter config, the build does not emit a Node server entry Compute can run. + +## 4. Authenticate and deploy + + + + @looma/prisma-cli + @prisma/compute-cli + + + +```bash +npx @looma/prisma-cli auth login +npx @looma/prisma-cli app deploy --app my-app --http-port 4321 +``` + + + + +```bash +bunx @prisma/compute-cli login +bunx @prisma/compute-cli deploy --service-name my-app --http-port 4321 +``` + + + + +The first deploy bootstraps project context. Re-deploys reuse the saved selection, so `app deploy` (or `deploy`) is enough. + +In CI, set `PRISMA_API_TOKEN` instead of running `auth login`. + +## Next steps + +- [Environment variables](/compute/environment-variables): set secrets and config at deploy time or after. +- [Logs](/compute/logs): stream runtime logs per deployment. +- [CLI reference](/compute/cli): full command inventory for both CLIs. +- [Limitations](/compute/limitations): known EA caveats. diff --git a/apps/docs/content/docs/compute/quickstart/bun.mdx b/apps/docs/content/docs/compute/quickstart/bun.mdx new file mode 100644 index 0000000000..e80e879c79 --- /dev/null +++ b/apps/docs/content/docs/compute/quickstart/bun.mdx @@ -0,0 +1,69 @@ +--- +title: Bun +badge: early-access +url: /compute/quickstart/bun +metaTitle: "Quickstart: Deploy a Bun app to Prisma Compute" +metaDescription: Scaffold a Bun HTTP server and deploy it to Prisma Compute during EA. +--- + +Deploy a Bun HTTP server to Prisma Compute. Bun.serve apps are supported directly, no bundler or adapter required. + +## Prerequisites + +- [Bun](https://bun.sh) installed locally +- A Prisma account logged in via CLI (covered in step 3) + +## 1. Initialize the app + +```bash +mkdir my-app && cd my-app && bun init --yes +``` + +## 2. Replace `index.ts` + +```typescript title="index.ts" +Bun.serve({ + port: Number(process.env.PORT ?? 3000), + fetch() { + return new Response("Hello from Compute"); + }, +}); +``` + +Reading `PORT` from the environment keeps the server aligned with Compute's injected port. + +## 3. Authenticate and deploy + + + + @looma/prisma-cli + @prisma/compute-cli + + + +```bash +npx @looma/prisma-cli auth login +npx @looma/prisma-cli app deploy --app my-app --http-port 3000 +``` + + + + +```bash +bunx @prisma/compute-cli login +bunx @prisma/compute-cli deploy --service-name my-app --http-port 3000 +``` + + + + +The first deploy bootstraps project context. Re-deploys reuse the saved selection, so `app deploy` (or `deploy`) is enough. + +In CI, set `PRISMA_API_TOKEN` instead of running `auth login`. + +## Next steps + +- [Environment variables](/compute/environment-variables): set secrets and config at deploy time or after. +- [Logs](/compute/logs): stream runtime logs per deployment. +- [CLI reference](/compute/cli): full command inventory for both CLIs. +- [Limitations](/compute/limitations): known EA caveats. diff --git a/apps/docs/content/docs/compute/quickstart/meta.json b/apps/docs/content/docs/compute/quickstart/meta.json new file mode 100644 index 0000000000..8f77f50952 --- /dev/null +++ b/apps/docs/content/docs/compute/quickstart/meta.json @@ -0,0 +1,4 @@ +{ + "title": "Quickstart", + "pages": ["nextjs", "astro", "nuxt", "tanstack-start", "bun"] +} diff --git a/apps/docs/content/docs/compute/quickstart/nextjs.mdx b/apps/docs/content/docs/compute/quickstart/nextjs.mdx new file mode 100644 index 0000000000..72096b1457 --- /dev/null +++ b/apps/docs/content/docs/compute/quickstart/nextjs.mdx @@ -0,0 +1,68 @@ +--- +title: Next.js +badge: early-access +url: /compute/quickstart/nextjs +metaTitle: "Quickstart: Deploy a Next.js app to Prisma Compute" +metaDescription: Scaffold a Next.js app, enable standalone output, and deploy it to Prisma Compute during EA. +--- + +Deploy a Next.js app to Prisma Compute. This quickstart walks through scaffolding a fresh app, enabling standalone output (required by Compute), and running the first deploy with either `@looma/prisma-cli` or `@prisma/compute-cli`. + +## Prerequisites + +- Node.js 20+ +- A Prisma account logged in via CLI (covered in step 3) + +## 1. Scaffold the app + +```bash +pnpm create next-app@latest my-app --yes +cd my-app +``` + +## 2. Enable standalone output + +Edit `next.config.ts`: + +```typescript title="next.config.ts" +const nextConfig = { output: "standalone" }; +export default nextConfig; +``` + +Compute deploys Next.js apps in standalone mode. Without this flag, the build output does not include the server entry Compute expects. + +## 3. Authenticate and deploy + + + + @looma/prisma-cli + @prisma/compute-cli + + + +```bash +npx @looma/prisma-cli auth login +npx @looma/prisma-cli app deploy --app my-app --http-port 3000 +``` + + + + +```bash +bunx @prisma/compute-cli login +bunx @prisma/compute-cli deploy --service-name my-app --http-port 3000 +``` + + + + +The first deploy bootstraps project context. Re-deploys reuse the saved selection, so `app deploy` (or `deploy`) is enough. + +In CI, set `PRISMA_API_TOKEN` instead of running `auth login`. + +## Next steps + +- [Environment variables](/compute/environment-variables): set secrets and config at deploy time or after. +- [Logs](/compute/logs): stream runtime logs per deployment. +- [CLI reference](/compute/cli): full command inventory for both CLIs. +- [Limitations](/compute/limitations): known EA caveats. diff --git a/apps/docs/content/docs/compute/quickstart/nuxt.mdx b/apps/docs/content/docs/compute/quickstart/nuxt.mdx new file mode 100644 index 0000000000..7f6fc85205 --- /dev/null +++ b/apps/docs/content/docs/compute/quickstart/nuxt.mdx @@ -0,0 +1,59 @@ +--- +title: Nuxt +badge: early-access +url: /compute/quickstart/nuxt +metaTitle: "Quickstart: Deploy a Nuxt app to Prisma Compute" +metaDescription: Scaffold a Nuxt app and deploy it to Prisma Compute during EA. No extra config, Nuxt uses the Nitro node-server preset by default. +--- + +Deploy a Nuxt app to Prisma Compute. Nuxt builds with the Nitro `node-server` preset by default, so no adapter config is required. + +## Prerequisites + +- Node.js 20+ +- A Prisma account logged in via CLI (covered in step 2) + +## 1. Scaffold the app + +```bash +pnpm create nuxt my-app +cd my-app +``` + +No extra config is needed. The default build output targets Node. + +## 2. Authenticate and deploy + + + + @looma/prisma-cli + @prisma/compute-cli + + + +```bash +npx @looma/prisma-cli auth login +npx @looma/prisma-cli app deploy --app my-app --http-port 3000 +``` + + + + +```bash +bunx @prisma/compute-cli login +bunx @prisma/compute-cli deploy --service-name my-app --http-port 3000 +``` + + + + +The first deploy bootstraps project context. Re-deploys reuse the saved selection, so `app deploy` (or `deploy`) is enough. + +In CI, set `PRISMA_API_TOKEN` instead of running `auth login`. + +## Next steps + +- [Environment variables](/compute/environment-variables): set secrets and config at deploy time or after. +- [Logs](/compute/logs): stream runtime logs per deployment. +- [CLI reference](/compute/cli): full command inventory for both CLIs. +- [Limitations](/compute/limitations): known EA caveats. diff --git a/apps/docs/content/docs/compute/quickstart/tanstack-start.mdx b/apps/docs/content/docs/compute/quickstart/tanstack-start.mdx new file mode 100644 index 0000000000..4ee39b3a8a --- /dev/null +++ b/apps/docs/content/docs/compute/quickstart/tanstack-start.mdx @@ -0,0 +1,72 @@ +--- +title: TanStack Start +badge: early-access +url: /compute/quickstart/tanstack-start +metaTitle: "Quickstart: Deploy a TanStack Start app to Prisma Compute" +metaDescription: Scaffold a TanStack Start app (Vite + Nitro node preset) and deploy it to Prisma Compute during EA. +--- + +Deploy a TanStack Start app to Prisma Compute. TanStack Start builds with Vite and the Nitro `node` preset, both already wired in the official starter. + +## Prerequisites + +- Node.js 20+ +- A Prisma account logged in via CLI (covered in step 2) + +## 1. Scaffold the app + +Scaffold from the [official TanStack Start starter](https://tanstack.com/start/latest/docs/framework/react/getting-started) and `cd` into the project. Ensure `vite.config.ts` includes the `tanstackStart()` and `nitro()` plugins, which match the detection the Compute SDK expects. + +Example `vite.config.ts`: + +```typescript title="vite.config.ts" +import { defineConfig } from "vite"; +import { tanstackStart } from "@tanstack/react-start/plugin/vite"; +import viteReact from "@vitejs/plugin-react"; +import { nitro } from "nitro/vite"; + +export default defineConfig({ + server: { port: 3000 }, + plugins: [ + tanstackStart(), + nitro(), + viteReact(), + ], +}); +``` + +## 2. Authenticate and deploy + + + + @looma/prisma-cli + @prisma/compute-cli + + + +```bash +npx @looma/prisma-cli auth login +npx @looma/prisma-cli app deploy --app my-app --http-port 3000 +``` + + + + +```bash +bunx @prisma/compute-cli login +bunx @prisma/compute-cli deploy --service-name my-app --http-port 3000 +``` + + + + +The first deploy bootstraps project context. Re-deploys reuse the saved selection, so `app deploy` (or `deploy`) is enough. + +In CI, set `PRISMA_API_TOKEN` instead of running `auth login`. + +## Next steps + +- [Environment variables](/compute/environment-variables): set secrets and config at deploy time or after. +- [Logs](/compute/logs): stream runtime logs per deployment. +- [CLI reference](/compute/cli): full command inventory for both CLIs. +- [Limitations](/compute/limitations): known EA caveats. From 9fc4672a422a1bbcdc027fa30ab9276b490eb95d Mon Sep 17 00:00:00 2001 From: ArthurGamby Date: Thu, 23 Apr 2026 12:50:32 +0200 Subject: [PATCH 07/15] docs(compute): remove early-access badge and EA references Drops the `badge: early-access` frontmatter from every Compute page and rewrites the remaining "EA" / "Early Access" mentions (metaDescriptions, section headings, support lines) to unbadged equivalents. --- apps/docs/content/docs/compute/cli.mdx | 1 - apps/docs/content/docs/compute/environment-variables.mdx | 1 - apps/docs/content/docs/compute/index.mdx | 5 ++--- apps/docs/content/docs/compute/limitations.mdx | 7 +++---- apps/docs/content/docs/compute/logs.mdx | 5 ++--- apps/docs/content/docs/compute/quickstart/astro.mdx | 5 ++--- apps/docs/content/docs/compute/quickstart/bun.mdx | 5 ++--- apps/docs/content/docs/compute/quickstart/nextjs.mdx | 5 ++--- apps/docs/content/docs/compute/quickstart/nuxt.mdx | 5 ++--- .../content/docs/compute/quickstart/tanstack-start.mdx | 5 ++--- 10 files changed, 17 insertions(+), 27 deletions(-) diff --git a/apps/docs/content/docs/compute/cli.mdx b/apps/docs/content/docs/compute/cli.mdx index 35dcda6dbc..c635a72252 100644 --- a/apps/docs/content/docs/compute/cli.mdx +++ b/apps/docs/content/docs/compute/cli.mdx @@ -1,6 +1,5 @@ --- title: CLI reference -badge: early-access url: /compute/cli metaTitle: CLI reference | Prisma Compute metaDescription: Command inventory for deploying and managing Prisma Compute apps with @looma/prisma-cli or @prisma/compute-cli. diff --git a/apps/docs/content/docs/compute/environment-variables.mdx b/apps/docs/content/docs/compute/environment-variables.mdx index 11f2db6991..1f29b66e2d 100644 --- a/apps/docs/content/docs/compute/environment-variables.mdx +++ b/apps/docs/content/docs/compute/environment-variables.mdx @@ -1,6 +1,5 @@ --- title: Environment variables -badge: early-access url: /compute/environment-variables metaTitle: Environment variables | Prisma Compute metaDescription: Set environment variables on a Prisma Compute deployment, either inline on deploy or without rebuilding. diff --git a/apps/docs/content/docs/compute/index.mdx b/apps/docs/content/docs/compute/index.mdx index ff8669242d..ea9ee00329 100644 --- a/apps/docs/content/docs/compute/index.mdx +++ b/apps/docs/content/docs/compute/index.mdx @@ -1,6 +1,5 @@ --- title: Prisma Compute -badge: early-access url: /compute metaTitle: Prisma Compute metaDescription: Internal one-stop reference for deploying Next.js, Astro, Nuxt, TanStack Start, and Bun apps to Prisma Compute, managing environment variables, and streaming logs. @@ -52,10 +51,10 @@ After the first deploy, use these references day-to-day. Full command inventory for both `@looma/prisma-cli` and `@prisma/compute-cli`. - Known EA caveats around framework support, env updates, and log streaming. + Known caveats around framework support, env updates, and log streaming. ## Support -Questions or breakage during EA: `#product-compute`. +Questions or breakage: `#product-compute`. diff --git a/apps/docs/content/docs/compute/limitations.mdx b/apps/docs/content/docs/compute/limitations.mdx index bbc056a8d2..f580ca0cc6 100644 --- a/apps/docs/content/docs/compute/limitations.mdx +++ b/apps/docs/content/docs/compute/limitations.mdx @@ -1,12 +1,11 @@ --- title: Limitations -badge: early-access url: /compute/limitations metaTitle: Limitations | Prisma Compute -metaDescription: Known Prisma Compute limitations during Early Access, covering framework support, env updates, and log streaming. +metaDescription: Known Prisma Compute limitations covering framework support, env updates, and log streaming. --- -Known caveats while Compute is in Early Access. +Known caveats. ## Framework support @@ -30,4 +29,4 @@ No bulk `.env` import yet. Repeat `--env KEY=VALUE` for each variable. ## Support -Questions or breakage during EA: `#product-compute`. +Questions or breakage: `#product-compute`. diff --git a/apps/docs/content/docs/compute/logs.mdx b/apps/docs/content/docs/compute/logs.mdx index 7530fc4edb..0cea9be119 100644 --- a/apps/docs/content/docs/compute/logs.mdx +++ b/apps/docs/content/docs/compute/logs.mdx @@ -1,9 +1,8 @@ --- title: Logs -badge: early-access url: /compute/logs metaTitle: Logs | Prisma Compute -metaDescription: Stream runtime logs from a Prisma Compute deployment, with EA limits documented. +metaDescription: Stream runtime logs from a Prisma Compute deployment. --- Stream logs for a specific compute version or deployment. @@ -36,7 +35,7 @@ npx @looma/prisma-cli app logs --tail 200 -## EA limits +## Limits - Stream caps at around 10 minutes. Reconnect with `--cursor ` to resume from where the last stream ended. - Only one concurrent log stream per compute version. diff --git a/apps/docs/content/docs/compute/quickstart/astro.mdx b/apps/docs/content/docs/compute/quickstart/astro.mdx index 1d76d2a2db..83627f7d69 100644 --- a/apps/docs/content/docs/compute/quickstart/astro.mdx +++ b/apps/docs/content/docs/compute/quickstart/astro.mdx @@ -1,9 +1,8 @@ --- title: Astro -badge: early-access url: /compute/quickstart/astro metaTitle: "Quickstart: Deploy an Astro app to Prisma Compute" -metaDescription: Scaffold an Astro app with the Node adapter in standalone mode and deploy it to Prisma Compute during EA. +metaDescription: Scaffold an Astro app with the Node adapter in standalone mode and deploy it to Prisma Compute. --- Deploy an Astro app to Prisma Compute using the `@astrojs/node` adapter in standalone mode. Astro serves on port `4321` by default, so the first deploy command sets `--http-port 4321`. @@ -76,4 +75,4 @@ In CI, set `PRISMA_API_TOKEN` instead of running `auth login`. - [Environment variables](/compute/environment-variables): set secrets and config at deploy time or after. - [Logs](/compute/logs): stream runtime logs per deployment. - [CLI reference](/compute/cli): full command inventory for both CLIs. -- [Limitations](/compute/limitations): known EA caveats. +- [Limitations](/compute/limitations): known caveats. diff --git a/apps/docs/content/docs/compute/quickstart/bun.mdx b/apps/docs/content/docs/compute/quickstart/bun.mdx index e80e879c79..46fe430365 100644 --- a/apps/docs/content/docs/compute/quickstart/bun.mdx +++ b/apps/docs/content/docs/compute/quickstart/bun.mdx @@ -1,9 +1,8 @@ --- title: Bun -badge: early-access url: /compute/quickstart/bun metaTitle: "Quickstart: Deploy a Bun app to Prisma Compute" -metaDescription: Scaffold a Bun HTTP server and deploy it to Prisma Compute during EA. +metaDescription: Scaffold a Bun HTTP server and deploy it to Prisma Compute. --- Deploy a Bun HTTP server to Prisma Compute. Bun.serve apps are supported directly, no bundler or adapter required. @@ -66,4 +65,4 @@ In CI, set `PRISMA_API_TOKEN` instead of running `auth login`. - [Environment variables](/compute/environment-variables): set secrets and config at deploy time or after. - [Logs](/compute/logs): stream runtime logs per deployment. - [CLI reference](/compute/cli): full command inventory for both CLIs. -- [Limitations](/compute/limitations): known EA caveats. +- [Limitations](/compute/limitations): known caveats. diff --git a/apps/docs/content/docs/compute/quickstart/nextjs.mdx b/apps/docs/content/docs/compute/quickstart/nextjs.mdx index 72096b1457..4f24d1e04b 100644 --- a/apps/docs/content/docs/compute/quickstart/nextjs.mdx +++ b/apps/docs/content/docs/compute/quickstart/nextjs.mdx @@ -1,9 +1,8 @@ --- title: Next.js -badge: early-access url: /compute/quickstart/nextjs metaTitle: "Quickstart: Deploy a Next.js app to Prisma Compute" -metaDescription: Scaffold a Next.js app, enable standalone output, and deploy it to Prisma Compute during EA. +metaDescription: Scaffold a Next.js app, enable standalone output, and deploy it to Prisma Compute. --- Deploy a Next.js app to Prisma Compute. This quickstart walks through scaffolding a fresh app, enabling standalone output (required by Compute), and running the first deploy with either `@looma/prisma-cli` or `@prisma/compute-cli`. @@ -65,4 +64,4 @@ In CI, set `PRISMA_API_TOKEN` instead of running `auth login`. - [Environment variables](/compute/environment-variables): set secrets and config at deploy time or after. - [Logs](/compute/logs): stream runtime logs per deployment. - [CLI reference](/compute/cli): full command inventory for both CLIs. -- [Limitations](/compute/limitations): known EA caveats. +- [Limitations](/compute/limitations): known caveats. diff --git a/apps/docs/content/docs/compute/quickstart/nuxt.mdx b/apps/docs/content/docs/compute/quickstart/nuxt.mdx index 7f6fc85205..6532ae1323 100644 --- a/apps/docs/content/docs/compute/quickstart/nuxt.mdx +++ b/apps/docs/content/docs/compute/quickstart/nuxt.mdx @@ -1,9 +1,8 @@ --- title: Nuxt -badge: early-access url: /compute/quickstart/nuxt metaTitle: "Quickstart: Deploy a Nuxt app to Prisma Compute" -metaDescription: Scaffold a Nuxt app and deploy it to Prisma Compute during EA. No extra config, Nuxt uses the Nitro node-server preset by default. +metaDescription: Scaffold a Nuxt app and deploy it to Prisma Compute. No extra config, Nuxt uses the Nitro node-server preset by default. --- Deploy a Nuxt app to Prisma Compute. Nuxt builds with the Nitro `node-server` preset by default, so no adapter config is required. @@ -56,4 +55,4 @@ In CI, set `PRISMA_API_TOKEN` instead of running `auth login`. - [Environment variables](/compute/environment-variables): set secrets and config at deploy time or after. - [Logs](/compute/logs): stream runtime logs per deployment. - [CLI reference](/compute/cli): full command inventory for both CLIs. -- [Limitations](/compute/limitations): known EA caveats. +- [Limitations](/compute/limitations): known caveats. diff --git a/apps/docs/content/docs/compute/quickstart/tanstack-start.mdx b/apps/docs/content/docs/compute/quickstart/tanstack-start.mdx index 4ee39b3a8a..0089097177 100644 --- a/apps/docs/content/docs/compute/quickstart/tanstack-start.mdx +++ b/apps/docs/content/docs/compute/quickstart/tanstack-start.mdx @@ -1,9 +1,8 @@ --- title: TanStack Start -badge: early-access url: /compute/quickstart/tanstack-start metaTitle: "Quickstart: Deploy a TanStack Start app to Prisma Compute" -metaDescription: Scaffold a TanStack Start app (Vite + Nitro node preset) and deploy it to Prisma Compute during EA. +metaDescription: Scaffold a TanStack Start app (Vite + Nitro node preset) and deploy it to Prisma Compute. --- Deploy a TanStack Start app to Prisma Compute. TanStack Start builds with Vite and the Nitro `node` preset, both already wired in the official starter. @@ -69,4 +68,4 @@ In CI, set `PRISMA_API_TOKEN` instead of running `auth login`. - [Environment variables](/compute/environment-variables): set secrets and config at deploy time or after. - [Logs](/compute/logs): stream runtime logs per deployment. - [CLI reference](/compute/cli): full command inventory for both CLIs. -- [Limitations](/compute/limitations): known EA caveats. +- [Limitations](/compute/limitations): known caveats. From cc06ce48020a9a6ba1501871dc6c297503ee8137 Mon Sep 17 00:00:00 2001 From: ArthurGamby Date: Thu, 23 Apr 2026 12:56:56 +0200 Subject: [PATCH 08/15] docs(compute): document --env file path, comma-separated, and quoted formats Reflects project-compute PR #68 (merged 2026-04-22) which expanded `@prisma/compute-cli`'s `--env` handling. Adds a "Bulk input" section showing the three new formats (`.env` file path, comma-separated assignments, quoted values with commas) and notes that `@looma/prisma-cli` still accepts only one `KEY=VALUE` per `--env` flag. Drops the now-stale "No bulk .env import yet" caveat from `limitations.mdx` and replaces it with a short note on the CLI parity gap. --- .../docs/compute/environment-variables.mdx | 38 ++++++++++++++++++- .../docs/content/docs/compute/limitations.mdx | 2 +- 2 files changed, 37 insertions(+), 3 deletions(-) diff --git a/apps/docs/content/docs/compute/environment-variables.mdx b/apps/docs/content/docs/compute/environment-variables.mdx index 1f29b66e2d..c31341b67a 100644 --- a/apps/docs/content/docs/compute/environment-variables.mdx +++ b/apps/docs/content/docs/compute/environment-variables.mdx @@ -2,7 +2,7 @@ title: Environment variables url: /compute/environment-variables metaTitle: Environment variables | Prisma Compute -metaDescription: Set environment variables on a Prisma Compute deployment, either inline on deploy or without rebuilding. +metaDescription: Set environment variables on a Prisma Compute deployment, either inline on deploy or without rebuilding. Supports KEY=VALUE, comma-separated assignments, and dotenv file paths. --- Set environment variables inline when deploying, or update them later without rebuilding. Either path cuts a new compute version. The old version stays live until the new one is healthy. @@ -63,6 +63,40 @@ bunx @prisma/compute-cli env update --unset-env LEGACY_FLAG +## Bulk input with `@prisma/compute-cli` + +`@prisma/compute-cli` accepts three `--env` input formats. They can be combined on the same command and `--env` is repeatable. When a key appears more than once, the later value wins. + +**Load a `.env` file:** + +```bash +bunx @prisma/compute-cli deploy --env ./.env.production +``` + +The file is parsed with standard dotenv rules (comments, `export KEY=VALUE`, quoted values, inline comments). Malformed lines fail fast. + +**Comma-separated assignments in one flag:** + +```bash +bunx @prisma/compute-cli deploy --env FOO=1,BAR=2 +``` + +**Values that contain commas:** wrap the whole assignment in single quotes and the value in double quotes: + +```bash +bunx @prisma/compute-cli deploy --env 'DB_URL="postgres://user:pass@host/db?options=a,b"' +``` + +For complex values (URLs with query params, multi-line secrets), a `.env` file is easier to get right than inline quoting. + +**Mix them:** + +```bash +bunx @prisma/compute-cli env update \ + --env ./.env \ + --env API_URL=https://example.com +``` + :::note -No bulk `.env` import yet. Repeat `--env KEY=VALUE` for each variable. +The `.env` file path and comma-separated formats are currently only supported by `@prisma/compute-cli`. With `@looma/prisma-cli`, pass one `KEY=VALUE` per `--env` flag. ::: diff --git a/apps/docs/content/docs/compute/limitations.mdx b/apps/docs/content/docs/compute/limitations.mdx index f580ca0cc6..75d3b9aeee 100644 --- a/apps/docs/content/docs/compute/limitations.mdx +++ b/apps/docs/content/docs/compute/limitations.mdx @@ -20,7 +20,7 @@ Framework-specific requirements: `env update` (compute) and `app update-env` (looma) each cut a new compute version. The old version stays live until the new one is healthy. -No bulk `.env` import yet. Repeat `--env KEY=VALUE` for each variable. +`@looma/prisma-cli` accepts only one `KEY=VALUE` per `--env` flag. `.env` file paths and comma-separated assignments are currently only supported by `@prisma/compute-cli` (see [Environment variables](/compute/environment-variables)). ## Logs From 11cf43235c084f52e4d438adb1eabf5cb696a05a Mon Sep 17 00:00:00 2001 From: ArthurGamby Date: Thu, 23 Apr 2026 16:30:53 +0200 Subject: [PATCH 09/15] docs(compute): split into /compute (official) and /compute-internal (team) Separate the Compute docs into two surfaces so Mike's incoming launch-docs pass has a clean target while preserving the team's experimentation notes. Rationale: from #project-compute on 2026-04-23, Shane confirmed that user-facing docs should promote `prisma-cli` (the future unified CLI) and that `@looma/prisma-cli` / `@prisma/compute-cli` are temporary internal tools, not for users. Prisma Compute public beta launches 2026-05-13; keeping the /compute URL stable now avoids a rename flip on launch day. /compute (new, Official): - Landing page, 5 framework quickstarts, env vars, logs, limitations. - Every command uses `prisma` directly (no looma/compute-cli). - No "EA" language, no badges, no #product-compute references. - Structure/content are a skeleton Mike can refine; examples work today via `alias prisma=prisma-cli` per Shane's workaround. /compute-internal (moved from the previous /compute tree): - All current content preserved verbatim: both CLIs, PR #68 env detail, team channel references, full quickstart flows. - Each page carries a warning Alert linking back to /compute so the scope is always visible. - meta.json title reads "Compute (Internal)". - URLs rewritten from /compute/* to /compute-internal/*. Refs: PTL-1391 --- .../{compute => compute-internal}/cli.mdx | 8 +- .../environment-variables.mdx | 106 ++++++++++++++++++ .../content/docs/compute-internal/index.mdx | 64 +++++++++++ .../docs/compute-internal/limitations.mdx | 36 ++++++ .../content/docs/compute-internal/logs.mdx | 45 ++++++++ .../content/docs/compute-internal/meta.json | 17 +++ .../compute-internal/quickstart/astro.mdx | 82 ++++++++++++++ .../docs/compute-internal/quickstart/bun.mdx | 72 ++++++++++++ .../compute-internal/quickstart/meta.json | 4 + .../compute-internal/quickstart/nextjs.mdx | 71 ++++++++++++ .../docs/compute-internal/quickstart/nuxt.mdx | 62 ++++++++++ .../quickstart/tanstack-start.mdx | 75 +++++++++++++ .../docs/compute/environment-variables.mdx | 87 +------------- apps/docs/content/docs/compute/index.mdx | 38 ++----- .../docs/content/docs/compute/limitations.mdx | 20 +--- apps/docs/content/docs/compute/logs.mdx | 32 +----- apps/docs/content/docs/compute/meta.json | 1 - .../content/docs/compute/quickstart/astro.mdx | 39 ++----- .../content/docs/compute/quickstart/bun.mdx | 33 ++---- .../docs/compute/quickstart/nextjs.mdx | 41 ++----- .../content/docs/compute/quickstart/nuxt.mdx | 35 ++---- .../compute/quickstart/tanstack-start.mdx | 37 ++---- 22 files changed, 714 insertions(+), 291 deletions(-) rename apps/docs/content/docs/{compute => compute-internal}/cli.mdx (92%) create mode 100644 apps/docs/content/docs/compute-internal/environment-variables.mdx create mode 100644 apps/docs/content/docs/compute-internal/index.mdx create mode 100644 apps/docs/content/docs/compute-internal/limitations.mdx create mode 100644 apps/docs/content/docs/compute-internal/logs.mdx create mode 100644 apps/docs/content/docs/compute-internal/meta.json create mode 100644 apps/docs/content/docs/compute-internal/quickstart/astro.mdx create mode 100644 apps/docs/content/docs/compute-internal/quickstart/bun.mdx create mode 100644 apps/docs/content/docs/compute-internal/quickstart/meta.json create mode 100644 apps/docs/content/docs/compute-internal/quickstart/nextjs.mdx create mode 100644 apps/docs/content/docs/compute-internal/quickstart/nuxt.mdx create mode 100644 apps/docs/content/docs/compute-internal/quickstart/tanstack-start.mdx diff --git a/apps/docs/content/docs/compute/cli.mdx b/apps/docs/content/docs/compute-internal/cli.mdx similarity index 92% rename from apps/docs/content/docs/compute/cli.mdx rename to apps/docs/content/docs/compute-internal/cli.mdx index c635a72252..234ce5e716 100644 --- a/apps/docs/content/docs/compute/cli.mdx +++ b/apps/docs/content/docs/compute-internal/cli.mdx @@ -1,10 +1,14 @@ --- title: CLI reference -url: /compute/cli -metaTitle: CLI reference | Prisma Compute +url: /compute-internal/cli +metaTitle: CLI reference | Prisma Compute (Internal) metaDescription: Command inventory for deploying and managing Prisma Compute apps with @looma/prisma-cli or @prisma/compute-cli. --- + + Internal team reference. Not for users. The public docs live at [/compute](/compute). + + Two CLIs are usable today. Pick whichever fits your workflow. Both authenticate the same way and target the same backend. - [`@looma/prisma-cli`](https://www.npmjs.com/package/@looma/prisma-cli): unified `prisma app` surface. diff --git a/apps/docs/content/docs/compute-internal/environment-variables.mdx b/apps/docs/content/docs/compute-internal/environment-variables.mdx new file mode 100644 index 0000000000..56e668d32f --- /dev/null +++ b/apps/docs/content/docs/compute-internal/environment-variables.mdx @@ -0,0 +1,106 @@ +--- +title: Environment variables +url: /compute-internal/environment-variables +metaTitle: Environment variables | Prisma Compute (Internal) +metaDescription: Set environment variables on a Prisma Compute deployment, either inline on deploy or without rebuilding. Supports KEY=VALUE, comma-separated assignments, and dotenv file paths. +--- + + + Internal team reference. Not for users. The public docs live at [/compute](/compute). + + +Set environment variables inline when deploying, or update them later without rebuilding. Either path cuts a new compute version. The old version stays live until the new one is healthy. + +## During a deploy + +Repeat `--env` per variable: + + + + @looma/prisma-cli + @prisma/compute-cli + + + +```bash +npx @looma/prisma-cli app deploy \ + --env DATABASE_URL=postgresql://example \ + --env NODE_ENV=production +``` + + + + +```bash +bunx @prisma/compute-cli deploy \ + --env DATABASE_URL=postgresql://example \ + --env NODE_ENV=production +``` + + + + +## Without rebuilding + +Same flag shape, dedicated command: + + + + @looma/prisma-cli + @prisma/compute-cli + + + +```bash +npx @looma/prisma-cli app update-env --env STRIPE_KEY=sk_live_xxx +npx @looma/prisma-cli app list-env +``` + + + + +```bash +bunx @prisma/compute-cli env update --env STRIPE_KEY=sk_live_xxx +bunx @prisma/compute-cli env update --unset-env LEGACY_FLAG +``` + + + + +## Bulk input with `@prisma/compute-cli` + +`@prisma/compute-cli` accepts three `--env` input formats. They can be combined on the same command and `--env` is repeatable. When a key appears more than once, the later value wins. + +**Load a `.env` file:** + +```bash +bunx @prisma/compute-cli deploy --env ./.env.production +``` + +The file is parsed with standard dotenv rules (comments, `export KEY=VALUE`, quoted values, inline comments). Malformed lines fail fast. + +**Comma-separated assignments in one flag:** + +```bash +bunx @prisma/compute-cli deploy --env FOO=1,BAR=2 +``` + +**Values that contain commas:** wrap the whole assignment in single quotes and the value in double quotes: + +```bash +bunx @prisma/compute-cli deploy --env 'DB_URL="postgres://user:pass@host/db?options=a,b"' +``` + +For complex values (URLs with query params, multi-line secrets), a `.env` file is easier to get right than inline quoting. + +**Mix them:** + +```bash +bunx @prisma/compute-cli env update \ + --env ./.env \ + --env API_URL=https://example.com +``` + +:::note +The `.env` file path and comma-separated formats are currently only supported by `@prisma/compute-cli`. With `@looma/prisma-cli`, pass one `KEY=VALUE` per `--env` flag. +::: diff --git a/apps/docs/content/docs/compute-internal/index.mdx b/apps/docs/content/docs/compute-internal/index.mdx new file mode 100644 index 0000000000..5b5bfc1993 --- /dev/null +++ b/apps/docs/content/docs/compute-internal/index.mdx @@ -0,0 +1,64 @@ +--- +title: Prisma Compute +url: /compute-internal +metaTitle: Prisma Compute (Internal) +metaDescription: Internal one-stop reference for deploying Next.js, Astro, Nuxt, TanStack Start, and Bun apps to Prisma Compute, managing environment variables, and streaming logs. +--- + + + Internal team reference. Not for users. The public docs live at [/compute](/compute). + + +Prisma Compute is app hosting for Node.js and Bun apps, driven from the CLI. First-class support for Next.js, Astro, Nuxt, TanStack Start, and Bun. Deploys are zero-flag on the SDK side: the framework is auto-detected from your `package.json` and config. + +Two CLIs are usable today, pick whichever you prefer: + +- [`@looma/prisma-cli`](https://www.npmjs.com/package/@looma/prisma-cli): unified `prisma app` surface. +- [`@prisma/compute-cli`](https://www.npmjs.com/package/@prisma/compute-cli): original `compute` surface. + +See the full [CLI reference](/compute-internal/cli) for both. + +## Pick a quickstart + +Each quickstart walks you from a fresh app to a live deployment. Pick the one that matches your stack. + + + + Scaffold, enable standalone output, and deploy. + + + Set up the Node adapter in standalone mode and deploy on port 4321. + + + Scaffold and deploy with the default Nitro node-server preset. + + + Deploy the official Vite plus Nitro starter. + + + Deploy a Bun.serve HTTP server directly. + + + +## Manage a deployment + +After the first deploy, use these references day-to-day. + + + + Set secrets and config inline on deploy, or update later without rebuilding. + + + Stream runtime logs per compute version or deployment. + + + Full command inventory for both `@looma/prisma-cli` and `@prisma/compute-cli`. + + + Known caveats around framework support, env updates, and log streaming. + + + +## Support + +Questions or breakage: `#product-compute`. diff --git a/apps/docs/content/docs/compute-internal/limitations.mdx b/apps/docs/content/docs/compute-internal/limitations.mdx new file mode 100644 index 0000000000..431a638dad --- /dev/null +++ b/apps/docs/content/docs/compute-internal/limitations.mdx @@ -0,0 +1,36 @@ +--- +title: Limitations +url: /compute-internal/limitations +metaTitle: Limitations | Prisma Compute (Internal) +metaDescription: Known Prisma Compute limitations covering framework support, env updates, and log streaming. +--- + + + Internal team reference. Not for users. The public docs live at [/compute](/compute). + + +Known caveats. + +## Framework support + +First-class support: **Next.js**, **Astro**, **Nuxt**, **TanStack Start**, and **Bun**. Other Node.js frameworks may build via auto-detection, but are not explicitly tested. + +Framework-specific requirements: + +- **Next.js**: must use `output: "standalone"` in `next.config.ts`. +- **Astro**: needs `@astrojs/node` in standalone mode via the adapter. + +## Environment updates + +`env update` (compute) and `app update-env` (looma) each cut a new compute version. The old version stays live until the new one is healthy. + +`@looma/prisma-cli` accepts only one `KEY=VALUE` per `--env` flag. `.env` file paths and comma-separated assignments are currently only supported by `@prisma/compute-cli` (see [Environment variables](/compute-internal/environment-variables)). + +## Logs + +- Stream caps at around 10 minutes. Reconnect with `--cursor `. +- One concurrent log stream per compute version. + +## Support + +Questions or breakage: `#product-compute`. diff --git a/apps/docs/content/docs/compute-internal/logs.mdx b/apps/docs/content/docs/compute-internal/logs.mdx new file mode 100644 index 0000000000..20fda49cfa --- /dev/null +++ b/apps/docs/content/docs/compute-internal/logs.mdx @@ -0,0 +1,45 @@ +--- +title: Logs +url: /compute-internal/logs +metaTitle: Logs | Prisma Compute (Internal) +metaDescription: Stream runtime logs from a Prisma Compute deployment. +--- + + + Internal team reference. Not for users. The public docs live at [/compute](/compute). + + +Stream logs for a specific compute version or deployment. + +## Stream logs + + + + @prisma/compute-cli + @looma/prisma-cli + + + +```bash +bunx @prisma/compute-cli logs +bunx @prisma/compute-cli logs --tail 200 +bunx @prisma/compute-cli logs --from-start +bunx @prisma/compute-cli logs --cursor +``` + + + + +```bash +npx @looma/prisma-cli app logs +npx @looma/prisma-cli app logs --deployment +npx @looma/prisma-cli app logs --tail 200 +``` + + + + +## Limits + +- Stream caps at around 10 minutes. Reconnect with `--cursor ` to resume from where the last stream ended. +- Only one concurrent log stream per compute version. diff --git a/apps/docs/content/docs/compute-internal/meta.json b/apps/docs/content/docs/compute-internal/meta.json new file mode 100644 index 0000000000..daba0a7aaf --- /dev/null +++ b/apps/docs/content/docs/compute-internal/meta.json @@ -0,0 +1,17 @@ +{ + "title": "Compute (Internal)", + "root": true, + "icon": "Cpu", + "pages": [ + "---Introduction---", + "index", + "---Quickstart---", + "...quickstart", + "---Reference---", + "environment-variables", + "logs", + "cli", + "---More---", + "limitations" + ] +} diff --git a/apps/docs/content/docs/compute-internal/quickstart/astro.mdx b/apps/docs/content/docs/compute-internal/quickstart/astro.mdx new file mode 100644 index 0000000000..d585ae218b --- /dev/null +++ b/apps/docs/content/docs/compute-internal/quickstart/astro.mdx @@ -0,0 +1,82 @@ +--- +title: Astro +url: /compute-internal/quickstart/astro +metaTitle: "Quickstart: Deploy an Astro app to Prisma Compute (Internal)" +metaDescription: Scaffold an Astro app with the Node adapter in standalone mode and deploy it to Prisma Compute. +--- + + + Internal team reference. Not for users. The public docs live at [/compute](/compute). + + +Deploy an Astro app to Prisma Compute using the `@astrojs/node` adapter in standalone mode. Astro serves on port `4321` by default, so the first deploy command sets `--http-port 4321`. + +## Prerequisites + +- Node.js 20+ +- A Prisma account logged in via CLI (covered in step 4) + +## 1. Scaffold the app + +```bash +pnpm create astro@latest my-app +cd my-app +``` + +## 2. Add the Node adapter + +```bash +pnpm add @astrojs/node +``` + +## 3. Enable SSR with the Node adapter + +Edit `astro.config.mjs`: + +```typescript title="astro.config.mjs" +import { defineConfig } from "astro/config"; +import node from "@astrojs/node"; + +export default defineConfig({ + output: "server", + adapter: node({ mode: "standalone" }), +}); +``` + +Compute deploys Astro apps in standalone mode. Without this adapter config, the build does not emit a Node server entry Compute can run. + +## 4. Authenticate and deploy + + + + @looma/prisma-cli + @prisma/compute-cli + + + +```bash +npx @looma/prisma-cli auth login +npx @looma/prisma-cli app deploy --app my-app --http-port 4321 +``` + + + + +```bash +bunx @prisma/compute-cli login +bunx @prisma/compute-cli deploy --service-name my-app --http-port 4321 +``` + + + + +The first deploy bootstraps project context. Re-deploys reuse the saved selection, so `app deploy` (or `deploy`) is enough. + +In CI, set `PRISMA_API_TOKEN` instead of running `auth login`. + +## Next steps + +- [Environment variables](/compute-internal/environment-variables): set secrets and config at deploy time or after. +- [Logs](/compute-internal/logs): stream runtime logs per deployment. +- [CLI reference](/compute-internal/cli): full command inventory for both CLIs. +- [Limitations](/compute-internal/limitations): known caveats. diff --git a/apps/docs/content/docs/compute-internal/quickstart/bun.mdx b/apps/docs/content/docs/compute-internal/quickstart/bun.mdx new file mode 100644 index 0000000000..7778207d9a --- /dev/null +++ b/apps/docs/content/docs/compute-internal/quickstart/bun.mdx @@ -0,0 +1,72 @@ +--- +title: Bun +url: /compute-internal/quickstart/bun +metaTitle: "Quickstart: Deploy a Bun app to Prisma Compute (Internal)" +metaDescription: Scaffold a Bun HTTP server and deploy it to Prisma Compute. +--- + + + Internal team reference. Not for users. The public docs live at [/compute](/compute). + + +Deploy a Bun HTTP server to Prisma Compute. Bun.serve apps are supported directly, no bundler or adapter required. + +## Prerequisites + +- [Bun](https://bun.sh) installed locally +- A Prisma account logged in via CLI (covered in step 3) + +## 1. Initialize the app + +```bash +mkdir my-app && cd my-app && bun init --yes +``` + +## 2. Replace `index.ts` + +```typescript title="index.ts" +Bun.serve({ + port: Number(process.env.PORT ?? 3000), + fetch() { + return new Response("Hello from Compute"); + }, +}); +``` + +Reading `PORT` from the environment keeps the server aligned with Compute's injected port. + +## 3. Authenticate and deploy + + + + @looma/prisma-cli + @prisma/compute-cli + + + +```bash +npx @looma/prisma-cli auth login +npx @looma/prisma-cli app deploy --app my-app --http-port 3000 +``` + + + + +```bash +bunx @prisma/compute-cli login +bunx @prisma/compute-cli deploy --service-name my-app --http-port 3000 +``` + + + + +The first deploy bootstraps project context. Re-deploys reuse the saved selection, so `app deploy` (or `deploy`) is enough. + +In CI, set `PRISMA_API_TOKEN` instead of running `auth login`. + +## Next steps + +- [Environment variables](/compute-internal/environment-variables): set secrets and config at deploy time or after. +- [Logs](/compute-internal/logs): stream runtime logs per deployment. +- [CLI reference](/compute-internal/cli): full command inventory for both CLIs. +- [Limitations](/compute-internal/limitations): known caveats. diff --git a/apps/docs/content/docs/compute-internal/quickstart/meta.json b/apps/docs/content/docs/compute-internal/quickstart/meta.json new file mode 100644 index 0000000000..8f77f50952 --- /dev/null +++ b/apps/docs/content/docs/compute-internal/quickstart/meta.json @@ -0,0 +1,4 @@ +{ + "title": "Quickstart", + "pages": ["nextjs", "astro", "nuxt", "tanstack-start", "bun"] +} diff --git a/apps/docs/content/docs/compute-internal/quickstart/nextjs.mdx b/apps/docs/content/docs/compute-internal/quickstart/nextjs.mdx new file mode 100644 index 0000000000..be268e0fca --- /dev/null +++ b/apps/docs/content/docs/compute-internal/quickstart/nextjs.mdx @@ -0,0 +1,71 @@ +--- +title: Next.js +url: /compute-internal/quickstart/nextjs +metaTitle: "Quickstart: Deploy a Next.js app to Prisma Compute (Internal)" +metaDescription: Scaffold a Next.js app, enable standalone output, and deploy it to Prisma Compute. +--- + + + Internal team reference. Not for users. The public docs live at [/compute](/compute). + + +Deploy a Next.js app to Prisma Compute. This quickstart walks through scaffolding a fresh app, enabling standalone output (required by Compute), and running the first deploy with either `@looma/prisma-cli` or `@prisma/compute-cli`. + +## Prerequisites + +- Node.js 20+ +- A Prisma account logged in via CLI (covered in step 3) + +## 1. Scaffold the app + +```bash +pnpm create next-app@latest my-app --yes +cd my-app +``` + +## 2. Enable standalone output + +Edit `next.config.ts`: + +```typescript title="next.config.ts" +const nextConfig = { output: "standalone" }; +export default nextConfig; +``` + +Compute deploys Next.js apps in standalone mode. Without this flag, the build output does not include the server entry Compute expects. + +## 3. Authenticate and deploy + + + + @looma/prisma-cli + @prisma/compute-cli + + + +```bash +npx @looma/prisma-cli auth login +npx @looma/prisma-cli app deploy --app my-app --http-port 3000 +``` + + + + +```bash +bunx @prisma/compute-cli login +bunx @prisma/compute-cli deploy --service-name my-app --http-port 3000 +``` + + + + +The first deploy bootstraps project context. Re-deploys reuse the saved selection, so `app deploy` (or `deploy`) is enough. + +In CI, set `PRISMA_API_TOKEN` instead of running `auth login`. + +## Next steps + +- [Environment variables](/compute-internal/environment-variables): set secrets and config at deploy time or after. +- [Logs](/compute-internal/logs): stream runtime logs per deployment. +- [CLI reference](/compute-internal/cli): full command inventory for both CLIs. +- [Limitations](/compute-internal/limitations): known caveats. diff --git a/apps/docs/content/docs/compute-internal/quickstart/nuxt.mdx b/apps/docs/content/docs/compute-internal/quickstart/nuxt.mdx new file mode 100644 index 0000000000..60268b5fff --- /dev/null +++ b/apps/docs/content/docs/compute-internal/quickstart/nuxt.mdx @@ -0,0 +1,62 @@ +--- +title: Nuxt +url: /compute-internal/quickstart/nuxt +metaTitle: "Quickstart: Deploy a Nuxt app to Prisma Compute (Internal)" +metaDescription: Scaffold a Nuxt app and deploy it to Prisma Compute. No extra config, Nuxt uses the Nitro node-server preset by default. +--- + + + Internal team reference. Not for users. The public docs live at [/compute](/compute). + + +Deploy a Nuxt app to Prisma Compute. Nuxt builds with the Nitro `node-server` preset by default, so no adapter config is required. + +## Prerequisites + +- Node.js 20+ +- A Prisma account logged in via CLI (covered in step 2) + +## 1. Scaffold the app + +```bash +pnpm create nuxt my-app +cd my-app +``` + +No extra config is needed. The default build output targets Node. + +## 2. Authenticate and deploy + + + + @looma/prisma-cli + @prisma/compute-cli + + + +```bash +npx @looma/prisma-cli auth login +npx @looma/prisma-cli app deploy --app my-app --http-port 3000 +``` + + + + +```bash +bunx @prisma/compute-cli login +bunx @prisma/compute-cli deploy --service-name my-app --http-port 3000 +``` + + + + +The first deploy bootstraps project context. Re-deploys reuse the saved selection, so `app deploy` (or `deploy`) is enough. + +In CI, set `PRISMA_API_TOKEN` instead of running `auth login`. + +## Next steps + +- [Environment variables](/compute-internal/environment-variables): set secrets and config at deploy time or after. +- [Logs](/compute-internal/logs): stream runtime logs per deployment. +- [CLI reference](/compute-internal/cli): full command inventory for both CLIs. +- [Limitations](/compute-internal/limitations): known caveats. diff --git a/apps/docs/content/docs/compute-internal/quickstart/tanstack-start.mdx b/apps/docs/content/docs/compute-internal/quickstart/tanstack-start.mdx new file mode 100644 index 0000000000..d7ddd01718 --- /dev/null +++ b/apps/docs/content/docs/compute-internal/quickstart/tanstack-start.mdx @@ -0,0 +1,75 @@ +--- +title: TanStack Start +url: /compute-internal/quickstart/tanstack-start +metaTitle: "Quickstart: Deploy a TanStack Start app to Prisma Compute (Internal)" +metaDescription: Scaffold a TanStack Start app (Vite + Nitro node preset) and deploy it to Prisma Compute. +--- + + + Internal team reference. Not for users. The public docs live at [/compute](/compute). + + +Deploy a TanStack Start app to Prisma Compute. TanStack Start builds with Vite and the Nitro `node` preset, both already wired in the official starter. + +## Prerequisites + +- Node.js 20+ +- A Prisma account logged in via CLI (covered in step 2) + +## 1. Scaffold the app + +Scaffold from the [official TanStack Start starter](https://tanstack.com/start/latest/docs/framework/react/getting-started) and `cd` into the project. Ensure `vite.config.ts` includes the `tanstackStart()` and `nitro()` plugins, which match the detection the Compute SDK expects. + +Example `vite.config.ts`: + +```typescript title="vite.config.ts" +import { defineConfig } from "vite"; +import { tanstackStart } from "@tanstack/react-start/plugin/vite"; +import viteReact from "@vitejs/plugin-react"; +import { nitro } from "nitro/vite"; + +export default defineConfig({ + server: { port: 3000 }, + plugins: [ + tanstackStart(), + nitro(), + viteReact(), + ], +}); +``` + +## 2. Authenticate and deploy + + + + @looma/prisma-cli + @prisma/compute-cli + + + +```bash +npx @looma/prisma-cli auth login +npx @looma/prisma-cli app deploy --app my-app --http-port 3000 +``` + + + + +```bash +bunx @prisma/compute-cli login +bunx @prisma/compute-cli deploy --service-name my-app --http-port 3000 +``` + + + + +The first deploy bootstraps project context. Re-deploys reuse the saved selection, so `app deploy` (or `deploy`) is enough. + +In CI, set `PRISMA_API_TOKEN` instead of running `auth login`. + +## Next steps + +- [Environment variables](/compute-internal/environment-variables): set secrets and config at deploy time or after. +- [Logs](/compute-internal/logs): stream runtime logs per deployment. +- [CLI reference](/compute-internal/cli): full command inventory for both CLIs. +- [Limitations](/compute-internal/limitations): known caveats. diff --git a/apps/docs/content/docs/compute/environment-variables.mdx b/apps/docs/content/docs/compute/environment-variables.mdx index c31341b67a..488a7348de 100644 --- a/apps/docs/content/docs/compute/environment-variables.mdx +++ b/apps/docs/content/docs/compute/environment-variables.mdx @@ -2,101 +2,26 @@ title: Environment variables url: /compute/environment-variables metaTitle: Environment variables | Prisma Compute -metaDescription: Set environment variables on a Prisma Compute deployment, either inline on deploy or without rebuilding. Supports KEY=VALUE, comma-separated assignments, and dotenv file paths. +metaDescription: Set environment variables on a Prisma Compute deployment, either inline on deploy or without rebuilding. --- -Set environment variables inline when deploying, or update them later without rebuilding. Either path cuts a new compute version. The old version stays live until the new one is healthy. +Set environment variables inline when deploying, or update them later without rebuilding. Either path cuts a new deployment. The old deployment stays live until the new one is healthy. ## During a deploy Repeat `--env` per variable: - - - @looma/prisma-cli - @prisma/compute-cli - - - ```bash -npx @looma/prisma-cli app deploy \ +prisma app deploy \ --env DATABASE_URL=postgresql://example \ --env NODE_ENV=production ``` - - - -```bash -bunx @prisma/compute-cli deploy \ - --env DATABASE_URL=postgresql://example \ - --env NODE_ENV=production -``` - - - - ## Without rebuilding -Same flag shape, dedicated command: - - - - @looma/prisma-cli - @prisma/compute-cli - - +Update environment variables on an existing deployment: ```bash -npx @looma/prisma-cli app update-env --env STRIPE_KEY=sk_live_xxx -npx @looma/prisma-cli app list-env +prisma app update-env --env STRIPE_KEY=sk_live_xxx +prisma app list-env ``` - - - - -```bash -bunx @prisma/compute-cli env update --env STRIPE_KEY=sk_live_xxx -bunx @prisma/compute-cli env update --unset-env LEGACY_FLAG -``` - - - - -## Bulk input with `@prisma/compute-cli` - -`@prisma/compute-cli` accepts three `--env` input formats. They can be combined on the same command and `--env` is repeatable. When a key appears more than once, the later value wins. - -**Load a `.env` file:** - -```bash -bunx @prisma/compute-cli deploy --env ./.env.production -``` - -The file is parsed with standard dotenv rules (comments, `export KEY=VALUE`, quoted values, inline comments). Malformed lines fail fast. - -**Comma-separated assignments in one flag:** - -```bash -bunx @prisma/compute-cli deploy --env FOO=1,BAR=2 -``` - -**Values that contain commas:** wrap the whole assignment in single quotes and the value in double quotes: - -```bash -bunx @prisma/compute-cli deploy --env 'DB_URL="postgres://user:pass@host/db?options=a,b"' -``` - -For complex values (URLs with query params, multi-line secrets), a `.env` file is easier to get right than inline quoting. - -**Mix them:** - -```bash -bunx @prisma/compute-cli env update \ - --env ./.env \ - --env API_URL=https://example.com -``` - -:::note -The `.env` file path and comma-separated formats are currently only supported by `@prisma/compute-cli`. With `@looma/prisma-cli`, pass one `KEY=VALUE` per `--env` flag. -::: diff --git a/apps/docs/content/docs/compute/index.mdx b/apps/docs/content/docs/compute/index.mdx index ea9ee00329..66ee8f0891 100644 --- a/apps/docs/content/docs/compute/index.mdx +++ b/apps/docs/content/docs/compute/index.mdx @@ -2,59 +2,43 @@ title: Prisma Compute url: /compute metaTitle: Prisma Compute -metaDescription: Internal one-stop reference for deploying Next.js, Astro, Nuxt, TanStack Start, and Bun apps to Prisma Compute, managing environment variables, and streaming logs. +metaDescription: Deploy Next.js, Astro, Nuxt, TanStack Start, and Bun apps to Prisma Compute with a single command. --- -Prisma Compute is app hosting for Node.js and Bun apps, driven from the CLI. First-class support for Next.js, Astro, Nuxt, TanStack Start, and Bun. Deploys are zero-flag on the SDK side: the framework is auto-detected from your `package.json` and config. - -Two CLIs are usable today, pick whichever you prefer: - -- [`@looma/prisma-cli`](https://www.npmjs.com/package/@looma/prisma-cli): unified `prisma app` surface. -- [`@prisma/compute-cli`](https://www.npmjs.com/package/@prisma/compute-cli): original `compute` surface. - -See the full [CLI reference](/compute/cli) for both. +Prisma Compute is app hosting for Node.js and Bun apps. Deploy from the command line with a single command. Framework detection is automatic for Next.js, Astro, Nuxt, TanStack Start, and Bun. ## Pick a quickstart -Each quickstart walks you from a fresh app to a live deployment. Pick the one that matches your stack. +Each quickstart walks you from a fresh app to a live deployment. - Scaffold, enable standalone output, and deploy. + Scaffold a Next.js app, enable standalone output, and deploy. - Set up the Node adapter in standalone mode and deploy on port 4321. + Deploy an Astro app with the Node adapter in standalone mode. - Scaffold and deploy with the default Nitro node-server preset. + Deploy a Nuxt app with the default Nitro node-server preset. - Deploy the official Vite plus Nitro starter. + Deploy a TanStack Start app built with Vite and Nitro. - Deploy a Bun.serve HTTP server directly. + Deploy a Bun HTTP server directly. ## Manage a deployment -After the first deploy, use these references day-to-day. - - Set secrets and config inline on deploy, or update later without rebuilding. + Set secrets and configuration inline on deploy, or update later without rebuilding. - Stream runtime logs per compute version or deployment. - - - Full command inventory for both `@looma/prisma-cli` and `@prisma/compute-cli`. + Stream runtime logs per deployment. - Known caveats around framework support, env updates, and log streaming. + Known caveats around framework support, environment updates, and log streaming. - -## Support - -Questions or breakage: `#product-compute`. diff --git a/apps/docs/content/docs/compute/limitations.mdx b/apps/docs/content/docs/compute/limitations.mdx index 75d3b9aeee..60ed54d5da 100644 --- a/apps/docs/content/docs/compute/limitations.mdx +++ b/apps/docs/content/docs/compute/limitations.mdx @@ -2,31 +2,23 @@ title: Limitations url: /compute/limitations metaTitle: Limitations | Prisma Compute -metaDescription: Known Prisma Compute limitations covering framework support, env updates, and log streaming. +metaDescription: Known Prisma Compute limitations covering framework support, environment updates, and log streaming. --- -Known caveats. - ## Framework support -First-class support: **Next.js**, **Astro**, **Nuxt**, **TanStack Start**, and **Bun**. Other Node.js frameworks may build via auto-detection, but are not explicitly tested. +First-class support: **Next.js**, **Astro**, **Nuxt**, **TanStack Start**, and **Bun**. Other Node.js frameworks may build via auto-detection but are not explicitly tested. Framework-specific requirements: - **Next.js**: must use `output: "standalone"` in `next.config.ts`. -- **Astro**: needs `@astrojs/node` in standalone mode via the adapter. +- **Astro**: needs `@astrojs/node` in standalone mode. ## Environment updates -`env update` (compute) and `app update-env` (looma) each cut a new compute version. The old version stays live until the new one is healthy. - -`@looma/prisma-cli` accepts only one `KEY=VALUE` per `--env` flag. `.env` file paths and comma-separated assignments are currently only supported by `@prisma/compute-cli` (see [Environment variables](/compute/environment-variables)). +Updating environment variables cuts a new deployment. The old deployment stays live until the new one is healthy. ## Logs -- Stream caps at around 10 minutes. Reconnect with `--cursor `. -- One concurrent log stream per compute version. - -## Support - -Questions or breakage: `#product-compute`. +- Stream caps at around 10 minutes. +- One concurrent log stream per deployment. diff --git a/apps/docs/content/docs/compute/logs.mdx b/apps/docs/content/docs/compute/logs.mdx index 0cea9be119..3892532644 100644 --- a/apps/docs/content/docs/compute/logs.mdx +++ b/apps/docs/content/docs/compute/logs.mdx @@ -5,37 +5,17 @@ metaTitle: Logs | Prisma Compute metaDescription: Stream runtime logs from a Prisma Compute deployment. --- -Stream logs for a specific compute version or deployment. +Stream runtime logs for your deployment. ## Stream logs - - - @prisma/compute-cli - @looma/prisma-cli - - - -```bash -bunx @prisma/compute-cli logs -bunx @prisma/compute-cli logs --tail 200 -bunx @prisma/compute-cli logs --from-start -bunx @prisma/compute-cli logs --cursor -``` - - - - ```bash -npx @looma/prisma-cli app logs -npx @looma/prisma-cli app logs --deployment -npx @looma/prisma-cli app logs --tail 200 +prisma app logs +prisma app logs --deployment +prisma app logs --tail 200 ``` - - - ## Limits -- Stream caps at around 10 minutes. Reconnect with `--cursor ` to resume from where the last stream ended. -- Only one concurrent log stream per compute version. +- Stream caps at around 10 minutes. Reconnect to resume. +- One concurrent log stream per deployment. diff --git a/apps/docs/content/docs/compute/meta.json b/apps/docs/content/docs/compute/meta.json index 450fa47106..9a02c18928 100644 --- a/apps/docs/content/docs/compute/meta.json +++ b/apps/docs/content/docs/compute/meta.json @@ -10,7 +10,6 @@ "---Reference---", "environment-variables", "logs", - "cli", "---More---", "limitations" ] diff --git a/apps/docs/content/docs/compute/quickstart/astro.mdx b/apps/docs/content/docs/compute/quickstart/astro.mdx index 83627f7d69..2572224b52 100644 --- a/apps/docs/content/docs/compute/quickstart/astro.mdx +++ b/apps/docs/content/docs/compute/quickstart/astro.mdx @@ -5,12 +5,12 @@ metaTitle: "Quickstart: Deploy an Astro app to Prisma Compute" metaDescription: Scaffold an Astro app with the Node adapter in standalone mode and deploy it to Prisma Compute. --- -Deploy an Astro app to Prisma Compute using the `@astrojs/node` adapter in standalone mode. Astro serves on port `4321` by default, so the first deploy command sets `--http-port 4321`. +Deploy an Astro app to Prisma Compute using the `@astrojs/node` adapter in standalone mode. Astro serves on port `4321` by default. ## Prerequisites -- Node.js 20+ -- A Prisma account logged in via CLI (covered in step 4) +- Node.js 20 or later +- A Prisma account ## 1. Scaffold the app @@ -39,40 +39,21 @@ export default defineConfig({ }); ``` -Compute deploys Astro apps in standalone mode. Without this adapter config, the build does not emit a Node server entry Compute can run. +Compute runs Astro apps from the standalone Node build. Without this adapter config, the build does not emit a server entry Compute can run. ## 4. Authenticate and deploy - - - @looma/prisma-cli - @prisma/compute-cli - - - -```bash -npx @looma/prisma-cli auth login -npx @looma/prisma-cli app deploy --app my-app --http-port 4321 -``` - - - - ```bash -bunx @prisma/compute-cli login -bunx @prisma/compute-cli deploy --service-name my-app --http-port 4321 +prisma auth login +prisma app deploy --app my-app --http-port 4321 ``` - - - -The first deploy bootstraps project context. Re-deploys reuse the saved selection, so `app deploy` (or `deploy`) is enough. +The first deploy bootstraps project context. Re-deploys reuse the saved selection, so `prisma app deploy` is enough. -In CI, set `PRISMA_API_TOKEN` instead of running `auth login`. +In CI, set `PRISMA_API_TOKEN` instead of running `prisma auth login`. ## Next steps -- [Environment variables](/compute/environment-variables): set secrets and config at deploy time or after. -- [Logs](/compute/logs): stream runtime logs per deployment. -- [CLI reference](/compute/cli): full command inventory for both CLIs. +- [Environment variables](/compute/environment-variables): set secrets and configuration at deploy time or after. +- [Logs](/compute/logs): stream runtime logs. - [Limitations](/compute/limitations): known caveats. diff --git a/apps/docs/content/docs/compute/quickstart/bun.mdx b/apps/docs/content/docs/compute/quickstart/bun.mdx index 46fe430365..7836857379 100644 --- a/apps/docs/content/docs/compute/quickstart/bun.mdx +++ b/apps/docs/content/docs/compute/quickstart/bun.mdx @@ -10,7 +10,7 @@ Deploy a Bun HTTP server to Prisma Compute. Bun.serve apps are supported directl ## Prerequisites - [Bun](https://bun.sh) installed locally -- A Prisma account logged in via CLI (covered in step 3) +- A Prisma account ## 1. Initialize the app @@ -33,36 +33,17 @@ Reading `PORT` from the environment keeps the server aligned with Compute's inje ## 3. Authenticate and deploy - - - @looma/prisma-cli - @prisma/compute-cli - - - -```bash -npx @looma/prisma-cli auth login -npx @looma/prisma-cli app deploy --app my-app --http-port 3000 -``` - - - - ```bash -bunx @prisma/compute-cli login -bunx @prisma/compute-cli deploy --service-name my-app --http-port 3000 +prisma auth login +prisma app deploy --app my-app --http-port 3000 ``` - - - -The first deploy bootstraps project context. Re-deploys reuse the saved selection, so `app deploy` (or `deploy`) is enough. +The first deploy bootstraps project context. Re-deploys reuse the saved selection, so `prisma app deploy` is enough. -In CI, set `PRISMA_API_TOKEN` instead of running `auth login`. +In CI, set `PRISMA_API_TOKEN` instead of running `prisma auth login`. ## Next steps -- [Environment variables](/compute/environment-variables): set secrets and config at deploy time or after. -- [Logs](/compute/logs): stream runtime logs per deployment. -- [CLI reference](/compute/cli): full command inventory for both CLIs. +- [Environment variables](/compute/environment-variables): set secrets and configuration at deploy time or after. +- [Logs](/compute/logs): stream runtime logs. - [Limitations](/compute/limitations): known caveats. diff --git a/apps/docs/content/docs/compute/quickstart/nextjs.mdx b/apps/docs/content/docs/compute/quickstart/nextjs.mdx index 4f24d1e04b..752e6aaa08 100644 --- a/apps/docs/content/docs/compute/quickstart/nextjs.mdx +++ b/apps/docs/content/docs/compute/quickstart/nextjs.mdx @@ -2,15 +2,15 @@ title: Next.js url: /compute/quickstart/nextjs metaTitle: "Quickstart: Deploy a Next.js app to Prisma Compute" -metaDescription: Scaffold a Next.js app, enable standalone output, and deploy it to Prisma Compute. +metaDescription: Scaffold a Next.js app, enable standalone output, and deploy it to Prisma Compute with a single command. --- -Deploy a Next.js app to Prisma Compute. This quickstart walks through scaffolding a fresh app, enabling standalone output (required by Compute), and running the first deploy with either `@looma/prisma-cli` or `@prisma/compute-cli`. +Deploy a Next.js app to Prisma Compute. This quickstart covers scaffolding a fresh app, enabling the standalone build output Compute requires, and running the first deploy. ## Prerequisites -- Node.js 20+ -- A Prisma account logged in via CLI (covered in step 3) +- Node.js 20 or later +- A Prisma account ## 1. Scaffold the app @@ -28,40 +28,21 @@ const nextConfig = { output: "standalone" }; export default nextConfig; ``` -Compute deploys Next.js apps in standalone mode. Without this flag, the build output does not include the server entry Compute expects. +Compute deploys Next.js apps from the standalone build. Without this flag, the build output does not include the server entry Compute expects. ## 3. Authenticate and deploy - - - @looma/prisma-cli - @prisma/compute-cli - - - -```bash -npx @looma/prisma-cli auth login -npx @looma/prisma-cli app deploy --app my-app --http-port 3000 -``` - - - - ```bash -bunx @prisma/compute-cli login -bunx @prisma/compute-cli deploy --service-name my-app --http-port 3000 +prisma auth login +prisma app deploy --app my-app --http-port 3000 ``` - - - -The first deploy bootstraps project context. Re-deploys reuse the saved selection, so `app deploy` (or `deploy`) is enough. +The first deploy bootstraps project context. Re-deploys reuse the saved selection, so `prisma app deploy` is enough. -In CI, set `PRISMA_API_TOKEN` instead of running `auth login`. +In CI, set `PRISMA_API_TOKEN` instead of running `prisma auth login`. ## Next steps -- [Environment variables](/compute/environment-variables): set secrets and config at deploy time or after. -- [Logs](/compute/logs): stream runtime logs per deployment. -- [CLI reference](/compute/cli): full command inventory for both CLIs. +- [Environment variables](/compute/environment-variables): set secrets and configuration at deploy time or after. +- [Logs](/compute/logs): stream runtime logs. - [Limitations](/compute/limitations): known caveats. diff --git a/apps/docs/content/docs/compute/quickstart/nuxt.mdx b/apps/docs/content/docs/compute/quickstart/nuxt.mdx index 6532ae1323..c1c7ea825e 100644 --- a/apps/docs/content/docs/compute/quickstart/nuxt.mdx +++ b/apps/docs/content/docs/compute/quickstart/nuxt.mdx @@ -9,8 +9,8 @@ Deploy a Nuxt app to Prisma Compute. Nuxt builds with the Nitro `node-server` pr ## Prerequisites -- Node.js 20+ -- A Prisma account logged in via CLI (covered in step 2) +- Node.js 20 or later +- A Prisma account ## 1. Scaffold the app @@ -23,36 +23,17 @@ No extra config is needed. The default build output targets Node. ## 2. Authenticate and deploy - - - @looma/prisma-cli - @prisma/compute-cli - - - -```bash -npx @looma/prisma-cli auth login -npx @looma/prisma-cli app deploy --app my-app --http-port 3000 -``` - - - - ```bash -bunx @prisma/compute-cli login -bunx @prisma/compute-cli deploy --service-name my-app --http-port 3000 +prisma auth login +prisma app deploy --app my-app --http-port 3000 ``` - - - -The first deploy bootstraps project context. Re-deploys reuse the saved selection, so `app deploy` (or `deploy`) is enough. +The first deploy bootstraps project context. Re-deploys reuse the saved selection, so `prisma app deploy` is enough. -In CI, set `PRISMA_API_TOKEN` instead of running `auth login`. +In CI, set `PRISMA_API_TOKEN` instead of running `prisma auth login`. ## Next steps -- [Environment variables](/compute/environment-variables): set secrets and config at deploy time or after. -- [Logs](/compute/logs): stream runtime logs per deployment. -- [CLI reference](/compute/cli): full command inventory for both CLIs. +- [Environment variables](/compute/environment-variables): set secrets and configuration at deploy time or after. +- [Logs](/compute/logs): stream runtime logs. - [Limitations](/compute/limitations): known caveats. diff --git a/apps/docs/content/docs/compute/quickstart/tanstack-start.mdx b/apps/docs/content/docs/compute/quickstart/tanstack-start.mdx index 0089097177..526ddca2c6 100644 --- a/apps/docs/content/docs/compute/quickstart/tanstack-start.mdx +++ b/apps/docs/content/docs/compute/quickstart/tanstack-start.mdx @@ -9,12 +9,12 @@ Deploy a TanStack Start app to Prisma Compute. TanStack Start builds with Vite a ## Prerequisites -- Node.js 20+ -- A Prisma account logged in via CLI (covered in step 2) +- Node.js 20 or later +- A Prisma account ## 1. Scaffold the app -Scaffold from the [official TanStack Start starter](https://tanstack.com/start/latest/docs/framework/react/getting-started) and `cd` into the project. Ensure `vite.config.ts` includes the `tanstackStart()` and `nitro()` plugins, which match the detection the Compute SDK expects. +Scaffold from the [official TanStack Start starter](https://tanstack.com/start/latest/docs/framework/react/getting-started) and `cd` into the project. Ensure `vite.config.ts` includes the `tanstackStart()` and `nitro()` plugins. Example `vite.config.ts`: @@ -36,36 +36,17 @@ export default defineConfig({ ## 2. Authenticate and deploy - - - @looma/prisma-cli - @prisma/compute-cli - - - -```bash -npx @looma/prisma-cli auth login -npx @looma/prisma-cli app deploy --app my-app --http-port 3000 -``` - - - - ```bash -bunx @prisma/compute-cli login -bunx @prisma/compute-cli deploy --service-name my-app --http-port 3000 +prisma auth login +prisma app deploy --app my-app --http-port 3000 ``` - - - -The first deploy bootstraps project context. Re-deploys reuse the saved selection, so `app deploy` (or `deploy`) is enough. +The first deploy bootstraps project context. Re-deploys reuse the saved selection, so `prisma app deploy` is enough. -In CI, set `PRISMA_API_TOKEN` instead of running `auth login`. +In CI, set `PRISMA_API_TOKEN` instead of running `prisma auth login`. ## Next steps -- [Environment variables](/compute/environment-variables): set secrets and config at deploy time or after. -- [Logs](/compute/logs): stream runtime logs per deployment. -- [CLI reference](/compute/cli): full command inventory for both CLIs. +- [Environment variables](/compute/environment-variables): set secrets and configuration at deploy time or after. +- [Logs](/compute/logs): stream runtime logs. - [Limitations](/compute/limitations): known caveats. From 9a43b7af212e5bae574f9cf400135e71de9644fa Mon Sep 17 00:00:00 2001 From: ArthurGamby Date: Thu, 23 Apr 2026 16:35:56 +0200 Subject: [PATCH 10/15] docs(compute): add Compute (Internal) top-level navbar item Wire /compute-internal into the v7 top navbar as a sibling of Compute. Extend the warning Alert on every internal page to state the section will be removed after the public beta launch on 2026-05-13. This branch is intentionally not merged to main; the nav entry exists so the team can access the internal reference on preview deploys during the run-up to launch. --- apps/docs/content/docs/compute-internal/cli.mdx | 2 +- .../content/docs/compute-internal/environment-variables.mdx | 2 +- apps/docs/content/docs/compute-internal/index.mdx | 2 +- apps/docs/content/docs/compute-internal/limitations.mdx | 2 +- apps/docs/content/docs/compute-internal/logs.mdx | 2 +- apps/docs/content/docs/compute-internal/quickstart/astro.mdx | 2 +- apps/docs/content/docs/compute-internal/quickstart/bun.mdx | 2 +- .../docs/content/docs/compute-internal/quickstart/nextjs.mdx | 2 +- apps/docs/content/docs/compute-internal/quickstart/nuxt.mdx | 2 +- .../docs/compute-internal/quickstart/tanstack-start.mdx | 2 +- apps/docs/src/lib/layout.shared.tsx | 5 +++++ 11 files changed, 15 insertions(+), 10 deletions(-) diff --git a/apps/docs/content/docs/compute-internal/cli.mdx b/apps/docs/content/docs/compute-internal/cli.mdx index 234ce5e716..5e3328abaf 100644 --- a/apps/docs/content/docs/compute-internal/cli.mdx +++ b/apps/docs/content/docs/compute-internal/cli.mdx @@ -6,7 +6,7 @@ metaDescription: Command inventory for deploying and managing Prisma Compute app --- - Internal team reference. Not for users. The public docs live at [/compute](/compute). + Internal team reference. Not for users. This section will be removed after the public beta launch on 2026-05-13. The public docs live at [/compute](/compute). Two CLIs are usable today. Pick whichever fits your workflow. Both authenticate the same way and target the same backend. diff --git a/apps/docs/content/docs/compute-internal/environment-variables.mdx b/apps/docs/content/docs/compute-internal/environment-variables.mdx index 56e668d32f..7dd85fae51 100644 --- a/apps/docs/content/docs/compute-internal/environment-variables.mdx +++ b/apps/docs/content/docs/compute-internal/environment-variables.mdx @@ -6,7 +6,7 @@ metaDescription: Set environment variables on a Prisma Compute deployment, eithe --- - Internal team reference. Not for users. The public docs live at [/compute](/compute). + Internal team reference. Not for users. This section will be removed after the public beta launch on 2026-05-13. The public docs live at [/compute](/compute). Set environment variables inline when deploying, or update them later without rebuilding. Either path cuts a new compute version. The old version stays live until the new one is healthy. diff --git a/apps/docs/content/docs/compute-internal/index.mdx b/apps/docs/content/docs/compute-internal/index.mdx index 5b5bfc1993..1d0a8b9f6c 100644 --- a/apps/docs/content/docs/compute-internal/index.mdx +++ b/apps/docs/content/docs/compute-internal/index.mdx @@ -6,7 +6,7 @@ metaDescription: Internal one-stop reference for deploying Next.js, Astro, Nuxt, --- - Internal team reference. Not for users. The public docs live at [/compute](/compute). + Internal team reference. Not for users. This section will be removed after the public beta launch on 2026-05-13. The public docs live at [/compute](/compute). Prisma Compute is app hosting for Node.js and Bun apps, driven from the CLI. First-class support for Next.js, Astro, Nuxt, TanStack Start, and Bun. Deploys are zero-flag on the SDK side: the framework is auto-detected from your `package.json` and config. diff --git a/apps/docs/content/docs/compute-internal/limitations.mdx b/apps/docs/content/docs/compute-internal/limitations.mdx index 431a638dad..99690ef55f 100644 --- a/apps/docs/content/docs/compute-internal/limitations.mdx +++ b/apps/docs/content/docs/compute-internal/limitations.mdx @@ -6,7 +6,7 @@ metaDescription: Known Prisma Compute limitations covering framework support, en --- - Internal team reference. Not for users. The public docs live at [/compute](/compute). + Internal team reference. Not for users. This section will be removed after the public beta launch on 2026-05-13. The public docs live at [/compute](/compute). Known caveats. diff --git a/apps/docs/content/docs/compute-internal/logs.mdx b/apps/docs/content/docs/compute-internal/logs.mdx index 20fda49cfa..3bcadc80fd 100644 --- a/apps/docs/content/docs/compute-internal/logs.mdx +++ b/apps/docs/content/docs/compute-internal/logs.mdx @@ -6,7 +6,7 @@ metaDescription: Stream runtime logs from a Prisma Compute deployment. --- - Internal team reference. Not for users. The public docs live at [/compute](/compute). + Internal team reference. Not for users. This section will be removed after the public beta launch on 2026-05-13. The public docs live at [/compute](/compute). Stream logs for a specific compute version or deployment. diff --git a/apps/docs/content/docs/compute-internal/quickstart/astro.mdx b/apps/docs/content/docs/compute-internal/quickstart/astro.mdx index d585ae218b..735d7f031a 100644 --- a/apps/docs/content/docs/compute-internal/quickstart/astro.mdx +++ b/apps/docs/content/docs/compute-internal/quickstart/astro.mdx @@ -6,7 +6,7 @@ metaDescription: Scaffold an Astro app with the Node adapter in standalone mode --- - Internal team reference. Not for users. The public docs live at [/compute](/compute). + Internal team reference. Not for users. This section will be removed after the public beta launch on 2026-05-13. The public docs live at [/compute](/compute). Deploy an Astro app to Prisma Compute using the `@astrojs/node` adapter in standalone mode. Astro serves on port `4321` by default, so the first deploy command sets `--http-port 4321`. diff --git a/apps/docs/content/docs/compute-internal/quickstart/bun.mdx b/apps/docs/content/docs/compute-internal/quickstart/bun.mdx index 7778207d9a..8bb49e4e96 100644 --- a/apps/docs/content/docs/compute-internal/quickstart/bun.mdx +++ b/apps/docs/content/docs/compute-internal/quickstart/bun.mdx @@ -6,7 +6,7 @@ metaDescription: Scaffold a Bun HTTP server and deploy it to Prisma Compute. --- - Internal team reference. Not for users. The public docs live at [/compute](/compute). + Internal team reference. Not for users. This section will be removed after the public beta launch on 2026-05-13. The public docs live at [/compute](/compute). Deploy a Bun HTTP server to Prisma Compute. Bun.serve apps are supported directly, no bundler or adapter required. diff --git a/apps/docs/content/docs/compute-internal/quickstart/nextjs.mdx b/apps/docs/content/docs/compute-internal/quickstart/nextjs.mdx index be268e0fca..069e132ee4 100644 --- a/apps/docs/content/docs/compute-internal/quickstart/nextjs.mdx +++ b/apps/docs/content/docs/compute-internal/quickstart/nextjs.mdx @@ -6,7 +6,7 @@ metaDescription: Scaffold a Next.js app, enable standalone output, and deploy it --- - Internal team reference. Not for users. The public docs live at [/compute](/compute). + Internal team reference. Not for users. This section will be removed after the public beta launch on 2026-05-13. The public docs live at [/compute](/compute). Deploy a Next.js app to Prisma Compute. This quickstart walks through scaffolding a fresh app, enabling standalone output (required by Compute), and running the first deploy with either `@looma/prisma-cli` or `@prisma/compute-cli`. diff --git a/apps/docs/content/docs/compute-internal/quickstart/nuxt.mdx b/apps/docs/content/docs/compute-internal/quickstart/nuxt.mdx index 60268b5fff..207eee6698 100644 --- a/apps/docs/content/docs/compute-internal/quickstart/nuxt.mdx +++ b/apps/docs/content/docs/compute-internal/quickstart/nuxt.mdx @@ -6,7 +6,7 @@ metaDescription: Scaffold a Nuxt app and deploy it to Prisma Compute. No extra c --- - Internal team reference. Not for users. The public docs live at [/compute](/compute). + Internal team reference. Not for users. This section will be removed after the public beta launch on 2026-05-13. The public docs live at [/compute](/compute). Deploy a Nuxt app to Prisma Compute. Nuxt builds with the Nitro `node-server` preset by default, so no adapter config is required. diff --git a/apps/docs/content/docs/compute-internal/quickstart/tanstack-start.mdx b/apps/docs/content/docs/compute-internal/quickstart/tanstack-start.mdx index d7ddd01718..c47263cb9e 100644 --- a/apps/docs/content/docs/compute-internal/quickstart/tanstack-start.mdx +++ b/apps/docs/content/docs/compute-internal/quickstart/tanstack-start.mdx @@ -6,7 +6,7 @@ metaDescription: Scaffold a TanStack Start app (Vite + Nitro node preset) and de --- - Internal team reference. Not for users. The public docs live at [/compute](/compute). + Internal team reference. Not for users. This section will be removed after the public beta launch on 2026-05-13. The public docs live at [/compute](/compute). Deploy a TanStack Start app to Prisma Compute. TanStack Start builds with Vite and the Nitro `node` preset, both already wired in the official starter. diff --git a/apps/docs/src/lib/layout.shared.tsx b/apps/docs/src/lib/layout.shared.tsx index f0884dfadb..82b38d57f7 100644 --- a/apps/docs/src/lib/layout.shared.tsx +++ b/apps/docs/src/lib/layout.shared.tsx @@ -38,6 +38,11 @@ export const links: LinkItemTypeWithActivePaths[] = [ url: "/compute", active: "nested-url", }, + { + text: "Compute (Internal)", + url: "/compute-internal", + active: "nested-url", + }, { text: "CLI", url: "/cli", From 7d02f2ec04f3eeab00f1ac4f8f465f42d4215957 Mon Sep 17 00:00:00 2001 From: ArthurGamby Date: Thu, 23 Apr 2026 16:38:11 +0200 Subject: [PATCH 11/15] fix(docs): swap Alert JSX for :::warning directive in compute-internal is not registered as a bare MDX component in mdx-components.tsx (only the ::: directive path maps to it via CalloutContainer), so direct JSX usage threw a missing-reference runtime error. --- apps/docs/content/docs/compute-internal/cli.mdx | 6 +++--- .../content/docs/compute-internal/environment-variables.mdx | 6 +++--- apps/docs/content/docs/compute-internal/index.mdx | 6 +++--- apps/docs/content/docs/compute-internal/limitations.mdx | 6 +++--- apps/docs/content/docs/compute-internal/logs.mdx | 6 +++--- .../docs/content/docs/compute-internal/quickstart/astro.mdx | 6 +++--- apps/docs/content/docs/compute-internal/quickstart/bun.mdx | 6 +++--- .../content/docs/compute-internal/quickstart/nextjs.mdx | 6 +++--- apps/docs/content/docs/compute-internal/quickstart/nuxt.mdx | 6 +++--- .../docs/compute-internal/quickstart/tanstack-start.mdx | 6 +++--- 10 files changed, 30 insertions(+), 30 deletions(-) diff --git a/apps/docs/content/docs/compute-internal/cli.mdx b/apps/docs/content/docs/compute-internal/cli.mdx index 5e3328abaf..b9585769ec 100644 --- a/apps/docs/content/docs/compute-internal/cli.mdx +++ b/apps/docs/content/docs/compute-internal/cli.mdx @@ -5,9 +5,9 @@ metaTitle: CLI reference | Prisma Compute (Internal) metaDescription: Command inventory for deploying and managing Prisma Compute apps with @looma/prisma-cli or @prisma/compute-cli. --- - - Internal team reference. Not for users. This section will be removed after the public beta launch on 2026-05-13. The public docs live at [/compute](/compute). - +:::warning +Internal team reference. Not for users. This section will be removed after the public beta launch on 2026-05-13. The public docs live at [/compute](/compute). +::: Two CLIs are usable today. Pick whichever fits your workflow. Both authenticate the same way and target the same backend. diff --git a/apps/docs/content/docs/compute-internal/environment-variables.mdx b/apps/docs/content/docs/compute-internal/environment-variables.mdx index 7dd85fae51..5eda27c116 100644 --- a/apps/docs/content/docs/compute-internal/environment-variables.mdx +++ b/apps/docs/content/docs/compute-internal/environment-variables.mdx @@ -5,9 +5,9 @@ metaTitle: Environment variables | Prisma Compute (Internal) metaDescription: Set environment variables on a Prisma Compute deployment, either inline on deploy or without rebuilding. Supports KEY=VALUE, comma-separated assignments, and dotenv file paths. --- - - Internal team reference. Not for users. This section will be removed after the public beta launch on 2026-05-13. The public docs live at [/compute](/compute). - +:::warning +Internal team reference. Not for users. This section will be removed after the public beta launch on 2026-05-13. The public docs live at [/compute](/compute). +::: Set environment variables inline when deploying, or update them later without rebuilding. Either path cuts a new compute version. The old version stays live until the new one is healthy. diff --git a/apps/docs/content/docs/compute-internal/index.mdx b/apps/docs/content/docs/compute-internal/index.mdx index 1d0a8b9f6c..ce2c4fd438 100644 --- a/apps/docs/content/docs/compute-internal/index.mdx +++ b/apps/docs/content/docs/compute-internal/index.mdx @@ -5,9 +5,9 @@ metaTitle: Prisma Compute (Internal) metaDescription: Internal one-stop reference for deploying Next.js, Astro, Nuxt, TanStack Start, and Bun apps to Prisma Compute, managing environment variables, and streaming logs. --- - - Internal team reference. Not for users. This section will be removed after the public beta launch on 2026-05-13. The public docs live at [/compute](/compute). - +:::warning +Internal team reference. Not for users. This section will be removed after the public beta launch on 2026-05-13. The public docs live at [/compute](/compute). +::: Prisma Compute is app hosting for Node.js and Bun apps, driven from the CLI. First-class support for Next.js, Astro, Nuxt, TanStack Start, and Bun. Deploys are zero-flag on the SDK side: the framework is auto-detected from your `package.json` and config. diff --git a/apps/docs/content/docs/compute-internal/limitations.mdx b/apps/docs/content/docs/compute-internal/limitations.mdx index 99690ef55f..8bd6f4ebfa 100644 --- a/apps/docs/content/docs/compute-internal/limitations.mdx +++ b/apps/docs/content/docs/compute-internal/limitations.mdx @@ -5,9 +5,9 @@ metaTitle: Limitations | Prisma Compute (Internal) metaDescription: Known Prisma Compute limitations covering framework support, env updates, and log streaming. --- - - Internal team reference. Not for users. This section will be removed after the public beta launch on 2026-05-13. The public docs live at [/compute](/compute). - +:::warning +Internal team reference. Not for users. This section will be removed after the public beta launch on 2026-05-13. The public docs live at [/compute](/compute). +::: Known caveats. diff --git a/apps/docs/content/docs/compute-internal/logs.mdx b/apps/docs/content/docs/compute-internal/logs.mdx index 3bcadc80fd..33e443ac36 100644 --- a/apps/docs/content/docs/compute-internal/logs.mdx +++ b/apps/docs/content/docs/compute-internal/logs.mdx @@ -5,9 +5,9 @@ metaTitle: Logs | Prisma Compute (Internal) metaDescription: Stream runtime logs from a Prisma Compute deployment. --- - - Internal team reference. Not for users. This section will be removed after the public beta launch on 2026-05-13. The public docs live at [/compute](/compute). - +:::warning +Internal team reference. Not for users. This section will be removed after the public beta launch on 2026-05-13. The public docs live at [/compute](/compute). +::: Stream logs for a specific compute version or deployment. diff --git a/apps/docs/content/docs/compute-internal/quickstart/astro.mdx b/apps/docs/content/docs/compute-internal/quickstart/astro.mdx index 735d7f031a..6228ec7088 100644 --- a/apps/docs/content/docs/compute-internal/quickstart/astro.mdx +++ b/apps/docs/content/docs/compute-internal/quickstart/astro.mdx @@ -5,9 +5,9 @@ metaTitle: "Quickstart: Deploy an Astro app to Prisma Compute (Internal)" metaDescription: Scaffold an Astro app with the Node adapter in standalone mode and deploy it to Prisma Compute. --- - - Internal team reference. Not for users. This section will be removed after the public beta launch on 2026-05-13. The public docs live at [/compute](/compute). - +:::warning +Internal team reference. Not for users. This section will be removed after the public beta launch on 2026-05-13. The public docs live at [/compute](/compute). +::: Deploy an Astro app to Prisma Compute using the `@astrojs/node` adapter in standalone mode. Astro serves on port `4321` by default, so the first deploy command sets `--http-port 4321`. diff --git a/apps/docs/content/docs/compute-internal/quickstart/bun.mdx b/apps/docs/content/docs/compute-internal/quickstart/bun.mdx index 8bb49e4e96..3381f0115f 100644 --- a/apps/docs/content/docs/compute-internal/quickstart/bun.mdx +++ b/apps/docs/content/docs/compute-internal/quickstart/bun.mdx @@ -5,9 +5,9 @@ metaTitle: "Quickstart: Deploy a Bun app to Prisma Compute (Internal)" metaDescription: Scaffold a Bun HTTP server and deploy it to Prisma Compute. --- - - Internal team reference. Not for users. This section will be removed after the public beta launch on 2026-05-13. The public docs live at [/compute](/compute). - +:::warning +Internal team reference. Not for users. This section will be removed after the public beta launch on 2026-05-13. The public docs live at [/compute](/compute). +::: Deploy a Bun HTTP server to Prisma Compute. Bun.serve apps are supported directly, no bundler or adapter required. diff --git a/apps/docs/content/docs/compute-internal/quickstart/nextjs.mdx b/apps/docs/content/docs/compute-internal/quickstart/nextjs.mdx index 069e132ee4..acc323a48d 100644 --- a/apps/docs/content/docs/compute-internal/quickstart/nextjs.mdx +++ b/apps/docs/content/docs/compute-internal/quickstart/nextjs.mdx @@ -5,9 +5,9 @@ metaTitle: "Quickstart: Deploy a Next.js app to Prisma Compute (Internal)" metaDescription: Scaffold a Next.js app, enable standalone output, and deploy it to Prisma Compute. --- - - Internal team reference. Not for users. This section will be removed after the public beta launch on 2026-05-13. The public docs live at [/compute](/compute). - +:::warning +Internal team reference. Not for users. This section will be removed after the public beta launch on 2026-05-13. The public docs live at [/compute](/compute). +::: Deploy a Next.js app to Prisma Compute. This quickstart walks through scaffolding a fresh app, enabling standalone output (required by Compute), and running the first deploy with either `@looma/prisma-cli` or `@prisma/compute-cli`. diff --git a/apps/docs/content/docs/compute-internal/quickstart/nuxt.mdx b/apps/docs/content/docs/compute-internal/quickstart/nuxt.mdx index 207eee6698..b8a98c4aa6 100644 --- a/apps/docs/content/docs/compute-internal/quickstart/nuxt.mdx +++ b/apps/docs/content/docs/compute-internal/quickstart/nuxt.mdx @@ -5,9 +5,9 @@ metaTitle: "Quickstart: Deploy a Nuxt app to Prisma Compute (Internal)" metaDescription: Scaffold a Nuxt app and deploy it to Prisma Compute. No extra config, Nuxt uses the Nitro node-server preset by default. --- - - Internal team reference. Not for users. This section will be removed after the public beta launch on 2026-05-13. The public docs live at [/compute](/compute). - +:::warning +Internal team reference. Not for users. This section will be removed after the public beta launch on 2026-05-13. The public docs live at [/compute](/compute). +::: Deploy a Nuxt app to Prisma Compute. Nuxt builds with the Nitro `node-server` preset by default, so no adapter config is required. diff --git a/apps/docs/content/docs/compute-internal/quickstart/tanstack-start.mdx b/apps/docs/content/docs/compute-internal/quickstart/tanstack-start.mdx index c47263cb9e..7de63090e5 100644 --- a/apps/docs/content/docs/compute-internal/quickstart/tanstack-start.mdx +++ b/apps/docs/content/docs/compute-internal/quickstart/tanstack-start.mdx @@ -5,9 +5,9 @@ metaTitle: "Quickstart: Deploy a TanStack Start app to Prisma Compute (Internal) metaDescription: Scaffold a TanStack Start app (Vite + Nitro node preset) and deploy it to Prisma Compute. --- - - Internal team reference. Not for users. This section will be removed after the public beta launch on 2026-05-13. The public docs live at [/compute](/compute). - +:::warning +Internal team reference. Not for users. This section will be removed after the public beta launch on 2026-05-13. The public docs live at [/compute](/compute). +::: Deploy a TanStack Start app to Prisma Compute. TanStack Start builds with Vite and the Nitro `node` preset, both already wired in the official starter. From 354a6f094c465d9e8543aa3f0ec438519d7274c9 Mon Sep 17 00:00:00 2001 From: ArthurGamby Date: Thu, 23 Apr 2026 16:42:42 +0200 Subject: [PATCH 12/15] docs(compute): add framework logos to quickstart Cards Uses existing SVGs in /public/img/technologies/ for Next.js, Astro (dark variant), Nuxt, and TanStack. Adds a placeholder bun.svg (simple bun glyph) since no Bun logo existed in the repo. Both /compute and /compute-internal index pages get the same icon treatment. Next.js logo is black-on-transparent, so it carries `dark:invert` to render correctly on the dark docs theme. --- .../content/docs/compute-internal/index.mdx | 30 +++++++++++++++---- apps/docs/content/docs/compute/index.mdx | 30 +++++++++++++++---- apps/docs/public/img/technologies/bun.svg | 6 ++++ 3 files changed, 56 insertions(+), 10 deletions(-) create mode 100644 apps/docs/public/img/technologies/bun.svg diff --git a/apps/docs/content/docs/compute-internal/index.mdx b/apps/docs/content/docs/compute-internal/index.mdx index ce2c4fd438..b4eea6099e 100644 --- a/apps/docs/content/docs/compute-internal/index.mdx +++ b/apps/docs/content/docs/compute-internal/index.mdx @@ -23,19 +23,39 @@ See the full [CLI reference](/compute-internal/cli) for both. Each quickstart walks you from a fresh app to a live deployment. Pick the one that matches your stack. - + } + > Scaffold, enable standalone output, and deploy. - + } + > Set up the Node adapter in standalone mode and deploy on port 4321. - + } + > Scaffold and deploy with the default Nitro node-server preset. - + } + > Deploy the official Vite plus Nitro starter. - + } + > Deploy a Bun.serve HTTP server directly. diff --git a/apps/docs/content/docs/compute/index.mdx b/apps/docs/content/docs/compute/index.mdx index 66ee8f0891..959a9f7393 100644 --- a/apps/docs/content/docs/compute/index.mdx +++ b/apps/docs/content/docs/compute/index.mdx @@ -12,19 +12,39 @@ Prisma Compute is app hosting for Node.js and Bun apps. Deploy from the command Each quickstart walks you from a fresh app to a live deployment. - + } + > Scaffold a Next.js app, enable standalone output, and deploy. - + } + > Deploy an Astro app with the Node adapter in standalone mode. - + } + > Deploy a Nuxt app with the default Nitro node-server preset. - + } + > Deploy a TanStack Start app built with Vite and Nitro. - + } + > Deploy a Bun HTTP server directly. diff --git a/apps/docs/public/img/technologies/bun.svg b/apps/docs/public/img/technologies/bun.svg new file mode 100644 index 0000000000..579cf474b6 --- /dev/null +++ b/apps/docs/public/img/technologies/bun.svg @@ -0,0 +1,6 @@ + + + + + + From b8ecf4147b4ffbbc8e236d9b6e06a23f426edeee Mon Sep 17 00:00:00 2001 From: ArthurGamby Date: Thu, 23 Apr 2026 17:20:30 +0200 Subject: [PATCH 13/15] fix(docs): add width/height to logo img tags The MDX `img` tag is overridden to a Next.js Image wrapper in mdx-components.tsx, which requires explicit width and height props. Without them the page 500s during render. --- apps/docs/content/docs/compute-internal/index.mdx | 10 +++++----- apps/docs/content/docs/compute/index.mdx | 10 +++++----- 2 files changed, 10 insertions(+), 10 deletions(-) diff --git a/apps/docs/content/docs/compute-internal/index.mdx b/apps/docs/content/docs/compute-internal/index.mdx index b4eea6099e..46da265691 100644 --- a/apps/docs/content/docs/compute-internal/index.mdx +++ b/apps/docs/content/docs/compute-internal/index.mdx @@ -26,35 +26,35 @@ Each quickstart walks you from a fresh app to a live deployment. Pick the one th } + icon={} > Scaffold, enable standalone output, and deploy. } + icon={} > Set up the Node adapter in standalone mode and deploy on port 4321. } + icon={} > Scaffold and deploy with the default Nitro node-server preset. } + icon={} > Deploy the official Vite plus Nitro starter. } + icon={} > Deploy a Bun.serve HTTP server directly. diff --git a/apps/docs/content/docs/compute/index.mdx b/apps/docs/content/docs/compute/index.mdx index 959a9f7393..bc2b98b0f7 100644 --- a/apps/docs/content/docs/compute/index.mdx +++ b/apps/docs/content/docs/compute/index.mdx @@ -15,35 +15,35 @@ Each quickstart walks you from a fresh app to a live deployment. } + icon={} > Scaffold a Next.js app, enable standalone output, and deploy. } + icon={} > Deploy an Astro app with the Node adapter in standalone mode. } + icon={} > Deploy a Nuxt app with the default Nitro node-server preset. } + icon={} > Deploy a TanStack Start app built with Vite and Nitro. } + icon={} > Deploy a Bun HTTP server directly. From f6c2e1edf6c5046ee622ad680b322c09c89e47b2 Mon Sep 17 00:00:00 2001 From: ArthurGamby Date: Thu, 23 Apr 2026 17:21:26 +0200 Subject: [PATCH 14/15] docs(compute): render framework logo inline with Card title Moves the img into the `title` prop (wrapped in a flex span) instead of passing it via the separate `icon` prop, so the logo sits on the same line as the framework name rather than above it. --- apps/docs/content/docs/compute-internal/index.mdx | 15 +++++---------- apps/docs/content/docs/compute/index.mdx | 15 +++++---------- 2 files changed, 10 insertions(+), 20 deletions(-) diff --git a/apps/docs/content/docs/compute-internal/index.mdx b/apps/docs/content/docs/compute-internal/index.mdx index 46da265691..3b28cb2bb9 100644 --- a/apps/docs/content/docs/compute-internal/index.mdx +++ b/apps/docs/content/docs/compute-internal/index.mdx @@ -25,36 +25,31 @@ Each quickstart walks you from a fresh app to a live deployment. Pick the one th } + title={Next.js} > Scaffold, enable standalone output, and deploy. } + title={Astro} > Set up the Node adapter in standalone mode and deploy on port 4321. } + title={Nuxt} > Scaffold and deploy with the default Nitro node-server preset. } + title={TanStack Start} > Deploy the official Vite plus Nitro starter. } + title={Bun} > Deploy a Bun.serve HTTP server directly. diff --git a/apps/docs/content/docs/compute/index.mdx b/apps/docs/content/docs/compute/index.mdx index bc2b98b0f7..5a07d55c13 100644 --- a/apps/docs/content/docs/compute/index.mdx +++ b/apps/docs/content/docs/compute/index.mdx @@ -14,36 +14,31 @@ Each quickstart walks you from a fresh app to a live deployment. } + title={Next.js} > Scaffold a Next.js app, enable standalone output, and deploy. } + title={Astro} > Deploy an Astro app with the Node adapter in standalone mode. } + title={Nuxt} > Deploy a Nuxt app with the default Nitro node-server preset. } + title={TanStack Start} > Deploy a TanStack Start app built with Vite and Nitro. } + title={Bun} > Deploy a Bun HTTP server directly. From f69b5c4e97dc96bb8af74a8459444c537b443fdf Mon Sep 17 00:00:00 2001 From: ArthurGamby Date: Thu, 23 Apr 2026 17:21:46 +0200 Subject: [PATCH 15/15] docs(compute): replace Bun logo placeholder with official SVG from bun.com --- apps/docs/public/img/technologies/bun.svg | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/apps/docs/public/img/technologies/bun.svg b/apps/docs/public/img/technologies/bun.svg index 579cf474b6..7ef15001d2 100644 --- a/apps/docs/public/img/technologies/bun.svg +++ b/apps/docs/public/img/technologies/bun.svg @@ -1,6 +1 @@ - - - - - - +Bun Logo \ No newline at end of file