pixelysg rewires Mike to run on the edge

A new database path lets this fork survive on Cloudflare's serverless platform, where Mike's usual plumbing breaks.

infrastructure

pixelysg gave Mike a second way to talk to its database. The original setup leaned on a client library that misbehaves inside Cloudflare Workers - a "serverless" platform that runs code on servers near the user rather than in one central data centre. That made Mike hard to host there.

The fix is an alternate connection that speaks directly to the database using a driver built for the Workers environment. It only kicks in when configured; otherwise the existing path runs untouched, so nothing breaks for current deployments. The tradeoff pixelysg takes on is a hand-written translation layer that has to keep matching every way the rest of Mike queries data - useful to know if you're weighing this fork for production.

So what Worth a look for any team that wants to deploy Mike on edge or serverless infrastructure instead of a conventional always-on server.

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

1 commit from pixelysg/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA	Subject	Author	Date
`27f2ffc9`	feat: support direct Postgres via DATABASE_URL	Jia Jian Goi	2026-05-15	↗ GitHub
commit body When DATABASE_URL is set, data queries route to a direct Postgres connection using a Supabase-compatible query builder. Auth continues through Supabase. Falls back to existing Supabase client when unset. Supports optional DATABASE_SCHEMA env var for custom schema prefix. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

SHA

Subject

Author

Date

27f2ffc9

feat: support direct Postgres via DATABASE_URL

Jia Jian Goi

2026-05-15

↗ GitHub

commit body

When DATABASE_URL is set, data queries route to a direct Postgres
connection using a Supabase-compatible query builder. Auth continues
through Supabase. Falls back to existing Supabase client when unset.

Supports optional DATABASE_SCHEMA env var for custom schema prefix.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-394.md from inside the repo you want the changes in.