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.

infrastructure

elitan tore out Mike's standalone backend and relocated everything inside the web app. Instead of running two pieces, this fork now hands all traffic to one entry point that quietly sorts it - sign-in, app calls, and everything else - and routes it onward. The payoff is a simpler thing to deploy and reason about.

The catch worth knowing about: rather than rewrite the old server logic, elitan wrapped it in a compatibility layer so it keeps running unchanged inside the new structure. That kept the change contained, but it leaves a non-standard layer in the middle that anyone adopting this fork inherits. There's also a tie to Cloudflare Workers - Cloudflare's platform for running code at the network edge - that the team flags as worth re-checking if you deploy somewhere else.

So what Worth a look for anyone weighing this fork as a base to build on, since it trades a two-part setup for one app at the cost of a custom layer you'd own.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

3 commits from elitan/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
b7320066 refactor(api): move backend into next route handlers Johan Eliasson 2026-05-15 ↗ GitHub
ba3270f4 Codex worktree snapshot: archive-cleanup Johan Eliasson 2026-05-15 ↗ GitHub
Co-authored-by: Codex
9fd7e44b refactor(api): merge latest main Johan Eliasson 2026-05-15 ↗ GitHub

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-413.md from inside the repo you want the changes in.

⬇ Download capture-thread-413.md