Back
Ian
Load previous page…
Porting the restaurant change-suggest webhook to api-cf with Drizzle #brg
Reservation email forwarding via Postmark Inbound #brg
api-cf parity in #brg: change-queue triggers, delete revalidation, workflow triggers wired into routers
Mounting Better Auth on #brg api-cf, sessions wired through
Retiring Vercel Workflow DevKit in #brg — background jobs (restaurant embeddings, user profile overview) now run on Cloudflare over HTTP
ISR revalidation over HTTP ported into the API Worker #brg
Migrating #brg background jobs off Vercel to Cloudflare Workers — restaurant/award updaters ported to Drizzle, crons repointed to Cron Triggers, Vercel crons deleted. Worker owns scheduling now.
Swapping Better Auth to the Drizzle adapter — auth no longer assumes Node, and Postgres goes through Hyperdrive in prod. #brg going runtime-agnostic
Wine-photos skill for the Concierge #brg
Migrating #brg from Neon to Planetscale
Health + db-check endpoints on the #brg agent, surfacing the underlying DB error instead of swallowing it
Ported the remaining restaurant tools into the agent #brg
Moving the #brg agent DB access off the Prisma Neon adapter to raw pg over Hyperdrive — DB and knowledge graph now read through the same binding
POCing #brg api as a Cloudflare Worker — Drizzle over Postgres, Hyperdrive for the connection. Health check now answers even when the DB doesn't.
Enabling logs + traces for the agent Worker. Flying blind was getting old. #brg
Ian 0, Possum 1
Untangling database config into packages/drizzle/#brg generic base schema table routers live duration fallback geolocate users general filters collector logs timeseries lab screens profiles collectors api actions autonomous poc status gap
Replacing eve with our first flue concierge agent #brg
Moving prisma migrate deploy out of the Vercel build into a GitHub Action. Migrations don't belong in the build pipeline #brg
Two crash fixes in #jot: project-tracker table-handle and a site-wide theme ReferenceError.
Home
Search
Messages
Notifications
More

Are you sure?