Skip to content
GitHub

Install HotLoop

There are two ways to run a HotLoop product for real: Helm on k3s or any Kubernetes, or Podman with Quadlet on a box that isn’t in a cluster. No Docker, no Compose, and no bare podman run from a shell that dies with the session. A plain podman run is fine to kick the tires, and Flow’s page says so, but it isn’t an install.

You have Use Page
A k3s or Kubernetes cluster Helm k3s and Helm
A Pi, a NUC or a small industrial PC, no cluster Podman Quadlet Podman Quadlet
Either, and you want to know how updates behave The :stable auto-update
Product Latest release Helm Quadlet Start here
HotLoop IoT 4.18.10 Yes Yes Install IoT
HotLoop Edge 4.18.10 Yes Yes Install Edge
HotLoop Gateway 4.18.10 Yes Yes Install the Gateway
HotLoop Edge Relay 4.18.10 Yes Yes Install the Edge Relay
HotLoop Flow 2.2.0 Yes Yes Install Flow
HotLoop Cascade 0.1.2 Yes, no login needed Yes, no login needed, see Cascade with Podman Quadlet Running Cascade

HotLoop IoT, Edge, Gateway and the Edge Relay come out of one tag, in lockstep, so they share a version number. Flow and Cascade have their own. The IoT, Edge and Gateway Quadlet units need Podman 5.0 or newer, and the relay’s unit was run on Podman 4.9.3. Raspberry Pi OS Bookworm ships 4.3, which has no Quadlet at all, so a Pi wants Trixie or newer.

  • Read the write gate. It is the same in every product, and it’s why nothing moves a machine you didn’t arm.
  • Put the database on a USB SSD and not the SD card, if it’s a Pi. History writes all day, every day, and SD cards die of exactly that.
  • Back up the device password key. It isn’t in the database and it isn’t in a backup, so it is part of your data. Backups says how.
  • Take a backup before you move a site up a product or upgrade across a release, and copy it off the box.