TAPPaaS

templates

Primary audience: TAPPaaS admin.

The TAPPaaS VM base images — prebuilt, preconfigured templates (NixOS today, Windows Server as an add-on) that every other TAPPaaS VM is cloned from, plus the per-OS service hooks that keep consumer VMs configured.

What you get

Capability Access from How
NixOS VM template (tappaas-nixos, VMID 8080) consumer modules dependsOn: ["templates:nixos"]; module json imageType: "clone", image: "8080"
Windows Server 2025 template (tappaas-winserver, VMID 8081) consumer modules dependsOn: ["templates:windows"] — see winserver/README.md
NixOS config apply on consumer VMs module lifecycle services/nixos/*.sh hooks (nixos-rebuild on the consumer VM)
Debian/Ubuntu config apply on consumer VMs module lifecycle services/debian/*.sh hooks
Windows baseline (OOBE, disk, updates, RDP, SSH) module lifecycle services/windows/*.sh hooks — see services/windows/README.md
Version-gated template refresh TAPPaaS admin module-manager module update templates (only downloads when the pinned version changes)

What is not included

Requirements

Dependencies

Depends on Purpose
cluster:vm Creates the template VMs (8080/8081) on the cluster

(templates.json itself declares no dependsOn; the per-template build configs tappaas-nixos.json / tappaas-winserver.json depend on cluster:vm.)

For installation steps see INSTALL.md.

Design and implementation detail: DESIGN.md. Test coverage: TEST.md.