Rather than storing assets, cache data, and logs under /config, use a dedicated /data directory for anything generated by PMM after startup.

This allows a clear separation of files I configure to run the app (/config/config.yml) and data that can be tracked, backed up, or deleted separately without permanent harm.

For example, running PMM in docker-compose alongside plex and other apps in a git-tracked repository, a separate data directory allows me to add /data to .gitignore and version control only changes to /config. It also allows me to optionally volume mount a /data directory if I want to persist it outside the container lifetime, or optionally delete the whole directory to start fresh without re-creating the config file.