Add rule26 deployment conventions to mike fork
Adds everything needed to run mike as a rule26 sibling service on ai-server alongside folio-enrich and folio-mapper: - backend/Dockerfile: Node 20 + LibreOffice multi-stage build - frontend/Dockerfile: Node 20 multi-stage; bakes NEXT_PUBLIC_* at build time - docker-compose.yml: two services on ports 8094 (frontend) / 8095 (backend) - .env.defaults: committed non-secret config (PORT, FRONTEND_URL, R2_BUCKET_NAME) - .env.example: template for Infisical-driven .env; documents all required secrets - scripts/deploy.sh: Infisical → .env → docker compose up --build → health poll - CLAUDE.md: full project guide for future Claude Code sessions - docs/rule26-integration.md: REST surface doc for sibling services and future chatcya integration - README.md: appended rule26 deployment section - .gitignore: added .env.bak, .env.tmp, .claude/; whitelisted .env.defaults Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
| Repository | jthacker48/mike |
|---|---|
| Author | Jeremy Thacker <jeremy.thacker@rule26.org> |
| Authored | |
| Parents | 469ee4ad |
| Stats | 10 files changed , +644 |
| Part of | Rule26 deployment scaffolding for mike fork |
Capture this commit into my fork
Download a Markdown prompt that tells Claude how to port this
exact commit into your working tree. Run it via
claude -p < capture-commit-67e256d6.md
from inside the repo you want the change in.