justice-bac/mike

A deployment-focused Mike fork preparing the app for containerized use, government networks, and Fly.io hosting.

Fourteen changes across seven tracked threads suggest a focused setup burst in mid-May 2026, with no later activity recorded.

View on GitHub →

justice-bac is concentrating on the practical work of getting Mike running reliably outside a developer laptop. The focus is a containerized setup that can cope with certificate and storage issues, including use behind a government firewall.

It also adds a clearer route to Fly.io, aiming to make a production deployment less of a bespoke exercise. This looks like operational groundwork rather than a new legal-practice experience, but it could matter to organisations assessing whether Mike can fit their environment.

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 with Government-of-Canada TLS Root 5 commits 5mo ago minor change
📝 Upstream Sync into jus-setup Branch 1 commit 5mo 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)

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

✅ Merged (1)

⛔ Closed without merge (1)