Where Does Medusa Store Config and Database?
Medusa keeps config.ini with sickbeard.db and caches in one data dir, mounted at /config in Docker.
Last updated
Medusa keeps everything in one data directory. The config file, the main database with its legacy sickbeard name, cache databases and logs all sit together. Docker images mount that tree at /config, so the host side is whatever the volume maps.
Native installs place the same tree wherever the app launches, which is why guides disagree: check Help and Info inside the app for the live Config, Database, Cache and Log paths. This is the Python TV manager, not the commerce platform sharing the name. Back up the INI plus the main database together.
Where Medusa stores this, by platform
/config (Docker volume)
Holds config.ini, sickbeard.db, cache.db, failed.db plus logs and cache trees. Native installs use the launch dir instead; read Help and Info for live paths. Media mounts for downloads, tv and anime sit outside this tree.
Frequently asked questions
What do I back up for Medusa?
Copy config.ini with sickbeard.db and the Cache folder from the data dir with the app stopped. That trio carries settings, shows and artwork. Media libraries live outside and need their own backup.
Is this the Medusa commerce platform?
No. This is the Python TV download manager with config.ini and sickbeard.db. The commerce tool uses medusa-config.ts and a different stack entirely. Check for sickbeard.db to confirm which one you run.
Where are Medusa logs?
In the logs folder inside the same data dir, path shown under Help and Info. Log verbosity configures in the app. Include recent logs when reporting failed searches or snatch errors.
Notice an outdated path? Let us know.