andrsschultz makes Mike runnable on a laptop

A one-command local setup, so you can kick the tyres on Mike without standing up cloud infrastructure first.

infrastructure

Until now, anyone wanting to try Mike had to go provision a Supabase project - Supabase being the hosted backend platform Mike relies on for its database and auth. andrsschultz has added a self-contained local setup: a config file, the database schema, seed data, and a short runbook that gets the whole stack running on your own machine. The README and example environment files now point at that local instance and tell you exactly where to grab the keys.

It's plumbing, not product - no new features for end users. But it materially lowers the bar for a curious lawyer, a legal-ops lead, or a prospective contributor to spin Mike up on a laptop over a coffee, instead of treating evaluation as an IT project.

So what If you've wanted to evaluate Mike but stalled at the infrastructure step, this is the fork to clone.

View this fork on GitHub →

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

Commits in this thread

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

SHA Subject Author Date

d354c310 Add local Supabase config and one-shot migration asschultz 2026-04-30 ↗ GitHub

SHA	Subject	Author	Date
`d354c310`	Add local Supabase config and one-shot migration	asschultz	2026-04-30	↗ GitHub
commit body Add a supabase/ directory with local Supabase runbook and config: config.toml (custom ports/API URL), migrations/000_one_shot_schema.sql (one-shot DB schema), seed.sql, README.md, and a supabase/.gitignore. Update docs and examples to prefer local Supabase: README updated with startup and key extraction steps and AIRGAP.md mention; backend/.env.example and frontend/.env.local.example now reference the local SUPABASE_URL and placeholder local keys. Also add GSJ-Master to .gitignore. This enables easy local development with npx supabase start and a fresh database initialized from the provided one-shot migration.

commit body

Add a supabase/ directory with local Supabase runbook and config: config.toml (custom ports/API URL), migrations/000_one_shot_schema.sql (one-shot DB schema), seed.sql, README.md, and a supabase/.gitignore. Update docs and examples to prefer local Supabase: README updated with startup and key extraction steps and AIRGAP.md mention; backend/.env.example and frontend/.env.local.example now reference the local SUPABASE_URL and placeholder local keys. Also add GSJ-Master to .gitignore. This enables easy local development with npx supabase start and a fresh database initialized from the provided one-shot migration.

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-83.md from inside the repo you want the changes in.

⬇ Download capture-thread-83.md