Interfaces & Data
Interfaces
| Interface | Type |
|---|---|
HTTP site (https://aptlantis.net) | Public site |
API proxy at /api (dev proxy to localhost:3001) | Backend routing |
rsync endpoints (rsync://mirrors.aptlantis.net/*) | Mirror distribution |
| Torrent webseeds and magnet links | Distribution |
| Caddy reverse/proxy via docker-compose | Production serving |
| Local CLI/npm scripts (dev, build, start, import-all) | Tooling |
LLM assistant interfaces via llm.instructions in the manifest | Metadata generation |
Produces
- Public JSON catalogs (
aptlantis.distros.json,torrents.json,artifacts.json) - JSON Schemas (
distro.schema.json,torrent.schema.json,dataset.schema.json, etc.) sitemap.xml,robots.txt- Built static site (
dist/) - Mirror-status and dashboard JSON
- Video catalog JSON and transcript artifacts
- UI assets (CSS, JS)
Consumes
- Upstream mirrors via rsync/HTTP
- Torrent files and ISO payloads
- Local filesystem mirror roots (
A:/,B:/paths referenced) - LLM outputs used for metadata generation
- External analytics libraries (Amplitude, Google Analytics)
Depends on
- Caddy (Docker image), Docker/docker-compose
- Node.js/pnpm
- rsync upstreams
- MongoDB
- External analytics providers (Amplitude, Google Tag Manager)
Used by
- The site operator
- Internal dashboard and monitoring UI
- Users retrieving ISO/torrent artifacts via HTTP/rsync
- LLM agents and metadata generation pipelines
Relationship to aptlantis_net
See the aptlantis_net interfaces page — both projects target the same domain with overlapping archive/mirror concepts, and the analyzer captured them as distinct entries without a clear resolution of how they relate.