R2 Uploads

blob-starter

Vercel's Blob Next.js Starter — an image uploader with drag-and-drop, preview, progress and a private delivery route — running on Cloudflare Workers + Static Assets through @opennextjs/cloudflare, with the files in a Cloudflare R2 bucket provisioned by Terraform through Orun, and packaged as an Orun baseline: one command takes a new product from nothing to live on stage and prod, in its own repository, under its own name — in ONE landing.

The page and the uploader are the template's; the store is R2 and the upload route is its front door. What the baseline adds is everything needed to make a copy of it somebody else's, built the way cirrus-baseline is since its one-landing bootstrap. See specs/epics/blob-starter for the design, the milestones and the as-built status.

Instantiating a product

git clone --depth 1 --branch <baseline-tag> https://github.com/sourceplane/blob-starter
cd blob-starter
orun new --blueprint repo-blueprint.yaml --out ~/sites/acme-uploads --run-hooks --resume \
  --set reponame=acme-uploads --set productname="Acme Uploads" \
  --set githuborg=acme-inc --set subdomain=<workers-dev-subdomain>

Or, once the platform's registry lists it, from the Orun console (Baselines → blob-starter → Build). Two phases: 01-product creates the repository and lands the whole product as ONE pull request — intent, CI, tooling, the R2 root, the uploader and its tests — and one convergence applies the R2 bucket on stage and prod and then deploys the uploader bound to it; 02-docs records the live deployment from probed facts. BOOTSTRAP.md is the operator guide; docs/phases/ has a page per phase.

The only connection a build needs is Cloudflare (with R2 enabled on the account). Uploads work from the first deploy: the Worker reaches its bucket through its R2 binding, so there is no storage token to paste — Vercel Blob's BLOB_READ_WRITE_TOKEN has no counterpart here.

The new repository receives the product only — the app, its R2 root, its tests, its CI, its tooling, a README of its own and its operating contract — renamed throughout to the product's name, repository, Cloudflare Worker and bucket names. None of this repository's machinery ships.

What is here (the product)

Getting started

pnpm install
pnpm run wire:fixture   # render apps/web/wrangler.jsonc from the offline fixture
pnpm typecheck
pnpm lint
pnpm test
pnpm build              # next build + opennextjs-cloudflare build → apps/web/.open-next

pnpm --filter @app/web dev        # http://localhost:3000 — a local R2 bucket through wrangler's platform proxy
pnpm --filter @app/web preview    # wrangler dev over the built Worker, same local bucket

How it maps to Vercel

Both routes carry the template's ⚠️ "add your own authentication" notes: nothing ships auth.

How the bucket name reaches the Worker

infra/terraform/cloudflare-r2 ──apply──► orun secret WIRING_CLOUDFLARE_R2 (stage, prod)
   (CLOUDFLARE_R2_TOKEN, r2-data)              │   (each deploy resolves it as it starts;
                                               │    a missing one fails the lane)
                                               ▼
apps/web  dependsOn cloudflare-r2 (enforced on main) · secretEnv WIRING_CLOUDFLARE_R2_<ENV>
  build:  tooling/wire/live.mjs → wrangler.jsonc with the environment's bucket name
          (dev, verify-only, renders the fixture) → next build → opennextjs-cloudflare
  deploy: CLOUDFLARE_API_TOKEN (workers-deploy) — the running Worker holds no storage key

wrangler.jsonc is committed as the fixture render of wrangler.template.jsonc, because the deploy lane's verify-app-structure step checks the config exists before it builds; testing/e2e.test.sh fails if the two disagree.

CI