Upgrading

Versions

The images are tagged:

Tag	What it is
latest	The last release (the default)
edge	The main branch, built on every change
0.1.0, …	A given release

Pinning a release

Set the version for all five services at once in .env:

HERON_VERSION=0.1.0

Or pin services one by one in a docker-compose.override.yml next to docker-compose.yml. Compose reads it automatically, and git ignores it:

services:
  heron-api:
    image: ghcr.io/dehy/heron-api:0.1.0
  heron-analyzer:
    image: ghcr.io/dehy/heron-analyzer:0.1.0
  heron-librarian:
    image: ghcr.io/dehy/heron-librarian:0.1.0
  heron-engine:
    image: ghcr.io/dehy/heron-engine:0.1.0
  heron-web:
    image: ghcr.io/dehy/heron-web:0.1.0

Upgrading

Change the version (or keep latest), then:

docker compose pull
docker compose up -d --wait

Database migrations run when heron-api starts. The engine saves its queue and the position of the track on air, so a restart resumes where it was: a clean restart keeps the exact position.

Caution

Heron is in early development: read the release notes before upgrading, and back up the database (the mariadb-data volume) first.

Re-analysis after an upgrade

When a release improves the analysis, every track is analyzed again once, in the background. Tracks keep playing with their previous analysis in the meantime.