hreiten/mike
An early-stage fork of Mike where hreiten is rebuilding the foundation around their own preferred stack before adding new direction.
This is hreiten's fork of Mike, and at this point it's essentially a bootstrap exercise. The single change on record is a bundled "make it run on my stack" pass - refreshing dependencies and reshaping storage and tooling so the project lines up with how hreiten wants to develop.
There isn't yet a visible product thesis here beyond "get a clean working baseline." No new features for end users, no rebrand, no obvious niche. If you're curious what hreiten plans to build on top of this groundwork, GitHub is the place to watch.
Worth checking back on. The shape of a fork usually becomes clear in the second or third thread of work, not the first.
What's in it
- Modernised stack hreiten has refreshed the underlying platform to current versions across both backend and frontend, giving the fork a contemporary foundation to build on.
- Reworked storage approach File storage has been reshaped around a cloud object-store model rather than the upstream default, suggesting a deployment story aimed at hosted use.
Direction
infrastructure