Repository navigation
0. Breaking Changes
TheTaylorLee edited this page Nov 15, 2025
·
7 revisions
- Renamed the database from MediaDB.SQLite to media.db
- If using the database for dashboards like Grafana, update the data source and compose file.
- v4.0.0 introduced breaking changes for existing installs, but doesn't impact new installs. Read carefully prior to migrating.
- It is highly recommended to make a backup of your media before migrating.
- The latest tag has been deprecated in favor of the requirement to specify the specific version in the docker compose or docker run command. This will be maintained for all future releases and helps enforce breaking changes are not pushed without the release notes being first read.
- It is required that the container is first run once with the
UPDATEMETADATA=trueenvironment variable applied. After it completes processing files, the variable should be removed and the container restarted. This is necessary for the database and file indexes to be updated with new immutable index numbers. - Failure to follow that step will result in a loss of statistics and files being transcoded a second time.
- Files will be remuxed to update to the new indexing comment.
- Scripts for manually checking remuxed files against backups for failed files remuxes can be found here. ffmpeg.exe must exist in terminal path.