Update

Update to latest

docker compose pull app
docker compose up -d app

Database schema migrations (the versioned V1 -> V35 system) apply automatically on startup. Data in Docker volumes is preserved.

Pin a version

Replace latest in docker-compose.yml with a tag:

image: ghcr.io/mlab-sh/tprm.mlab.sh:1.5.1

Upgrading to 1.5.1

• LICENSE_KEY is required, on Free too. Without it, or without a valid license, the instance is paused. Copy your key from mlab.sh.
• One place per instance. Each running instance holds a place on the license (1 by default). Run more instances than places and the extra ones are paused. See Licensing.
• Migrations V22 to V35 apply on startup. Keep your volumes: an instance recreated with empty volumes gets a new instance id and needs a free place.

ClickHouse version

Keep ClickHouse pinned to 26.8, as in the installation docker-compose.yml. Do not use clickhouse/clickhouse-server:latest: ClickHouse 26.9 answers tprm.mlab.sh's client with empty results and closes the connection after every query, so activity, statistics and jobs come back empty and ClickHouse migrations replay on every boot.

If your instance already pulled 26.9, back up the clickhouse_data volume, set the image to clickhouse/clickhouse-server:26.8, then docker compose up -d clickhouse app. ClickHouse does not promise that an older version reads data written by a newer one, so if it refuses to start, restore the volume and start from an empty one: what tprm.mlab.sh keeps in ClickHouse is its activity log.

Rollback

If a release introduces a regression: re-pin to the previous tag, then docker compose up -d app. Schema rollbacks are not automatic - restore the MySQL/ClickHouse volumes from backup if a migration is involved.

Release notifications

Subscribe to the changelog. Major releases announce breaking changes at least one minor version ahead.