Skip to main content

Operations

Production deployment (docker-compose)​

# Production docker-compose.yml for final location (A:/aptlantis)
services:
  mongodb:
    image: mongodb/mongodb-community-server:latest
    ports: ["27015:27017"]

  astro:                        # Astro Node.js server, SSR/hybrid mode
    build:
      context: A:/aptlantis
      dockerfile: Dockerfile
    environment:
      - NODE_ENV=production
      - HOST=0.0.0.0
      - PORT=4321

  # + Caddy reverse proxy (production entrypoint)

Local development​

Per the analyzer's evidence: dev, build, start, and import-all npm scripts are present (React/Vite-shaped tooling), alongside the Astro-based production compose file above — see the framework note on the Overview page.

Content pipeline​

  1. Content types are defined as JSON Schemas under public/schemas/
  2. Site manifest (AptlantsSchema.toml) includes llm.instructions driving automated metadata generation/reconstruction for archive entries
  3. Public JSON catalogs (aptlantis.distros.json, torrents.json, artifacts.json) are generated from schema + curated data
  4. public/data/mirror-status.json is updated to reflect live per-distro sync state

Known gap​

No formal WDS-style deployment record, release notes, or accessibility audit was found in the analyzer's evidence, despite this being a production site with real traffic-facing infrastructure (Caddy, Docker, MongoDB). See Roadmap.