Deployment
Environments, variables, queue, and the production checklist.
Deployment
Where it runs
Any runtime that executes Hono: Node 18+, Cloudflare Workers, Deno, Bun. Next.js route handlers are the documented pattern.
Variables
.env.local for local development. In production, define them in the platform environment (Vercel, Worker Secrets). Tenant secrets (X-Apointoo-Tenant-Key and equivalents) never take the NEXT_PUBLIC_ prefix: a public variable is a leaked variable.
Queue and outbox
Conversion uploads flow through the queue with an outbox. A transient Google failure does not break the confirm; the attempt retries on schedule. Without persistence configured, memory stores are for development only.
Deduplication
Keep the idempotency key beside the record. A repeated confirm returns the same result; nothing doubles at the destination.
Production checklist
-
NEXT_PUBLIC_SITE_URLpoints at the canonical host (www). - Tenant secrets live server-side only.
- A persistent state store is configured (not memory).
- Consent gates capture.
- Revalidation webhook wired if you run a CMS.
- Delivery logs reachable by the team that responds to incidents.
Lectura adicional