From a491937f67647cb9c46fa30acea2c377f907012d Mon Sep 17 00:00:00 2001 From: ArthurGamby Date: Wed, 15 Apr 2026 13:14:19 +0300 Subject: [PATCH 1/3] 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 2/3] 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 3/3] 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`.