Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
16 commits
Select commit Hold shift + click to select a range
a491937
feat(docs): add Prisma Compute EA section
ArthurGamby Apr 15, 2026
99ed136
refactor(docs): collapse Compute into a single internal reference page
ArthurGamby Apr 15, 2026
6426dd1
docs(compute): drop em dashes and ellipses from prose
ArthurGamby Apr 15, 2026
29f9003
Merge remote-tracking branch 'origin/main' into docs/prisma-compute-q…
ArthurGamby Apr 23, 2026
ac6d693
docs(compute): add Astro, Nuxt, and TanStack Start to quickstart
ArthurGamby Apr 23, 2026
8353ddf
docs(compute): clarify Quickstart tab scope and fix port note
ArthurGamby Apr 23, 2026
18936fa
docs(compute): split into landing + per-framework quickstarts + refer…
ArthurGamby Apr 23, 2026
9fc4672
docs(compute): remove early-access badge and EA references
ArthurGamby Apr 23, 2026
cc06ce4
docs(compute): document --env file path, comma-separated, and quoted …
ArthurGamby Apr 23, 2026
11cf432
docs(compute): split into /compute (official) and /compute-internal (…
ArthurGamby Apr 23, 2026
9a43b7a
docs(compute): add Compute (Internal) top-level navbar item
ArthurGamby Apr 23, 2026
7d02f2e
fix(docs): swap Alert JSX for :::warning directive in compute-internal
ArthurGamby Apr 23, 2026
354a6f0
docs(compute): add framework logos to quickstart Cards
ArthurGamby Apr 23, 2026
b8ecf41
fix(docs): add width/height to logo img tags
ArthurGamby Apr 23, 2026
f6c2e1e
docs(compute): render framework logo inline with Card title
ArthurGamby Apr 23, 2026
f69b5c4
docs(compute): replace Bun logo placeholder with official SVG from bu…
ArthurGamby Apr 23, 2026
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
78 changes: 78 additions & 0 deletions apps/docs/content/docs/compute-internal/cli.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,78 @@
---
title: CLI reference
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.
---

:::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.

- [`@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

<CodeBlockTabs defaultValue="looma">
<CodeBlockTabsList>
<CodeBlockTabsTrigger value="looma">@looma/prisma-cli</CodeBlockTabsTrigger>
<CodeBlockTabsTrigger value="compute">@prisma/compute-cli</CodeBlockTabsTrigger>
</CodeBlockTabsList>
<CodeBlockTab value="looma">

```bash
npx @looma/prisma-cli app list-deploys
npx @looma/prisma-cli app show-deploy <deployment-id>
```

</CodeBlockTab>
<CodeBlockTab value="compute">

```bash
bunx @prisma/compute-cli versions list
bunx @prisma/compute-cli versions show <version-id>
```

</CodeBlockTab>
</CodeBlockTabs>

## Command inventory

<CodeBlockTabs defaultValue="looma">
<CodeBlockTabsList>
<CodeBlockTabsTrigger value="looma">@looma/prisma-cli</CodeBlockTabsTrigger>
<CodeBlockTabsTrigger value="compute">@prisma/compute-cli</CodeBlockTabsTrigger>
</CodeBlockTabsList>
<CodeBlockTab value="looma">

```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 <id> | promote <id> | rollback | remove
```

</CodeBlockTab>
<CodeBlockTab value="compute">

```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 <version-id> [--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
```

</CodeBlockTab>
</CodeBlockTabs>

Need a flag that is not listed here? Run `--help` on the relevant command. Both CLIs have stable, browsable help output.
106 changes: 106 additions & 0 deletions apps/docs/content/docs/compute-internal/environment-variables.mdx
Original file line number Diff line number Diff line change
@@ -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.
---

:::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.

## During a deploy

Repeat `--env` per variable:

<CodeBlockTabs defaultValue="looma">
<CodeBlockTabsList>
<CodeBlockTabsTrigger value="looma">@looma/prisma-cli</CodeBlockTabsTrigger>
<CodeBlockTabsTrigger value="compute">@prisma/compute-cli</CodeBlockTabsTrigger>
</CodeBlockTabsList>
<CodeBlockTab value="looma">

```bash
npx @looma/prisma-cli app deploy \
--env DATABASE_URL=postgresql://example \
--env NODE_ENV=production
```

</CodeBlockTab>
<CodeBlockTab value="compute">

```bash
bunx @prisma/compute-cli deploy \
--env DATABASE_URL=postgresql://example \
--env NODE_ENV=production
```

</CodeBlockTab>
</CodeBlockTabs>

## Without rebuilding

Same flag shape, dedicated command:

<CodeBlockTabs defaultValue="looma">
<CodeBlockTabsList>
<CodeBlockTabsTrigger value="looma">@looma/prisma-cli</CodeBlockTabsTrigger>
<CodeBlockTabsTrigger value="compute">@prisma/compute-cli</CodeBlockTabsTrigger>
</CodeBlockTabsList>
<CodeBlockTab value="looma">

```bash
npx @looma/prisma-cli app update-env --env STRIPE_KEY=sk_live_xxx
npx @looma/prisma-cli app list-env
```

</CodeBlockTab>
<CodeBlockTab value="compute">

```bash
bunx @prisma/compute-cli env update --env STRIPE_KEY=sk_live_xxx
bunx @prisma/compute-cli env update --unset-env LEGACY_FLAG
```

</CodeBlockTab>
</CodeBlockTabs>

## 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.
:::
79 changes: 79 additions & 0 deletions apps/docs/content/docs/compute-internal/index.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,79 @@
---
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.
---

:::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.

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.

<Cards>
<Card
href="/compute-internal/quickstart/nextjs"
title={<span className="flex items-center gap-2"><img src="/img/technologies/nextjs.svg" alt="" width={20} height={20} className="dark:invert" />Next.js</span>}
>
Scaffold, enable standalone output, and deploy.
</Card>
<Card
href="/compute-internal/quickstart/astro"
title={<span className="flex items-center gap-2"><img src="/img/technologies/astrodark.svg" alt="" width={20} height={20} />Astro</span>}
>
Set up the Node adapter in standalone mode and deploy on port 4321.
</Card>
<Card
href="/compute-internal/quickstart/nuxt"
title={<span className="flex items-center gap-2"><img src="/img/technologies/nuxtjs.svg" alt="" width={20} height={20} />Nuxt</span>}
>
Scaffold and deploy with the default Nitro node-server preset.
</Card>
<Card
href="/compute-internal/quickstart/tanstack-start"
title={<span className="flex items-center gap-2"><img src="/img/technologies/tanstack.png" alt="" width={20} height={20} />TanStack Start</span>}
>
Deploy the official Vite plus Nitro starter.
</Card>
<Card
href="/compute-internal/quickstart/bun"
title={<span className="flex items-center gap-2"><img src="/img/technologies/bun.svg" alt="" width={20} height={20} />Bun</span>}
>
Deploy a Bun.serve HTTP server directly.
</Card>
</Cards>

## Manage a deployment

After the first deploy, use these references day-to-day.

<Cards>
<Card href="/compute-internal/environment-variables" title="Environment variables">
Set secrets and config inline on deploy, or update later without rebuilding.
</Card>
<Card href="/compute-internal/logs" title="Logs">
Stream runtime logs per compute version or deployment.
</Card>
<Card href="/compute-internal/cli" title="CLI reference">
Full command inventory for both `@looma/prisma-cli` and `@prisma/compute-cli`.
</Card>
<Card href="/compute-internal/limitations" title="Limitations">
Known caveats around framework support, env updates, and log streaming.
</Card>
</Cards>

## Support

Questions or breakage: `#product-compute`.
36 changes: 36 additions & 0 deletions apps/docs/content/docs/compute-internal/limitations.mdx
Original file line number Diff line number Diff line change
@@ -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.
---

:::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.

## 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 <byte-offset>`.
- One concurrent log stream per compute version.

## Support

Questions or breakage: `#product-compute`.
45 changes: 45 additions & 0 deletions apps/docs/content/docs/compute-internal/logs.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,45 @@
---
title: Logs
url: /compute-internal/logs
metaTitle: Logs | Prisma Compute (Internal)
metaDescription: Stream runtime logs from a Prisma Compute deployment.
---

:::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.

## Stream logs

<CodeBlockTabs defaultValue="compute">
<CodeBlockTabsList>
<CodeBlockTabsTrigger value="compute">@prisma/compute-cli</CodeBlockTabsTrigger>
<CodeBlockTabsTrigger value="looma">@looma/prisma-cli</CodeBlockTabsTrigger>
</CodeBlockTabsList>
<CodeBlockTab value="compute">

```bash
bunx @prisma/compute-cli logs <compute-version-id>
bunx @prisma/compute-cli logs <compute-version-id> --tail 200
bunx @prisma/compute-cli logs <compute-version-id> --from-start
bunx @prisma/compute-cli logs <compute-version-id> --cursor <byte-offset>
```

</CodeBlockTab>
<CodeBlockTab value="looma">

```bash
npx @looma/prisma-cli app logs
npx @looma/prisma-cli app logs --deployment <deployment-id>
npx @looma/prisma-cli app logs --tail 200
```

</CodeBlockTab>
</CodeBlockTabs>

## Limits

- Stream caps at around 10 minutes. Reconnect with `--cursor <byte-offset>` to resume from where the last stream ended.
- Only one concurrent log stream per compute version.
17 changes: 17 additions & 0 deletions apps/docs/content/docs/compute-internal/meta.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
{
"title": "Compute (Internal)",
"root": true,
"icon": "Cpu",
"pages": [
"---Introduction---",
"index",
"---Quickstart---",
"...quickstart",
"---Reference---",
"environment-variables",
"logs",
"cli",
"---More---",
"limitations"
]
}
Loading
Loading