TAPPaaS Module Dependency Model¶

Computed from every module's <module>.json (dependsOn: "provider:service"). Three views: the platform plumbing every module uses, the application topology worth drawing, and the complete per-module reference.

Generated: 2026-10-06 by generate-module-dependencies.sh from 26 modules / 105 dependencies — do not edit by hand.

1. Platform plumbing¶

These foundation services are consumed near-universally; drawing them would bury the interesting structure. A module uses them unless its entry in the reference below says otherwise.

2. Application topology¶

Everything that is not plumbing — the dependencies that shape the platform. Multiple services between the same pair are merged into one labeled edge; providers marked (external) have no module in this repo yet.

graph TD
    coturn -->|"fileservice"| nextcloud
    coturn -->|"nat"| network
    euro-office -->|"fileservice"| nextcloud
    hass -->|"audio, airplay"| sonos
    hass -->|"rtsp"| reolink
    hass -->|"ui, discovery, modbus"| alfen
    jellyfin -->|"nfs"| storage
    netbird-client -->|"debian"| templates
    nextcloud-hpb -->|"fileservice"| nextcloud
    nextcloud-hpb -->|"turn"| coturn
    openwebui -->|"models"| litellm
    vllm-amd -->|"lxc"| cluster
    windows-server -->|"windows"| templates
    alfen["alfen (external)"]:::ext
    classDef ext stroke-dasharray: 5 5
    reolink["reolink (external)"]:::ext
    sonos["sonos (external)"]:::ext

3. Complete reference¶

Every dependency of every module, verbatim from the json contracts.