📝 Root monorepo wrapper and Supabase env-var rename 2 commits 2mo ago minor change
heaventree/mike
Supabase-native Mike fork with the first authored schema migration in the ecosystem
heaventree/mike is a focused deployment fork targeting Supabase. The two tracked changes are a root monorepo wrapper with a Supabase env-var rename, and a 389-line SQL migration that defines the full Mike data model - 16 tables covering users, projects, documents, workflows, chats, and tabular reviews. Upstream willchen96/mike ships no canonical migration; heaventree's file is the only authored, version-stamped starting point available across known forks.
What's in it
- Supabase-native data model A from-scratch rebuild of Mike's database aimed at Supabase - a deployment path the upstream project doesn't offer out of the box.
- Reworked repository layout The project has been restructured into a unified workspace, the kind of housekeeping that tends to precede bigger changes.
- Refreshed configuration surface Environment and secrets handling has been reorganised, hinting at a self-hosted deployment in mind.
Direction
infrastructureintegration
Activity
📝 heaventree's database tips its hand: this fork wants to be a product 1 commit 2mo ago multi-tenantsecurity draft
The full data model just landed in one move, and it reads like a commercial SaaS rather than a weekend experiment.
Threads of work (detailed view)
heaventree's database tips its hand: this fork wants to be a product
The full data model just landed in one move, and it reads like a commercial SaaS rather than a weekend experiment.
heaventree adds a full Supabase migration file upstream had never shipped
heaventree/mike lands a 389-line SQL migration covering the complete Mike data model - something the upstream willchen96/mike never published. If you're deploying on Supabase, this is the only authored migration in the fork ecosystem that gets you from zero to a working schema.