1 Version Upgrades

New versions arrive as packages from the supplier, and upgrading is one command. This chapter covers preparation, what survives an upgrade, post-upgrade checks and rollback.

Before Upgrading

Confirm the package is the official new version, record the current version and key settings (port, data directory, administrator account), and ensure important data is backed up. Pick a business trough and announce in advance that "the service will be interrupted for about a minute".

Performing the Upgrade

Upload the package to the device or an accessible directory and run sudo dpkg -i lynxdrive_new-version_arm64.deb. The system replaces the program and restarts the service automatically — no reinstall, no reconfiguration.

What Survives an Upgrade

Accounts and permissions, share records, access port, data directory and every file remain. The upgrade swaps only the program itself; your directory structure and workflow stay the same.

Post-Upgrade Checks

Three steps: run lynxdrive-ctl status and confirm both the service and watchdog are running with a healthy port probe; open the page in a browser and hard-refresh (Ctrl+F5) so styles and scripts load the new version; spot-check upload and download in a common directory.

Rollback

Keep the previous package and rerun the same command with it to roll back. Rollback restarts the service too, keeping data and configuration. Run the same checks afterwards.

Three Prohibitions

Never hand-replace program files — system state diverges from the install records; never overlay the new directory structure with an old package; never upgrade before the data backup completes. Conservative as they look, these three rules prevent nine out of ten upgrade incidents.