Bare-Metal Install
How the standalone installer brings up the whole Elchi stack as systemd services on 1, 2 or 3+ Linux VMs, with no Docker and no Kubernetes required.
Prerequisites
OS, hardware, network and SSH requirements for the bare-metal Elchi installer, checked before it brings the stack up as systemd services on your VMs.
Quick Start
One-command bare-metal Elchi installs: a single all-in-one VM or a 3-VM cluster, with key-based or interactively bootstrapped SSH between the nodes.
install.sh — full flag reference
Complete reference for every install.sh flag — topology, SSH, versioning, TLS, MongoDB, VictoriaMetrics, Grafana, GSLB, backend, and op-mode.
upgrade.sh — version-diff upgrade
Version-diff upgrades with hash-based reconcile, additive or declarative variant changes, health gate, and per-binary rollback.
uninstall.sh — remove the stack
Non-destructive uninstall by default, cluster-wide fan-out from M1, and opt-in purge flags for data, packages, and secrets.
/etc/elchi/validate.sh — per-node post-install audit
Read-only per-node audit script that checks systemd, ports, service health, Envoy admin, config integrity, and system tuning.
elchi-stack helper
Reference for elchi-stack, the helper on every bare-metal Elchi node: status, logs, add-node, MongoDB and ClickHouse checks, secrets, TLS info and verify.
Port atlas
Every port the bare-metal Elchi stack listens on, per service and per node role, and whether it binds loopback or all interfaces, for your firewall rules.
Topology
How components distribute across 1, 2, and 3+ VM clusters — Mongo RS, per-node OTel and collector, ClickHouse replication, and the M1 storage tier.
Production hardening (kernel + systemd)
The kernel sysctl baseline, MongoDB systemd drop-in, per-service systemd hardening set, and preflight RAM/swap checks applied by every install.
Supported distros + idempotency
The Linux distributions the bare-metal Elchi installer supports, why older releases are dropped, and how hash-based reconcile makes reruns idempotent.