chmonitorVercel
Deploy chmonitor to Vercel — legacy guide for the Next.js v0.2 build; v0.3+ targets Cloudflare Workers or Docker.
Deploy chmonitor to Vercel using the legacy Next.js build. Vercel auto-deploys on push to main and inlines client env at build time.
Legacy guide — Next.js v0.2 only
This guide targets the legacy Next.js build (v0.2 and earlier). The current app (apps/dashboard, TanStack Start, v0.3+) is designed for Cloudflare Workers. If you run v0.3+, use Cloudflare Workers or Docker.
Prerequisites
What you need
- A Vercel account
- Node.js 22.x or later (build runtime)
- A reachable ClickHouse endpoint with a monitoring user
Setup
Use the one-click button, or follow the manual steps.
Import the repo
Go to vercel.com/new and import the repository.
Set build settings
Vercel detects Next.js automatically.
| Setting | Value |
|---|---|
| Framework preset | Next.js |
| Build command | pnpm run build (or npm run build) |
| Output directory | .next |
| Install command | pnpm install |
| Node.js version | 22.x or later |
Set environment variables
Project → Settings → Environment Variables — see Configure.
Deploy
Click Deploy or push to main.
Configure
Required: CLICKHOUSE_HOST, CLICKHOUSE_USER, CLICKHOUSE_PASSWORD.
Set CHM_* once (Environment variables).
Do not set VITE_* or NEXT_PUBLIC_* as operator config — the current app is TanStack Start.
Template: apps/dashboard/.env.example.
Verify
- Open the Vercel URL — overview should load.
- Upgrade: push to
main(or merge). Env changes: update in the dashboard, then Deployments → Redeploy.
For breaking changes, see Migrating to v0.3.
Troubleshooting
Related
Cloudflare Workers
The current v0.3+ deployment target — serverless, global, D1 and Cron support.
Docker
Run the published container anywhere Docker runs.
Authentication
Choose an auth provider: none, API key, Clerk, or trusted proxy.
Migrating to v0.3
Breaking changes between major versions.
Production checklist
Harden and validate before exposing to a team or the internet.