jthacker48/mike

Operational integration fork: Docker + Infisical deploy stack for a rule26 sibling-service environment

One topic on record. jthacker48 added a full Docker-based deployment scaffold - multi-stage Dockerfiles, docker-compose, deploy script, env defaults, CLAUDE.md, and integration docs - then iterated through four build fixes in the same session (path correction, `--legacy-peer-deps` for frontend npm install and prune, and `next.config.ts → next.config.js` transpilation for the slim runtime image). No changes to application logic.

View on GitHub →

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

Direction

infrastructureintegration

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.

Threads of work (detailed view)

1 thread have been distilled into posts.

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.