2 Data Backup and Upgrades

Data Backup and Recovery

All business data lives in the single file /opt/lynx-board/data/lynx-board.db (the port record port.json sits alongside); nothing is scattered elsewhere:

# Backup
sudo systemctl stop lynx-board
sudo cp /opt/lynx-board/data/lynx-board.db /var/backups/lynx-board-$(date +%F).db
sudo systemctl start lynx-board

# Restore
sudo systemctl stop lynx-board
sudo cp /var/backups/lynx-board-YYYY-MM-DD.db /opt/lynx-board/data/lynx-board.db
sudo systemctl start lynx-board

• Copying after stopping the service guarantees file integrity; keep backups off-site and mind their access permissions.
• Migrating to a new device: once the new device is ready, stop the service, copy the data file into the same path, start and verify by logging in.
• Directory conventions: inside /opt/lynx-board, do not touch anything except data/ (upgrades replace the rest wholesale); configuration lives in /etc/lynx-board/env and reloads on restart.

Upgrades

Upgrading is the most common later operation — one command:

sudo dpkg -i lynx-board_<new-version>_crypt_arm64.deb

The process runs automatically: stop the old service → back up the old program → deploy the new version → start and verify. Data and configuration are preserved throughout — boards, member accounts, login states and reminder settings are untouched; any failed check rolls back to the pre-upgrade version with the service still running.

Confirm after upgrading:

systemctl status lynx-board     # should be active (running)

• Upgrading from the old lynx-kanban: after installing the new package, disable and remove the old lynx-kanban service; to keep data, copy the old data file to /opt/lynx-board/data/lynx-board.db; finally remove /opt/lynx-kanban and confirm only lynx-board listens on the port.