pixelysg/mike

Infrastructure-focused fork adding Bedrock, Cloudflare Workers support, and a direct Postgres query path

Three topics of work: Amazon Bedrock provider support, Cloudflare Workers deploy fixes, and a direct Postgres adapter behind `DATABASE_URL`. Infrastructure-oriented changes with no apparent modifications to the legal AI feature logic.

View on GitHub →

pixelysg's fork diverges from upstream on the infrastructure side. The author has added Amazon Bedrock as an LLM provider, reworked the deployment configuration to run on Cloudflare Workers, and introduced a direct Postgres connection mode that routes data queries through node-postgres while keeping the Supabase JS API surface intact. These changes hang together: the Cloudflare target motivates avoiding Supabase's HTTP REST layer, and the Postgres adapter makes that possible without rewriting call sites.

The Bedrock integration and the DATABASE_URL direct-connect path are the two changes most likely to be useful in another codebase. Both are opt-in via environment variables and don't require changes to existing query or LLM call patterns.

What's in it

Direction

infrastructureintegration

Activity

Themed changes and pull requests touching this fork, newest first. Themed changes that haven't been turned into a public post yet still appear — they're real work even without a published writeup.

📝 Cloudflare Workers deploy fixes 4 commits 2mo ago minor change

Threads of work (detailed view)

4 threads have been distilled into posts.

Amazon Bedrock provider added, with eight model-ID fix commits to land it

pixelysg wires Claude through Amazon Bedrock as a fourth LLM backend. The adapter code is clean and small. Getting Bedrock's inference profile ID format right took eight commits and the final values still show inconsistencies - re-verify before importing.

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.

Direct Postgres path via DATABASE_URL, bypassing Supabase's REST layer

Commit 27f2ffc9 adds an opt-in query path that talks to Postgres directly through `node-postgres` rather than through the Supabase JS client. Set `DATABASE_URL` and the existing Supabase chain API -- `.from().select().eq()` and so on -- routes through a hand-rolled adapter instead of Supabase's REST gateway.