Next.js
Create and customise a Next.js status page with create-heyo-status.
Use create-heyo-status to generate the page, API, database setup and scheduler
wiring together. Choose a deployment target for production: Vercel uses Cron
and PostgreSQL; Cloudflare uses OpenNext, Worker cron triggers and D1. The
status page needs server rendering and scheduled checks; installing the package
into an app does not set those up.
Create a project
Pass next to select the framework without a prompt. Omit flags to choose
the framework, deployment, database and theme interactively.
The generated scripts and CLI require Bun 1.4.3+ even if you use another
package manager. If you skipped dependency installation, install the project's
dependencies first. Replace the example monitors in heyo-status.config.ts.
With Vercel/PostgreSQL, bun dev starts the local scheduler and bun run check
runs one check; Cloudflare/D1 uses Worker cron triggers in production instead.
Customise the generated Next.js project
heyo-status.config.tsdefines the database, monitors, schedule and theme.app/api/heyo-status/[...path]/route.tsmounts the status API under the config'sbasePath(default/api/heyo-status). Keep them in sync if you change that path.app/page.tsxrenders a fresh snapshot on every request. Keep its dynamic rendering setting; a static page would show stale status.app/layout.tsxloads the theme stylesheet and bootstrap script.- The deployment overlay supplies the production scheduler. Do not remove
its cron routes or Worker
scheduledhandler when changing the app.
For Cloudflare, use HTTP or DNS monitors: Workers cannot run native TCP/TLS checks. For Vercel, TCP/TLS checks need Node.js 20.19+. See the Cloudflare and Vercel guides before deploying.