Raylux Nexus

Appearance

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 ​

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 and check the Overview page 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 ​

A licence entitles you to updates within its platform generation — the first two numbers of the version. Moving from 1.0.4 to 1.0.9 is an update and your licence carries over. Moving to 1.1.0 is a generation change and needs an entitlement that covers it.

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.