promptly3518/mike
promptly3518's fork is a quiet, deploy-focused take on Mike that's being shipped to Render and Vercel while kept out of search engines.
This is promptly3518's fork of Mike, and so far the work has the feel of someone standing up a private instance rather than reshaping the product. The visible activity centres on getting the backend running on Render, getting the frontend deploying cleanly on Vercel, and fixing a real data bug that was being masked by thin error logging.
There's no rebrand here, no obvious vertical pivot, and no new headline feature for end users. What there is, instead, is a deliberate signal that this deployment isn't meant to be found: the frontend has been told to stay out of search indexes entirely. Read that alongside the deploy plumbing and the picture is consistent - a working copy intended for a specific, non-public audience.
If you're trying to gauge where promptly3518 is heading, the honest answer is: not far from upstream yet. The energy so far has gone into making Mike run somewhere real, not into changing what Mike is.
What's in it
- Render-ready backend deploy The backend is being packaged for Render, including the heavier dependencies needed for document conversion to actually work in that environment.
- Vercel-ready frontend deploy The frontend has been nudged through Vercel's install and build quirks so it deploys cleanly out of the box.
- Kept out of search engines The deployed frontend is explicitly told not to be indexed or crawled - a clear signal this instance isn't meant to surface publicly.
- Sharper backend error visibility A real bug in the projects listing was tracked down and fixed, with better server-side logging added along the way so the next one is easier to catch.
Direction
infrastructuresecurity