🟢 #1 Add deployment configs and DEPLOYMENT.md so the repo can be launched as a website +719 8d ago self by
cphlabspace ↗ analysis ↗ GitHub <!-- CURSOR_AGENT_PR_BODY_BEGIN -->
cphlabspace/mikeOSS
A Mike fork from @cphlabspace focused on making the project deployable as a real public site rather than a local-only build.
This is @cphlabspace's fork of Mike, and so far the work has nothing to do with what Mike does and everything to do with how it gets out the door. The application itself is untouched; the energy is going into the path from a working dev checkout to something actually hosted on the open web.
The single thread of work tracked here is about making the deployment story explicit - closing the gap between "builds locally" and "runs as a public site" without changing the product. If you're curious about Mike as an operational thing rather than as a feature set, this is a fork worth a click-through.
There isn't a rebrand, a niche pivot, or a new audience visible yet. It reads like infrastructure groundwork - the kind of work someone does before they stand a real instance up.
What's in it
- Deployable by default @cphlabspace is filling in the missing pieces so Mike can be hosted as a public site, not just run on a laptop.
- Hands off the product The application itself is left alone - this fork is about operations, not features.
Direction
infrastructure
Activity
A pull request that adds no features and changes no product behaviour - but turns the fork from "builds on my laptop" into something a stranger can host.
Threads of work (detailed view)
cphlabspace writes down how to actually launch Mike
A pull request that adds no features and changes no product behaviour - but turns the fork from "builds on my laptop" into something a stranger can host.
Pull requests (detailed view)
🟢 Open (1)
by
cphlabspace · opened 8d ago