Purdue Hackers API

Coordination server for managing Purdue Hackers hardware and systems. Controls doorbells, phones, Discord message feeds, and event attendance tracking — all through a unified REST + WebSocket API.

Built with Hono, deployed as a single Vercel Function on the standard Node.js (Fluid compute) runtime with WebSocket support. Bun runs it locally. Durable data lives in Turso via Drizzle; realtime coordination state lives in Redis (Upstash on Vercel).

Getting started

bun install
cp .env.example .env    # TURSO_DATABASE_URL=file:local.db and REDIS_URL=redis://localhost:6379 work for local dev
bun run db:migrate
redis-server --daemonize yes   # or: brew services start redis
bun dev

The server runs at http://localhost:3000. The OpenAPI spec is generated from the route annotations (hono-openapi) and served at /openapi.

Command	Description
bun dev	Run with hot reload
bun run lint	Lint with oxlint
bun run format	Format with oxfmt
bun run typecheck	Type-check with tsc
bun run db:generate	Generate Drizzle migrations
bun run db:migrate	Apply migrations to the database

Environment variables are listed in .env.example. Domain rules (the phone call model, device keys, dial plan) live in AGENTS.md.

Project layout

src/
├── app.ts       # Entrypoint: routes + OpenAPI + the WebSocket-injected HTTP server
├── routes/      # Endpoints, annotated with hono-openapi
├── services/    # WebSocket coordination per subsystem (Redis control plane)
├── protocol/    # Zod schemas for HTTP bodies and WS messages
├── lib/         # Turso-backed logic and shared helpers
└── db/          # Drizzle client, schema, migrations

WebSocket connections stay on the function instance that accepted them (data plane). Shared state, presence rosters, and cross-instance fan-out go through Redis pub/sub (control plane), so clients on different instances still see each other. Attendance data is durable in Turso.

Deploying

vercel.json sets maxDuration: "max". Vercel resolves src/app.ts as the Hono entrypoint; its default export is a Node HTTP server with WebSocket upgrades injected (@hono/node-ws), so everything — WebSockets included — runs through one function.

vercel deploy

Attach Upstash Redis from the Vercel Marketplace (its REDIS_URL is the rediss:// connection string), set the remaining environment variables, and run bun run db:migrate once against the Turso database.