benzuko

Deployment guide

This project builds to a standalone Next.js server and deploys anywhere that runs Node 20 or supports the Next.js adapter.

1. GitHub upload

cd benzuko
git init
git add .
git commit -m "feat: initial benzuko production scaffold"
git branch -M main
git remote add origin https://github.com/your-org/benzuko.git
git push -u origin main

CI (.github/workflows/deploy.yml) then runs lint → typecheck → test → build → E2E on every push and PR.

2. Vercel (recommended)

Dashboard: Import the repo → framework auto-detected as Next.js → add env vars → Deploy.

CLI:

npm i -g vercel
vercel            # preview
vercel --prod     # production

vercel.json sets the framework, install/build commands, region, and headers. For automated deploys, uncomment the amondnet/vercel-action block in the workflow and add VERCEL_TOKEN, VERCEL_ORG_ID, VERCEL_PROJECT_ID secrets.

3. Netlify

netlify.toml is preconfigured with @netlify/plugin-nextjs.

npm i -g netlify-cli
netlify deploy --build --prod

Or connect the repo in the Netlify dashboard (build npm run build).

4. Cloudflare Pages

Framework preset: Next.js
Build command: npm run build
Build output: .next
Add env vars in Settings → Environment variables.
For full edge support use @cloudflare/next-on-pages:
```
npx @cloudflare/next-on-pages@latest
```

5. Docker

# build + run with compose (includes healthcheck)
docker compose up --build          # http://localhost:3000

# or plain docker
docker build -t benzuko .
docker run -p 3000:3000 --env NEXT_PUBLIC_APP_URL=http://localhost:3000 benzuko

The multi-stage Dockerfile produces a minimal node:20-alpine runtime image from the standalone build and runs as a non-root user.

6. cPanel (Passenger / Node.js Selector)

BENZUKO runs as a live Node process on cPanel via server.js (Passenger entry point). Git deployment, ZIP upload, rollback, SSL, and the shared-hosting build caveats are covered in full in CPANEL.md.

Quick version:

Set up the app in Setup Node.js App (Node 20, startup file server.js).
Deploy via Git Version Control (uses .cpanel.yml) or ZIP upload.
Shared hosting often can’t run next build — build in CI (release-artifact.yml produces benzuko-cpanel.zip) and upload the .next.

Post-deploy checklist

Set NEXT_PUBLIC_APP_URL to the real domain (fixes SEO/sitemap/robots).
Set AUTH_SECRET and any provider secrets.
Point rate limiting at Redis/Upstash for multi-instance hosts.
Verify /api/health returns ok.
Run Lighthouse; confirm headers via curl -I.

This site is open source. Improve this page.