PasqualeMuraca makes Mike self-hostable in a box

A clean Docker setup that turns Mike into something a small firm's IT person could actually stand up on their own server.

infrastructuresecurity

Most legal-AI tools assume you'll use the vendor's cloud. PasqualeMuraca's fork takes the opposite bet: package the whole Mike platform - the backend service and the web app - into Docker containers (a standard way of bundling software so it runs the same on any machine) that can be spun up with a single command. There's a health-check wiring so the pieces start in the right order, an example secrets file documenting every key Mike needs to talk to its AI providers and storage, and a 250-line setup guide.

It's not turnkey production hosting - there's no database bundled in, and no HTTPS layer - but as a starting point for a firm that wants Mike running on its own infrastructure rather than someone else's cloud, it's the most lift-and-shift-friendly work in any Mike fork so far.

So what Relevant for any firm or legal-ops team weighing self-hosting Mike for data-residency, confidentiality, or procurement reasons.

View this fork on GitHub →

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

Commits in this thread

7 commits from PasqualeMuraca/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
a1b3ea05 Add Docker configuration for backend (Express) Pasquale Muraca 2026-05-13 ↗ GitHub
1d7e7196 Add Docker configuration for frontend (Next.js) Pasquale Muraca 2026-05-13 ↗ GitHub
4865d746 Add docker-compose orchestration for Mike platform Pasquale Muraca 2026-05-13 ↗ GitHub
30a17154 Add Docker environment variables template Pasquale Muraca 2026-05-13 ↗ GitHub
5aa62ed6 Add Docker ignore patterns Pasquale Muraca 2026-05-13 ↗ GitHub
f3e2a1ed Add Docker deployment guide Pasquale Muraca 2026-05-13 ↗ GitHub
70aaf0c2 Pass Supabase env vars to frontend Docker build Pasquale Muraca 2026-05-13 ↗ GitHub
commit body
Add NEXT_PUBLIC_SUPABASE_URL and NEXT_PUBLIC_SUPABASE_PUBLISHABLE_DEFAULT_KEY as build-time ARGs in Dockerfile.frontend and export them as ENV so the frontend build can embed Supabase configuration. Update docker-compose.yml to forward those build args with fallback defaults. Also remove the explicit compose version declaration at the top of docker-compose.yml.

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

⬇ Download capture-thread-427.md