📝 Rename `frontend/` to `app/` 1 commit 2mo ago minor change
elitan/mike
Activity
📝 Docker dev stack: Postgres 16 + MinIO, schema auto-applied on fresh volumes 1 commit 2mo ago infrastructureintegration draft
A single `docker compose up` now brings up the full local stack - Postgres, MinIO, and a one-shot bucket setup sidecar. Non-default ports (15432, 19000/19001) mean it won't stomp on services you already have running.
📝 elitan folds Mike's backend into the frontend and ships it as one app 3 commits 2mo ago infrastructure draft
The separate server is gone - elitan merged it into the web application so the whole fork deploys as a single unit.
📝 elitan wants to pull elitan/mike's whole backend in-house 6 commits 2mo ago infrastructuresecurity draft
A proposed re-platforming that trades hosted services for a stack the operator runs and controls directly.
✅ #2 refactor(api): move backend into next route handlers +2,294 -7,090 2mo ago self by
elitan ↗ analysis ↗ GitHub ## Summary
⛔ #141 refactor(api): move backend into next route handlers +1,858 -6,011 2mo ago by
elitan ↗ analysis ↗ GitHub ## Summary
⛔ #141 refactor(api): move backend into next route handlers +1,858 -6,011 2mo ago by
elitan ↗ analysis ↗ GitHub ## Summary
This fork no longer needs a Supabase account - it'll run on any standard Postgres database you point it at.
The fork swaps its hosted backend for a self-managed login-and-database stack - without rewriting the app on top of it.
A proposal to run the whole app as a single deployable instead of a separate backend service plus a frontend - though it never made it in.
📝 elitan teaches Mike to run its AI on your own hardware 1 commit 2mo ago infrastructureintegration draft
A fourth model option lets the fork answer without ever calling a cloud provider.
✅ #1 refactor(db): replace supabase with better auth and kysely +3,208 -1,374 2mo ago self by
elitan ↗ analysis ↗ GitHub ## Summary
📝 Express backend folded into Next.js route handlers with oRPC as the typed-RPC layer 0 commits — infrastructure draft
elitan eliminated the separate backend service by relocating Express routes under the Next.js app and wiring them through an oRPC dispatcher. One process to run, one set of deps to manage - but the migration left a non-t…
Threads of work (detailed view)
Docker dev stack: Postgres 16 + MinIO, schema auto-applied on fresh volumes
A single `docker compose up` now brings up the full local stack - Postgres, MinIO, and a one-shot bucket setup sidecar. Non-default ports (15432, 19000/19001) mean it won't stomp on services you already have running.
elitan folds Mike's backend into the frontend and ships it as one app
The separate server is gone - elitan merged it into the web application so the whole fork deploys as a single unit.
Standalone Express backend eliminated: everything moves into Next.js route handlers
elitan deleted the `backend/` package entirely and relocated its code under the Next.js app. The result is one process, one set of dependencies, one deployment unit - but the migration introduced an HTTP compatibility shim that you'd be inheriting.
elitan wants to pull elitan/mike's whole backend in-house
A proposed re-platforming that trades hosted services for a stack the operator runs and controls directly.
elitan cuts the Supabase cord
This fork no longer needs a Supabase account - it'll run on any standard Postgres database you point it at.
elitan drops Supabase entirely, moves to Better Auth + Kysely over plain Postgres
This is the most consequential commit in elitan's run: a full replacement of Supabase as both auth layer and data access layer, touching nearly every backend route and the entire frontend auth surface. The fork now requires only Postgres.
elitan rips Supabase out of Mike's foundations
The fork swaps its hosted backend for a self-managed login-and-database stack - without rewriting the app on top of it.
elitan replaces Supabase with Better Auth and Kysely
elitan dropped Supabase as both the auth and data layer, substituting Better Auth backed directly by Postgres and Kysely as the typed query builder. The result is a stack that runs against any Postgres database without a Supabase project.
elitan tries to fold Mike's two servers into one
A proposal to run the whole app as a single deployable instead of a separate backend service plus a frontend - though it never made it in.
elitan teaches Mike to run its AI on your own hardware
A fourth model option lets the fork answer without ever calling a cloud provider.
elitan adds Ollama as a fourth LLM provider for fully local inference
elitan wired Ollama's streaming chat API into the existing provider stack, so Mike can run entirely on local models with no external API key. The change is self-contained enough to evaluate on its own merits.
Express backend folded into Next.js route handlers with oRPC as the typed-RPC layer
elitan eliminated the separate backend service by relocating Express routes under the Next.js app and wiring them through an oRPC dispatcher. One process to run, one set of deps to manage - but the migration left a non-trivial HTTP compatibility shim in place.
Pull requests (detailed view)
✅ Merged (2)
by
elitan · opened 2mo ago · merged 2mo ago by elitan by
elitan · opened 2mo ago · merged 2mo ago by elitan ⛔ Closed without merge (4)
by
elitan · opened 2mo ago · closed 2mo ago by
elitan · opened 2mo ago · closed 2mo ago by
elitan · opened 2mo ago · closed 2mo ago by
elitan · opened 2mo ago · closed 2mo ago