Platform Bundle And Installer Architecture
See how the platform release repo assembles the bundle and how the installer, supervisor, and release metadata fit together.
Platform Bundle And Installer Architecture
The platform release repo owns the self-hosted packaging layer.
Bundle contents
The bundle includes:
- saved API and web images
- compose files for setup and installed runtime variants
- nginx configs for HTTP, TLS, and external TLS scenarios
- installer and status helper scripts
- release manifest and checksums
Host-side orchestration
Not all control-plane behavior lives inside containers. Host-side scripts own:
- initial install
- runtime promotion
- control-plane update request processing
- cert renewal timer installation
- current bundle symlink management
Release metadata
The published release manifest includes platformVersion, releaseId,
releasedAt, and bundle integrity data. releaseId is the operationally
important identity for self-update.
Control-plane self-update path
The API writes a host-side update request when a platform admin clicks
Download latest update or Apply prepared update.
The supervisor reads that request and invokes the control-plane update helper on the host.
Download prepares a new extracted release under
/opt/noderax-platform/releases/<releaseId>.
Apply switches the current symlink, recreates services, verifies health,
and rolls back if the new runtime fails verification.
Agent Architecture
Understand the Go agent runtime, its connection to the control plane, and how it participates in node install, metrics, tasks, and terminals.
Realtime And HA Data Flow
Trace the HA runtime path for websocket transport, workspace fanout, Redis pubsub bridging, and immediate event emission.