atomicdecay

This was driving me crazy too and I came to the same conclusion regarding papermerge.db. What I did was create a new container path- /db:/mnt/user/appdata/papermerge/db and then edited the papermerge settings.py to point to the new db location ("NAME": "/db/papermerge.db" for me). Now the documents stay on the array and all the db shenanigans that were keeping the drives spun up are taking place on my cache drive. The only times I've noticed the drives spinning back up is when I actually add new documents to papermerge. That does mean I'm relying on CA Appdata Backup/Restore to keep the db backed up, but I can live with that...having all the documents on the actual array is the whole point of doing this on Unraid in the first place. 😀 *Note* In the Papermerge documentation it says you can set a DBDIR path in the papermerge.conf.py, but I didn't have any luck getting that to work, which is why I made the change in settings.py.