Fresh Install
Run the installer-managed bundle from a clean host and understand what the install command provisions for you.
Fresh Install
The supported self-hosted entry point is:
curl -fsSL https://cdn.noderax.net/noderax-platform/install.sh | sudo bashThe supported path is the installer-managed bundle. The docs do not treat the compose files as a standalone product surface detached from the host-side installer and supervisor flow.
What the installer does
The installer:
- downloads the latest published bundle from the CDN
- verifies checksums
- extracts the bundle under
/opt/noderax-platform - writes runtime config under
/etc/noderax-platform - uses
/var/lib/noderax-platformas persistent state root - starts the setup stack with bundled nginx, PostgreSQL, Redis, API, web, and certbot
Host prerequisites
The current installer targets a clean Linux VM or server with:
- outbound internet access for bundle download, package install, and optional ACME issuance
- root or
sudoaccess - public reachability on ports
80and443if you want automatic HTTPS
The installer handles its own common toolchain requirements such as Docker,
Docker Compose, curl, jq, openssl, tar, and zstd.
Install path variants
Use a public origin such as https://dash.example.com. The installer will
preflight ACME routing on port 80, request the certificate, switch nginx
into TLS mode, and install the renewal timer.
Use an http:// origin when you do not have a DNS name yet. The installer
treats IP-based installs as non-ACME flows and keeps the setup surface
reachable without forcing a broken TLS path.
First successful install
Provide a public origin such as https://dash.example.com.
If the origin is a domain, let the installer provision automatic HTTPS.
Wait for the setup stack to come up and for /setup to respond.
Continue in the setup UI to finish bootstrap and runtime promotion.
After the installer exits successfully
Open /setup
Finish the first-run setup flow and write the final installed state.
Understand runtime promotion
See how `api-setup` is replaced by `api-a`, `api-b`, `web`, and nginx routing in installed mode.
Troubleshoot the host
Use the status helper, route probes, and service state to diagnose install failures.
Updates Center
Understand the split Updates Center with separate control-plane and agent update surfaces, plus the freeze modal shown during control-plane apply.
First-Run Setup Flow
Understand what happens in /setup, what the setup API validates, and what changes when the control plane is promoted into the installed runtime.