Install on Linux
The Linux source node runs as a systemd service and starts automatically on boot. It uses a single pre-built binary — no Python runtime or virtual environment needed. It supports self-updating: new versions (engine packs) are applied automatically when signalled by the Hub.
Prefer containers? The source node also ships as a container image with a Helm chart — same engines, same credentials.
Prerequisites
Section titled “Prerequisites”- Linux with systemd (Ubuntu/Debian)
curlinstalled — the installer auto-installs it on Debian/Ubuntu- Network connectivity to the Hub host and port (outbound TCP — no inbound rules needed)
- Network connectivity to the controller URL (for downloading the binary and updates)
sudoprivileges- Your node’s Client ID and Client Secret — shown once when you create the node (or regenerate its secret) on the Nodes screen (see the Nodes reference)
Quick Install
Section titled “Quick Install”The installer script handles everything: creating the service user, downloading the binary, writing the systemd unit, and enabling the service.
sudo ./install.sh --client-secret <your-client-secret>Run this from the folder containing the installer package (the zip with install.sh and the binary), or download the binary from your controller:
sudo ./install.sh --controller-url https://<controller-url> --client-secret <your-client-secret>Step-by-Step Installation
Section titled “Step-by-Step Installation”Step 1 — Obtain the installer
Section titled “Step 1 — Obtain the installer”Get the installer package from your platform administrator. It contains install.sh, uninstall.sh, and the nexomatic-source-node binary (the binary is also fetchable from the controller’s downloads API when you pass --controller-url).
Step 2 — Run the installer
Section titled “Step 2 — Run the installer”chmod +x install.shsudo ./install.sh --controller-url https://<controller-url> --client-secret <your-client-secret>The installer:
- Installs
curlif missing - Creates the
nexomaticservice user - Installs the binary to
/opt/nexomatic-source-node/ - Writes the
nexomatic-source-node.servicesystemd unit with your configuration - Enables the service and offers to start it
Useful installer options:
| Option | Meaning |
|---|---|
--hub-host / --hub-port / --no-hub-tls | Hub endpoint (defaults to the platform’s public hub with TLS) |
--client-id / --client-secret | Node credentials from the Nodes screen (create a source node there first) |
--node-version | Version string written to the install’s VERSION file |
--update-base-url | Base URL for self-update packages |
Step 3 — Verify
Section titled “Step 3 — Verify”sudo systemctl status nexomatic-source-nodesudo journalctl -u nexomatic-source-node -fA healthy start logs Registered node … followed by heartbeats. Once connected, your self-hosted sources appear on the Sources screen and the node’s workers show up in the journal as Spawned worker (type=…) lines.
Uninstalling
Section titled “Uninstalling”sudo /opt/nexomatic-source-node/uninstall.shPass --keep-data to preserve the node’s data directory (assignments, cursors, node identity).