This tool with convert Ceres files and database entries to the new Ganymede format. All of this can be done manually if you prefer to do so.
This tool will log into Ceres and get all the VODs in the database. It will then create a new entry in Ganymede for each VOD. Once the database entry has been created, all VOD files will be renamed to match the new naming convention used by Ganymede.
docker-compose.yml
and update the Ceres host, username, password along with the Ganymede host, username and password. Keep SHOULD_RENAME
and SHOULD_DELETE
commented out for now. If set to true it will rename/delete files. It is best to run a database to database migration test run first before renaming and then delete files.volumes
sections. This should match the folder you have in your Ceres or Ganymede compose files.docker compose up
command.At this point the migration tool should be running and adding the Ceres VOD DB entries into Ganymede. If any errors appear now is the time to fix them as once you run the container with SHOULD_RENAME
set to true, you cannot run it again.
Within the ./data
folder resides a log file of the migration and any errors.
If you need to make changes and run another dry run, delete all VODs in the Ganymede database. The script will duplicate entries if VODs are not first removed due to how the ID for each vod is generated.
If you are satisfied and want to rename VOD files follow the below steps. Once SHOULD_RENAME
is set to true, you cannot run the migration tool again!
SHOULD_RENAME
variable in the docker-compose.yml
file.docker compose up
command.It is likely a few files will error out because they could not be found. Take a look at the ./data/log.log
file and manually fix any rename errors.
Once you are done with everything (test by playing a few VODs), you can start the container with SHOULD_DELETE
set to true. WARNING: It will delete every old ceres created folders, make sure everything was moved and renamed correctly in the newly created folders!