Algolia Search

algolia-search

Vercel's Algolia Integration Example (Algolia's Algolia × Supabase × Vercel starter) — instant, typo-tolerant search over a Postgres products table, with InstantSearch's facets and a product page that shows what only the database holds — running on Cloudflare Workers + Static Assets through @opennextjs/cloudflare, with the database a Supabase Postgres project reached through Cloudflare Hyperdrive, both provisioned by Terraform through Orun and the schema and the template's demo products applied by Orun's db-migrate (the way the Lumen baseline does it), 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 template's code is the code. What the port changes is what the Workers runtime, a fresh unattended deployment and Orun's rule that no SaaS key is ever in a build force: upstream's lazy module-level pg.Pool becomes one pg client per request over the Hyperdrive binding (lib/db.ts, its query() unchanged at every call site); the Algolia application id and search-only key are the Worker's secrets, read when the page renders and handed to InstantSearch as props, instead of NEXT_PUBLIC_ variables inlined at build; and demo/seed.sql, which upstream had you paste into Supabase's SQL Editor, is two migrations (the table, then its twenty demo products) applied before the app serves. Until the owner connects Algolia, the home page keeps the template's "search activates once…" notice and lists the catalogue straight from Postgres under it. Every table in public has row-level security, so Supabase's Data API serves none of it — the internal-only cost prices, suppliers and notes above all. What the baseline adds is everything needed to make a copy of it somebody else's, built the way cirrus-baseline is. See specs/epics/algolia-search for the design, the milestones and the as-built status, including every departure.

Instantiating a product

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

Or, once the platform's registry lists it, from the Orun console (Baselines → algolia-search → Build). Two phases: 01-product creates the repository, mints the five brokered credentials (Cloudflare and Supabase) and lands the whole product as one pull request, whose convergence on main provisions and deploys it per environment in a fixed order —

supabase ──▶ cloudflare-hyperdrive ──▶ db-migrate ──▶ web

— each edge mode: enforced on a push to main and advisory on a pull request; then 02-docs records the live deployment from probed facts. BOOTSTRAP.md is the operator guide; docs/phases/ has a page per phase. The Supabase organization needs room for two projects (stage and prod) — the free plan's limit.

The new repository receives the product only — the app, the Terraform roots, the migrations, the tests, its CI, its tooling, a README of its own and its operating contract — renamed throughout to the product's name, repository, Worker, Supabase project and Hyperdrive config. None of this repository's machinery ships. The card asks for no Algolia key: the product goes live with search not connected, and its owner connects Algolia after the bootstrap — two optional secrets (ALGOLIA_APP_ID, ALGOLIA_SEARCH_API_KEY) and the Algolia connector in Algolia's dashboard (the product's README, "Connect Algolia").

What is here (the product)

Getting started

pnpm install
pnpm run wire:fixture   # re-render apps/web/wrangler.jsonc from its template (committed; this changes nothing)
pnpm typecheck
pnpm lint
pnpm test
pnpm build              # next build + opennextjs-cloudflare build → apps/web/.open-next

The build needs no database and no Algolia account. Running it locally — a Postgres on localhost:54322 (supabase start), pnpm --filter @app/web db:migrate, then next dev or wrangler dev, with Algolia's keys in apps/web/.dev.vars if you have them — is in the product's README (.baseline/product/README.md), which is what a product built from here carries.

How it maps to Vercel

CI