Updating
ReplayVOD updates in place. Migrations run automatically on start.
cd ~/replayvodgit pull --ff-only # pick up compose / config changesdocker compose --env-file server/.env --profile sqlite pulldocker compose --env-file server/.env --profile sqlite up -dThis pulls the newest published image. Use --profile postgres if your install runs Postgres, or add --build to the up step to rebuild from source instead of pulling.
Run from wherever you cloned the repo:
Set-Location replayvodgit pull --ff-only # pick up compose / config changesdocker compose --env-file server/.env --profile sqlite pulldocker compose --env-file server/.env --profile sqlite up -dThis pulls the newest published image. Use --profile postgres if your install runs Postgres, or add --build to the up step to rebuild from source instead of pulling.
cd replayvodgit pull --ff-onlytask buildAfter updating
Section titled “After updating”- Visit the dashboard once and confirm the Schedules and Live pages still render.
- If you bumped between major versions, skim the GitHub release notes for breaking changes to
server/.envorserver/config.toml.
Rollback
Section titled “Rollback”The recorder rolls back by checking out the previous tag and rebuilding. Database migrations are reversible (.down.sql pairs ship in the binary), but stepping the schema down is a manual operation; in practice rollbacks are easier to do by restoring from a backup than by reverting migrations.