mikeOnBreeze/mike-oss
A local-first take on Mike that swaps cloud dependencies for a filesystem-backed setup you can run entirely on your own machine.
This is mikeOnBreeze's fork of Mike, and it exists for a single, pointed reason: to run Mike without any cloud backend. Where upstream reaches out to managed Postgres, hosted auth, and object storage in the cloud, this build keeps everything on the local filesystem.
The practical upshot is a version of Mike you can stand up on a laptop or a single server without provisioning external accounts. That makes it a natural starting point for anyone evaluating Mike offline, working under data-residency constraints, or just preferring a self-contained deployment they fully control.
There's only one author visible here - mikeOnBreeze - and the fork is tightly scoped around this one idea rather than a broader product reimagining. Curious readers should click through to GitHub to see how far the local-only approach has been taken.
What's in it
- Runs without a cloud database Replaces the managed Postgres dependency with a local data store, so Mike can run without an external database account.
- No hosted auth required Strips out the dependency on a hosted authentication provider, simplifying setup for self-contained deployments.
- Local file storage instead of object storage Uses the local filesystem in place of cloud object storage, keeping uploads and assets on the machine running Mike.
- Self-contained deployment The combined effect is a Mike you can run end-to-end on your own infrastructure, with no third-party services in the loop.
Direction
infrastructure
Activity
Threads of work (detailed view)
mikeOnBreeze pulls Mike off the cloud and onto his laptop
A personal injury lawyer rebuilt Mike so that nothing - files, accounts, search index - ever leaves his own machine.