jthacker48/mike
Operational integration fork: Docker + Infisical deploy stack for a rule26 sibling-service environment
jthacker48's fork wires mike into rule26's internal service stack on a dedicated ai-server host alongside folio-enrich and case-brain. All recorded activity is infrastructure work: Dockerfiles, a deploy script backed by Infisical secret management, and env configuration. No product or backend-logic divergence from upstream. The Dockerfile fixes for React 19 peer deps and next.config.ts runtime parsing are the only changes that transfer to other deployments.
What's in it
- Rule26 deployment Mike is being set up as a sibling service inside Rule26's existing AI infrastructure rather than run as a standalone experiment.
Direction
infrastructureintegration
Activity
Threads of work (detailed view)
jthacker48 wires mike into a rule26 sibling-service stack on ai-server
Jeremy Thacker's fork adds a full Docker + Infisical + deploy-script stack to run mike alongside folio-enrich and other rule26 services. The deployment wiring is rule26-specific and not portable, but two Dockerfile fixes - React 19 peer-dep workaround and a `next.config.ts` transpilation step - will hit anyone containerizing the upstream frontend.