VTunedocs

Operations

Upgrades and rollback#

Upgrade only between published, pinned versions. Read the release notes, take a complete backup, and retain the prior image until the new version passes verification.

Upgrade#

  1. Confirm the current instance is healthy and record the running version.
  2. Stop new uploads and take a volume snapshot.
  3. Pin the new version in compose.release.yaml or your deployment override.
  4. Pull and start the service.
  5. Review startup and migration logs privately.
  6. Verify OAuth, library access, group sharing, upload, and Discord playback.
docker compose -f compose.release.yaml pull
docker compose -f compose.release.yaml up -d
docker compose -f compose.release.yaml logs --tail=150 vtune

Rollback#

If a migration ran, stop the service and restore the pre-upgrade volume snapshot before starting the prior image. Do not run old application code against a newly migrated database unless the release notes explicitly permit it.

Recovery evidence#

Record the release versions, backup identifier, start time, migration result, smoke checks, and rollback decision in your operator log. Treat successful image pull and successful application verification as separate milestones.