Interfaces & Data

Interfaces

Interface	Type
Web UI (React, Vite)	Frontend
API server (Node HTTP, :8788)	Backend
MongoDB (mongodb://localhost:27015/)	Database
Reverse proxy (Caddy in Docker, :8787)	Production serving
Static public assets (public/)	Static files
Dev proxy (/api → http://localhost:8788)	Local dev routing

Produces

• Public/static site assets
• public/manifest.json, public/robots.txt, public/humans.txt
• public/data/*.json and *.ndjson — exported datasets
• Terminal theme JSONs
• PGP public key
• QA/doc pages (public/docs/page.qa.json)

Consumes

• MongoDB collections (core, pages, ecosystems)
• Local or remote video URLs (for the video player)
• rsync/archival input (ecosystem import scripts)
• Reverse-proxy routing via Caddy

Depends on

• Node.js, pnpm/npm, Vite
• MongoDB
• Caddy (Docker), Docker
• Tailwind CSS

Used by

• The operator, directly
• Internal AI agents (per documented orchestration in CLAUDE.md)
• Archival crawlers and external indexers — explicitly welcomed via robots.txt
• Internal dashboards and export pipelines

Relationship to the "aptlantis" project

This project and the separately-tracked aptlantis project both target the aptlantis.net domain and both describe themselves as archive/mirror sites, but the analyzer captured them as two distinct entries with different emphases — aptlantis_net leans toward ecosystem reference pages and a Linux genealogy visualizer, while aptlantis leans toward the ISO/torrent mirror and TempleOS video catalog. Whether these are sequential (one replacing the other), parallel repos, or two views of the same evolving codebase isn't resolved by the available evidence — worth reconciling directly with the source rather than assuming either way.