📝 Render backend deployment config 1 commit 8d ago minor change
gregplumbly/mike
gregplumbly's fork takes Mike toward a containerized, deployable backend - a quiet infrastructure-first start.
This is an early-stage fork of Mike from gregplumbly, and so far the work is squarely about getting the backend service deployable rather than reshaping what Mike does for legal users. If you tried it today, you'd find the groundwork for running Mike's backend as a container on Render - including the document-handling pieces a legal tool needs at runtime - rather than a new feature set or a rebrand.
There's only one thread of work here, and it's plumbing: a deployment story, not a product pivot. That's a perfectly reasonable place to start a fork - get it running somewhere first, then build - but it does mean there isn't yet a distinct niche or direction to read into beyond "make this thing shippable."
If you're curious where gregplumbly takes it next, the fork is young enough that the GitHub repo is the best place to watch. Click through for the actual configuration and to see whether feature work follows the deployment groundwork.
What's in it
- Containerized backend Packages Mike's backend service to run as a container, so it can be deployed and run consistently rather than only locally.
- Render deployment Targets Render as a hosting platform, giving the fork a concrete path from repo to a running service.
- Document-handling runtime The runtime bundles document-conversion tooling - the kind of capability a legal-document workflow leans on once it's live.
Direction
infrastructure