This is a guide/notes for anyone planning to upgrade to 10.x, and is struggling with additional docker layer
Document assumes you replace cyberdrop-dl with your full docker run command
Prep
Backup your Appdata volume, just in case but also as a reference for config upgrade
Docker
Recommended for docker setup, otherwise everything gets scattered around $HOME.
If you want to keep everything under Appdata add docker environment variable
CDL_APPDATA_FOLDER=AppData
Config upgrade
All config has changed, follow upstream instructions on how to migrate. eg:
Generate new config
Save output to a new file. Fix it to your liking using upstream docs. Move to actual config location, which can be found via:
cyberdrop-dl config file
# ie: AppData/config.yaml
Database upgrade
Database needs to be manually upgraded. CDL will refuse to start if using old version. Follow upstream instructions, eg:
cyberdrop-dl database transfer --database-file AppData/Cache/cyberdrop.db
Migrate upgraded database into correct location, eg:
cyberdrop-dl database file
# ie: AppData/cyberdrop.db
cp AppData/Cache/cyberdrop.db TO_PATH_ABOVE
Cleanup
Move/remove all old config, otherwise will warn about outdated/migration each run
rm -rf AppData/{Configs,Cache,Logs,Cookies}
Final state
Minimal volume structure should now look like
AppData/config.yaml
AppData/URLs.txt
AppData/cyberdrop.db
Downloading
If you just want to download the --download option has changed, and input file must be provided every time
cyberdrop-dl download -i AppData/URLs.txt
This is a guide/notes for anyone planning to upgrade to 10.x, and is struggling with additional docker layer
Document assumes you replace
cyberdrop-dlwith your full docker run commandPrep
Backup your Appdata volume, just in case but also as a reference for config upgrade
Docker
Recommended for docker setup, otherwise everything gets scattered around
$HOME.If you want to keep everything under Appdata add docker environment variable
Config upgrade
All config has changed, follow upstream instructions on how to migrate. eg:
Generate new config
Save output to a new file. Fix it to your liking using upstream docs. Move to actual config location, which can be found via:
Database upgrade
Database needs to be manually upgraded. CDL will refuse to start if using old version. Follow upstream instructions, eg:
Migrate upgraded database into correct location, eg:
Cleanup
Move/remove all old config, otherwise will warn about outdated/migration each run
Final state
Minimal volume structure should now look like
Downloading
If you just want to download the
--downloadoption has changed, and input file must be provided every time