trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
P12 Files and data
54 of 60 done
6 open · 43 merged in 7 days · moved
About 1 day at this week's pace: 44 closed in 7 days, 6 open.
Limbs
Blocked
Merged in 7 days
- A .har file in a repository opens as a request waterfall: method, status, size and time per row, drawn on the server
- A GraphQL schema (`.graphql`, `.gql`) opens as its types: each type, input and enum with its fields and their types
- A `package.json` opens as its manifest: name and version, scripts, dependencies with their ranges, engines
42 more merged
- A `compose.yaml` or `docker-compose.yml` opens as its services: image or build, ports, volumes, depends_on and environment names
- A GitHub Actions workflow (`.github/workflows/*.yml`) opens as its jobs: triggers, then each job's runner, needs and steps
- A `Makefile` opens as its targets: each target with its prerequisites and recipe, phony ones marked
- A `Dockerfile` opens as its stages: base image, ports, and each instruction as one row
- A `.sql` file in a repository opens as its schema: each CREATE TABLE as its columns, other statements one per row
- A `.env.example` in a repository opens as the variables an app needs: name, example value and its comment per row
- An OpenAPI document in a repository opens as its operations: method, path and summary per row, grouped by tag
- An lcov coverage file in a repository opens as a table: each source file's line and branch coverage, worst first, linked to the file
- A JUnit XML test report in a repository opens as its results: pass, fail and skip counts, then each failing case with its message
- Displays: 2.3 s to list two rows and no word on what a display is — make it fast and clear, or fold it into boards
- A .sarif file in a repository opens as its findings: rule, level, file and line, and message per row
- An .eml file in a repository opens as a message: From, To, Subject, Date and the plain-text body, drawn on the server
- The terminal workspace opens .ipynb, .jsonl and .log files the way the browser does, with `s` for source
- A markdown file's relative images and links resolve inside the same repository at the same ref
- An .html file in a repository previews as a page in a sandboxed frame, with Source one tap away
- A sliced .gcode file shows its toolpath one layer at a time, drawn on the server
- A .3mf print project opens in the 3D view, like an STL
- Each app's prints are capped per day and logged on the device page
- An app granted the printer prints a PDF through the forge, and reaches nothing else on the LAN
- A read-only work repo shows on its owner's profile as work (read-only) with its last fetch and why a fetch failed
- A read-only mirror leaves no trace for a stranger or the crew: pages, changelog, Talk, search, briefs
- The owner declares the LAN printer and sees its model, state and supplies
- A contacts file (.vcf) in a repository renders as a list of its contacts, nothing run
- A GeoJSON file renders as an outline of its features and a table of their properties
- A Jupyter notebook (.ipynb) renders as its cells and outputs, nothing run
- A repository mirrored from a read-only origin is private to its owner everywhere
- An origin can be connected read-only, and every write-through path refuses it
- A GPS track (.gpx) in a repository renders as its route drawn as an outline, with distance and climb
- A calendar file (.ics) in a repository renders as a list of its events
- The terminal app browses the forge like a file system: repos → apps → environments → .db files → tables → rows, with a SQL prompt and vim keys
- A font file (ttf, otf, woff, woff2) in a repository renders as a specimen
- A .patch or .diff file in a repository renders as a coloured diff, the same way a pull's diff does
- MCP and API for data: a `data` tool and /api/v1/…/data endpoints, so agents and editors browse what a person can
- A SQLite file committed to a repository (.db, .sqlite, .sqlite3) renders as its tables and their first rows, read-only
- A log file with terminal colours (.log, .ansi) renders in colour, with no escape codes shown
- A JSON Lines file (.jsonl, .ndjson) renders as a table, as CSV does
- A subtitle file (.srt, .vtt) renders as a timed transcript
- A Data tab: every app's databases in the web, and the forge's own at /admin/data — table list, sortable paged rows, filters, a read-only SQL box
- A .zip, .tar or .tar.gz file in a repository shows the list of what is inside it, without unpacking it
- Data browser core: read any SQLite file a viewer may see — the forge's own (admins) and each app's per environment (its writers) — tables, rows, read-only SQL, secrets masked
- Data explorer: a model fallback for sentences the rules cannot read
- The data explorer is easy: start from a question, not from a query form