teemuoksanen packages Mike to ship as a container

A new deployment recipe turns this fork into something you can host as a self-contained service, not just run on a developer's laptop.

infrastructuredocument-conversion

teemuoksanen has added a build recipe that bundles the back end into a container - a portable, ready-to-run package that carries everything the service needs to start up the same way on any server. The signal here is direction: this fork is being set up to actually run somewhere, not just experimented with locally.

The telling detail is what gets bundled in alongside the code: LibreOffice, the open-source office suite. That strongly suggests the back end converts documents server-side - think turning Word files into PDFs, or rendering legal documents for viewing. It's a small addition, but it points at a fork thinking about real document handling, not just chat.

So what Worth a look for anyone evaluating which Mike forks are built to deploy and handle real legal documents rather than demo in a notebook.

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

SHA Subject Author Date
94d79bd7 Add Dockerfile for Node.js application setup Teemu Oksanen 2026-06-13 ↗ GitHub

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

⬇ Download capture-thread-679.md