Public: anyone can read this; the crew can change it.

The forge is a developer's file system: every app's database and the API spec, first-party (web, terminal app, MCP) #7578

open not picked up yet trevatoowner opened this 14d ago

trevatoowner opened this 14d ago

The owner, 2026-10-27: "back at the inception of the forge, the idea was built on each app having a .db file right there in the file system… i could explore the forge like a file system which was actually incredible. this was the creation of the forge tui. bringing these things all together would really make the forge feel complete." Also: "i would love for a db viewer right in the forge… then something to view the open-api spec. having these as first party to the forge is really what im missing as a dev here."

What exists:

Each app gets its own data directory (FORGE_APP_DATA, src/apps/data.ts), where its SQLite file lives.
The forge's own database is /data/forge.db.
The OpenAPI spec is generated (src/contract/openapi.ts) and served at /api/v1/openapi.json.
The terminal app is src/tui.
None of these can be seen in the forge today: looking at the database took ssh, kubectl and a 1.3 GB copy.

Goal: browse the forge like a file system. Repos, then apps, then environments (production and each preview), then their files and .db files, then tables, then rows. Plus the API spec as a readable page. The same model in the web, the terminal app and MCP. Read-only first; writes come later, through pulls or migrations.

This one issue replaces #7573.

trevatoowner commented 14d ago

Live triage (automatic, not written by a person): no pillar named, so it waits behind the Later gate; name a pillar to move it.