drewstokesbary/mike

drewstokesbary is getting Mike running on Render - a deployment fork, not a product pivot, at least so far.

A single concentrated burst - eight commits inside roughly 80 minutes on June 1st - with no activity since, so it reads as early setup rather than sustained momentum.

View on GitHub →

This is Mike, being wired up to run somewhere real. drewstokesbary spent a focused stretch on June 1st getting the backend ready to deploy on Render in a Docker container, sorting out the plumbing that stands between a checkout and a running instance.

There's no rebrand here, no new feature surface, no legal-practice niche staked out yet - just the unglamorous, necessary work of making the thing deployable. If you're evaluating this fork, read it as someone setting up their own hosted copy rather than building a distinct product on top of Mike.

Whether it grows into something more is an open question. Right now it's one tight thread of deployment work. Click through to GitHub if you want to watch where drewstokesbary takes it next.

What's in it

Direction

infrastructure

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.

📝 Render backend deployment setup 8 commits 7d ago minor change