Altien builds a Mike you can run on your laptop

No cloud account, no hosted database, no identity provider - just docker-compose up.

infrastructure

Altien's fork now ships a complete local development stack: a containerised Postgres database, a thin API layer in front of it (PostgREST, which turns a database directly into a web API), and an emulator that pretends to be Azure's file storage. The same role-and-permissions setup the team uses in production gets recreated locally, and a small helper mints the login tokens the app needs so you can sign in without wiring up a real identity provider.

There's also a one-shot health check that pokes each piece of the stack and prints a plain-English report of what's working and what isn't. The point is to let a developer - or an evaluator - clone the repo and have a working Mike in front of them in minutes, with nothing rented from anyone.

So what Matters to any legal-tech team weighing Mike as a foundation: a fork you can stand up offline is dramatically easier to evaluate, demo to a partner, or run inside a firewall.

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 Altien/mikeOssAzure, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date

56cadfe6 feat(local-stack): docker-compose dev stack + helper scripts Allen Morgan 2026-05-08 ↗ GitHub

SHA	Subject	Author	Date
`56cadfe6`	feat(local-stack): docker-compose dev stack + helper scripts	Allen Morgan	2026-05-08	↗ GitHub
commit body End-to-end developer experience without any hosted dependency. * docker-compose.dev.yml - Postgres 16, PostgREST 12.2.3, and Azurite (Azure Blob emulator) wired together for AUTH_PROVIDER=local development. Plays the role our Bicep stack plays in production. * scripts/local-stack/00-init-roles.sql - recreates the PostgREST role topology (web_anon / authenticated / service_role) on the freshly provisioned local Postgres. This is the same role topology that the 0005_postgres_roles migration applies to non-Supabase Azure Postgres deployments. * scripts/local-stack/forge-jwt.mjs - mints HS256 service-role and authenticated-role JWTs against JWT_SECRET so the local backend and tests can sign in without standing up a real IdP. * scripts/dev-infra-check.ps1 - smoke check: validates Postgres reachability, the role topology, PostgREST schema cache, and Azurite blob endpoints. Prints a human-readable status report so a fresh clone can confirm the stack is wired up correctly.

commit body

End-to-end developer experience without any hosted dependency.

  * docker-compose.dev.yml         - Postgres 16, PostgREST 12.2.3,
                                     and Azurite (Azure Blob emulator)
                                     wired together for AUTH_PROVIDER=local
                                     development.  Plays the role our
                                     Bicep stack plays in production.

  * scripts/local-stack/00-init-roles.sql
                                   - recreates the PostgREST role
                                     topology (web_anon / authenticated
                                     / service_role) on the freshly
                                     provisioned local Postgres.  This
                                     is the same role topology that the
                                     0005_postgres_roles migration
                                     applies to non-Supabase Azure
                                     Postgres deployments.

  * scripts/local-stack/forge-jwt.mjs
                                   - mints HS256 service-role and
                                     authenticated-role JWTs against
                                     JWT_SECRET so the local backend
                                     and tests can sign in without
                                     standing up a real IdP.

  * scripts/dev-infra-check.ps1     - smoke check: validates Postgres
                                     reachability, the role topology,
                                     PostgREST schema cache, and
                                     Azurite blob endpoints.  Prints a
                                     human-readable status report so a
                                     fresh clone can confirm the stack
                                     is wired up correctly.

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

⬇ Download capture-thread-201.md