Upgrades and Maintenance

Keeping your instance current gets you fixes, new features, and security updates. Because Legend is self-hosted, you choose when to upgrade. A little routine keeps it low-risk.

Before you upgrade

Read the release notes for the version you are moving to, and note anything that requires action.
Take a fresh backup of the database and uploaded files, as covered in Backup and Restore.
If you can, test the upgrade in a staging copy before touching production.

Performing the upgrade

With a container deployment, upgrading is a matter of moving to the new image tag and letting the stack recreate the application. Any database migrations that ship with the release run as part of startup, which is why a fresh backup matters.

Update the image tag in your Docker Compose file to the new version.
Pull the new image and recreate the application container.
Watch the logs until the application reports it is ready.

docker compose pull legend
docker compose up -d legend
docker compose logs -f legend

After upgrading

Sign in and confirm the map loads and search works.
Spot-check a few Agents and Landmarks and their relationships.
Confirm your license still shows the correct tier.

Routine maintenance

Keep backups running on a schedule and test a restore periodically.
Keep the host and its base images patched.
Renew TLS certificates automatically where your proxy supports it.
Review users, roles, and ownership from time to time so the map and its access stay accurate.

If an upgrade goes wrong, the recovery path is to roll back to the previous image tag and, if a migration changed the database, restore from the backup you took beforehand.