justice-bac/mike

justice-bac is doing the deployment plumbing that lets Mike actually run inside a government department, not just on a laptop.

A concentrated burst of setup work - 14 commits across five threads - that landed by mid-May 2026 and has been quiet since; early days for a fork focused on getting Mike deployable.

View on GitHub →

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

Direction

infrastructuresecurity

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.

📝 Devcontainer bring-up for the justice-bac fork 5 commits 2mo ago minor change
📝 Devcontainer with Government-of-Canada TLS Root 5 commits 2mo ago minor change
📝 Upstream Sync into jus-setup Branch 1 commit 2mo ago minor change

Threads of work (detailed view)

4 threads have been distilled into posts.

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 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)

3 PRs touch this fork — inbound (filed against it) or outbound (filed from it). State icons match the editorial dashboard.

✅ Merged (1)

⛔ Closed without merge (2)