openmixerGitHub →

Installing openmixer

openmixer installs from RPM packages with dnf. Nothing here assumes a development checkout: the packages carry the engine, the web surface, the systemd units and a default configuration that boots a working console on first start.

Read these in order the first time. If you would rather flash a disk image than run dnf yourself, start with the installable console image instead of step 1 — one signed repository feeds both paths.

  1. Packages — what each package contains, the install order of the three-repo stack (libreac → reac-pw → openmixer), and the one command that installs a mixer without a stagebox.
  2. Services — the two systemd user units, why lingering is required, and how to prove they survive a reboot.
  3. First boot — what a fresh install does when it starts, where to point the browser, and the checks that tell you the install is healthy.
  4. Your first session — a walkthrough from silence to one channel audible in the main mix.
  5. Trusting the console's certificate — the one step every device other than the console itself needs before a browser will open the surface without a warning, per platform, including the two that fail silently.
  6. Upgrading — what dnf upgrade does and does not restart, and how session files survive a version change.
  7. The bootable image — the bootc alternative to installing RPMs by hand, and how a console pulls it while the image stays private.

What you need

  • A Fedora host (the packages are built and tested against Fedora 42; Fedora 41 builds clean as well) with PipeWire running in the operator's user session.
  • Node 22 or newer — pulled in as a package dependency, not something you install by hand.
  • nginx, pulled in by openmixer-web-ui.
  • For a REAC stagebox: a dedicated wired network interface. See the hardware guide before you cable anything — the NIC choice is the single most common cause of bad audio.

Where to go afterwards