Remove the React frontend entirely #90

New issue

Closed

opened 2026-05-27 22:06:06 +00:00 by coilysiren · 1 comment

coilysiren commented

2026-05-27 22:06:06 +00:00

Owner

Problem

The repo-recall frontend has been non-functional since it was prompted into existence and Kai has never missed it in practice. Human-pull consumption of repo-recall data already flows through the MCP server (agents) and the luca-* skills + coily wrappers (Kai). The website is a second unused surface, costing build time, dependency surface, and mental overhead with no offsetting use case. Kai is also re-evaluating websites in general in favor of TUIs for deployments-of-one, so the frontend is unlikely to be revived in its current form.

Scope

Remove the React frontend entirely. The Rust binary continues to serve the JSON surface and MCP - those are the load-bearing surfaces.

Concrete deletions:

web/ subtree (React + Vite + Tailwind, package.json, tsconfig*, src, dist, node_modules)
Dockerfile.web
deploy/Caddyfile (only present to front the static bundle)
web service from docker-compose.yml
Makefile targets: web-install, web-dev, web-build, watch-all, docker-build-web, and the web-install call from the install target. Update .PHONY line accordingly.
README + AGENTS.md + docs/* references to the web frontend, two-container shape, or "future k8s deploy fronts the SPA". Replace with a one-liner that this is an API + MCP service only.
k8s deploy manifests (if any) that ship the web container - check deploy/ and any helm chart.
CI workflows that build or test web/.

Out of scope

Removing the JSON surface that the frontend consumed. Other clients (potential future TUI, ad-hoc curl, agents) may consume it.
Rebuilding as a TUI. Separate decision, separate issue if it ever happens. Kai's current read is that even a TUI is probably unnecessary given MCP + skills already cover the consumption paths.

Acceptance

cargo build --release and make ci pass.
docker compose up brings up only the API service.
No web/, Dockerfile.web, deploy/Caddyfile, or web-* Makefile target remains.
README accurately describes the post-removal shape.

**Problem** The repo-recall frontend has been non-functional since it was prompted into existence and Kai has never missed it in practice. Human-pull consumption of repo-recall data already flows through the MCP server (agents) and the `luca-*` skills + `coily` wrappers (Kai). The website is a second unused surface, costing build time, dependency surface, and mental overhead with no offsetting use case. Kai is also re-evaluating websites in general in favor of TUIs for deployments-of-one, so the frontend is unlikely to be revived in its current form. **Scope** Remove the React frontend entirely. The Rust binary continues to serve the JSON surface and MCP - those are the load-bearing surfaces. Concrete deletions: - `web/` subtree (React + Vite + Tailwind, package.json, tsconfig*, src, dist, node_modules) - `Dockerfile.web` - `deploy/Caddyfile` (only present to front the static bundle) - `web` service from `docker-compose.yml` - Makefile targets: `web-install`, `web-dev`, `web-build`, `watch-all`, `docker-build-web`, and the `web-install` call from the `install` target. Update `.PHONY` line accordingly. - README + AGENTS.md + docs/* references to the web frontend, two-container shape, or "future k8s deploy fronts the SPA". Replace with a one-liner that this is an API + MCP service only. - k8s deploy manifests (if any) that ship the web container - check `deploy/` and any helm chart. - CI workflows that build or test `web/`. **Out of scope** - Removing the JSON surface that the frontend consumed. Other clients (potential future TUI, ad-hoc curl, agents) may consume it. - Rebuilding as a TUI. Separate decision, separate issue if it ever happens. Kai's current read is that even a TUI is probably unnecessary given MCP + skills already cover the consumption paths. **Acceptance** - `cargo build --release` and `make ci` pass. - `docker compose up` brings up only the API service. - No `web/`, `Dockerfile.web`, `deploy/Caddyfile`, or web-* Makefile target remains. - README accurately describes the post-removal shape.

coilysiren referenced this issue from coilyco-flight-deck/infrastructure

2026-05-27 22:18:53 +00:00

Drop the repo-recall web container + adjust tailnet exposure for api-only service #159

coilysiren closed this issue

2026-05-27 22:19:19 +00:00

coilysiren commented

2026-05-27 22:19:31 +00:00

Author

Owner

Landed in github.com/coilysiren/repo-recall@d122c14 . Forgejo mirror has pre-existing drift (one commit ahead of GitHub main, unrelated to this work), so the commit-trailer auto-close didn't fire here. Closed manually.

Follow-up for the homelab manifest: coilysiren/infrastructure#159 (drop the web container from deploy/repo-recall.yml and adjust the tailnet exposure for an api-only pod).

Landed in https://github.com/coilysiren/repo-recall/commit/d122c14 . Forgejo mirror has pre-existing drift (one commit ahead of GitHub main, unrelated to this work), so the commit-trailer auto-close didn't fire here. Closed manually. Follow-up for the homelab manifest: coilysiren/infrastructure#159 (drop the `web` container from `deploy/repo-recall.yml` and adjust the tailnet exposure for an api-only pod).

coilysiren referenced this issue from a commit

2026-05-28 04:41:23 +00:00

chore: remove the React frontend entirely

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

coilyco-flight-deck/repo-recall#90

No description provided.

Rows
Columns