Store data in separate directory
Lyle Hanson
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.
Chaz Larson
There are only a couple things that Kometa creates which can be deleted without the potential for permanent harm:
- the cache database [typically config.cache]
- the logsdirectory
which you can add to your
.gitignore
.The
overlays
directory contains the clean art that Kometa backed up when it applied overlays, which is required to update or remove overlays and cannot be deleted without putting you in a bad state. You can of course ignore it for git purposes, but if it's lost or deleted you will have to reset art to recover.Similarly, if you have a asset directory in there, you would have created and filled it with images of your choice, so that is most likely not something you want to delete. Again, you can ignore it for git if you want, but that would all qualify as config data.
S
Shariff
I am a proponent of a clear separation of files.
Chaz Larson
Some of the stuff in
/config
can't
be deleted without permanent harm, however, notably the overlay image backup.