Updates & Rollback
Updating
Section titled “Updating”curl -fsSL https://github.com/grand2-products/echolore/releases/latest/download/update.sh | sudo bashTo update to a specific version:
curl -fsSL https://github.com/grand2-products/echolore/releases/latest/download/update.sh | sudo bash -s -- --version v0.2.0update.sh automatically:
- Checks the version (no-op if current; bypass with
--force) - Backs up
.envanddocker-compose.yml - Downloads and verifies the new compose file
- Pulls the new images
- Runs database migrations
- Restarts services
- Runs health checks
- Rolls back automatically on failure (migration failures or health check timeouts restore the previous version)
Version pinning
Section titled “Version pinning”Pin a version in .env via ECHOLORE_VERSION (default latest). Updates reconcile against the tags in docker-compose.production.yml.
Manual rollback
Section titled “Manual rollback”cd /opt/echolorels -la .env.backup.*cp .env.backup.20260316120000 .envdocker compose pulldocker compose up -d --remove-orphansUpdating from the admin console
Section titled “Updating from the admin console”The admin console → System shows the current version and can run updates (using the same update mechanism under the hood).
Release cycle
Section titled “Release cycle”- Releases use semantic versioning (
v0.1.0style tags) - Each release ships a GitHub Release plus container images on GHCR (tagged
v0.1.0,0.1,latest) - Breaking changes include migration notes in the release notes