justice-bac/mike
justice-bac is doing the deployment plumbing that lets Mike actually run inside a government department, not just on a laptop.
This fork of Mike is an infrastructure effort, plain and simple. Where the base project hands you something to clone and stand up yourself, justice-bac is building the path to production: a reproducible development container, a one-command route to cloud hosting on Fly.io, and - tellingly - the certificate and TLS work needed to run behind a Government-of-Canada firewall. The through-line is operability, not new legal features.
The work is led by justice-bac, with contributions from @juleskuehn on the devcontainer bring-up. The Government-of-Canada TLS root handling is the loudest signal about who this is for: an organization that needs Mike to run inside a locked-down public-sector environment rather than in the open. Alongside that, justice-bac kept the branch synced with upstream as the setup came together.
If you want to see how a legal-AI tool gets made deployable inside a government department - as opposed to what it does for lawyers - this is a fork worth clicking through to. The detail lives on GitHub.
What's in it
- Devcontainer bring-up A reproducible containerized setup so Mike starts cleanly and consistently, without hand-tuning a local machine.
- One-command Fly.io deployment A path that turns Mike from a clone-it-yourself project into something you can stand up on cloud hosting in a single run.
- Government-firewall readiness Certificate and TLS work - including a Government-of-Canada root - aimed at running Mike inside a locked-down public-sector environment.
- Kept current with upstream The fork was synced with upstream mid-stream, keeping the setup branch aligned as the deployment work landed.
Direction
infrastructuresecurity
Activity
juleskuehn ↗ analysis ↗ GitHub juleskuehn ↗ analysis ↗ GitHub juleskuehn ↗ analysis ↗ GitHub Threads of work (detailed view)
justice-bac gives Mike a one-command path to production
This fork turns Mike from a clone-it-yourself project into something you can actually stand up on cloud hosting in a single run.
justice-bac adds Fly.io deployment with an 855-line interactive deploy script
justice-bac/mike ships two-stage Dockerfiles for backend and frontend, `fly.toml` configs, and a substantial deploy script that handles multi-source secret resolution, builder retry logic, and automatic `NEXT_PUBLIC_*` build-arg injection. The Dockerfiles and the lazy-init Supabase pattern are straightforward to borrow; the script is opinionated around a `backend/.env` + `frontend/.env.local` workflow but structurally reusable.
justice-bac is wiring Mike up to run behind a government firewall
This fork is doing the unglamorous work that decides whether Mike can actually run inside a government department - not just on a laptop.
justice-bac wires devcontainer for corporate VPN and deploys mike to Fly.io
justice-bac/mike adds a `.devcontainer/` setup that trusts the Government of Canada TLS interception root, then builds out a full Fly.io deployment path including Dockerfiles, `fly.toml` configs, and an interactive deploy script. The devcontainer fix is specific to corporate VPN environments; the Fly.io scaffolding is broadly applicable.
Pull requests (detailed view)
✅ Merged (1)
juleskuehn · opened 2mo ago · merged 2mo ago by juleskuehn ⛔ Closed without merge (2)
juleskuehn · opened 2mo ago · closed 2mo ago juleskuehn · opened 2mo ago · closed 2mo ago