Raylux Manual

Appearance

Version 2026.20

Upgrading ​

Before you upgrade ​

  1. Take a backup. This is the step people skip and regret. An upgrade leaves your data directory alone, but a backup is what makes rolling back possible.
  2. Read the release notes for the version you are moving to.
  3. Plan a short outage. Nexus stops while it is replaced, so screens go offline and history has a gap.

Windows ​

Run the newer RayluxSetup-<version>-x64.exe. It detects the installed version, replaces it, and keeps your data directory untouched.

The service is stopped during the replacement and restarted afterwards.

Keep your feature selection

An upgrade keeps the components you originally chose. If you want to add one — say Studio on a machine that only had Nexus — choose Custom during the upgrade.

Check afterwards:

powershell
sc query RayluxNexus
curl.exe http://localhost:8080/health

Linux ​

Installed from the package ​

bash
sudo apt install ./raylux-nexus_<version>_<arch>.deb

Nexus is restarted only if it was already running — an upgrade will not start a gateway you had deliberately stopped. Your data directory is untouched.

Reinstalling the same version needs --reinstall, since apt otherwise sees nothing to do.

Installed from source ​

Rebuild and reinstall, then restart:

bash
cmake --build build --parallel
sudo cmake --install build --prefix /usr/local
sudo systemctl restart raylux-nexus

After upgrading ​

Open Nexus, sign in, and check the top bar (next to the gateway name) reports the new version. Confirm your devices are connected and history is being written before you consider the upgrade done.

Rolling back ​

Uninstall the newer version and install the older one. Your data directory survives both steps.

A newer Nexus may write a configuration an older one refuses

Nexus records a schema version in its configuration file, and it refuses to start on a configuration written by a newer version than itself. This is deliberate — starting anyway would mean silently discarding settings it does not understand.

The consequence is that rolling back is not always as simple as installing the older build: if the newer version upgraded your configuration, you need the backup you took before the upgrade. There is no automatic downgrade path.

Licensing across versions ​

Raylux's version is YEAR.FIX (e.g. 2026.12). A licence entitles you to every release of the calendar year it was bought — its platform generation. Moving from 2026.12 to 2026.13 is an update and your licence carries over. Moving to 2027.1 is a generation change and needs an entitlement that covers that year.

Once the first release of a new year is out, the previous year's line gets fixes only — bug and security fixes, no new features — and only the immediately previous year is maintained. Those fixes keep that year's numbering (a fix to 2026 released in 2027 is 2026.N), so a 2026 licence covers them with no change. This is an intention, not a guarantee — see the licence agreement, §6.4.

Check before you upgrade. ConfigHub → Licence shows a Covers row ("Every release through 2026"). Once a new calendar year has started, the same page warns you if your licence does not cover that year's releases — renew the support contract or buy the upgrade, then use Update licence, before installing the new version.

A Nexus instance upgraded past its entitlement does not refuse to start. It runs in the unlicensed tier and says why on its licence page, so you can see exactly what happened and roll back or update the licence.