Updates and Version Management
Legend releases updates regularly with new features, fixes, and security patches. This guide explains how updates work for self-hosted instances and for managed hosting.
Self-Hosted Updates
Section titled “Self-Hosted Updates”In-App Updates (Update Agent)
Section titled “In-App Updates (Update Agent)”The recommended way to update a self-hosted instance is the Check for Updates button in the Admin panel. It is powered by the update agent, a small companion container deployed during installation (the install script does this automatically).
- Navigate to Admin Panel
- Click Check for Updates
- If an update is available, confirm the update
- The update agent pulls the latest image, recreates the container preserving your configuration, and verifies health
- If the update fails, the agent rolls back to the previous image automatically
If you did not deploy the update agent, the app runs normally but the update button reports the agent as unreachable. You can still update manually as shown below.
Manual Updates
Section titled “Manual Updates”You can update manually at any time by pulling the latest image and recreating the container:
cd /opt/legenddocker compose pulldocker compose up -dStop and remove the existing container, then run it again with the latest image. Use the same environment variables, volumes, and ports as your original docker run command.
Your data is persisted in the mounted volume, so updates do not affect your configuration or entities.
Managed Hosting Updates
Section titled “Managed Hosting Updates”On managed hosting, updates are opt-in and handled by the Legend team. You trigger the update from the Admin panel, and Legend rolls it out safely:
- Opt-in: Updates are never forced; you confirm each update
- Batch rollout: Updates are deployed in batches across instances
- Automatic rollback: If the health check fails after an update, the previous version is restored automatically
- Brief downtime: The instance restarts during the update, so expect a minute or two of downtime
See Managed Hosting Updates for the full details.
Best Practices
Section titled “Best Practices”- Update regularly to receive security patches and fixes
- Check for updates before major changes so your instance is current
- Back up before updating so you can restore if needed. See Backups and Recovery
- Plan for downtime on self-hosted instances; the container restarts during an update
Next Steps
Section titled “Next Steps”- See Backups and Recovery to protect your data before and after updates
- See Managed Hosting to learn about managed instances
- See Troubleshooting for help if an update causes issues