userarena1002/mike

Parallel Databricks-target app added alongside the upstream codebase

Single large commit, single topic. Fork is a personal workspace reorientation toward Databricks - not a community effort, not production-ready (mocked review paths). Relevant only if you're evaluating Databricks as a deployment target for mike. The migration inventory document is worth a read even if the code isn't.

View on GitHub →

userarena1002's sole commit drops a self-contained databricks_app/ subtree - FastAPI + Vite React + Databricks notebook jobs + Unity Catalog bootstrap scripts - next to the untouched upstream frontend/ and backend/ directories. The model layer is pluggable (mock | openai | databricks) but all Databricks job paths currently return mocks. A migration inventory documents the planned cuts: auth, sharing, R2/S3, Cloudflare deployment, free-form chat, and doc generation are all removed in favor of a single-user, upload-first review shape.

What's in it

Direction

infrastructureintegration

Activity

Themed changes and pull requests touching this fork, newest first. Themed changes that haven't been turned into a public post yet still appear — they're real work even without a published writeup.

Threads of work (detailed view)

2 threads have been distilled into posts.

userarena1002 adds a parallel Databricks-target app alongside the upstream codebase

A 6,687-line commit lands a full parallel application under `databricks_app/` - FastAPI backend, Vite React frontend, Databricks notebook jobs, Unity Catalog bootstrap scripts, and a migration inventory document - while leaving the original `frontend/` and `backend/` trees intact. This is a reorientation toward a specific enterprise deployment shape, not a drop-in feature.