So using a volume with a folder for consumption is supported. Basically add the volume (in my case extradisk) to the app. This would mount it to /media/extradisk then I created a folder called consume/ in that disk and you have to give it read/write permissions for all users (so chmod it). After this adjust the corresponding env var in the paperless.conf in /app/data. In my case PAPERLESS_CONSUMPTION_DIR=/media/extradisk/consume then restart the app.
Also note the volume in Cloudron has to be read/write mounted! If paperless cannot write to it (for document deletion) it would simply not even attempt to consume documents.
Maybe obvious but I don't have experience with the app. What do you mean by "configuration like paths" ? What does document links have to do with these paths?
No, there is no special plugin. I justed added (or uncomment) the specific options in the paperless.conf.
I checked my installation: The app had already 4GB, I changed to 6 and tried it again. Works.
So maybe the solution was really "Add more RAM if problem exists"
Thx
@nebulon This is super Nebulon. There are so many apps Cloudron has made available. But adding "small" requests like this to existing apps makes Cloudron all that more appealing. You've just saved me the cost of a separate VPS on which I had been running Tika and Gotenburg! Has there been a better improvement of any app than this?! Thank you!
PAPERLESS_TIKA_ENABLED=true
PAPERLESS_TIKA_ENDPOINT=http://localhost:9998
PAPERLESS_TIKA_GOTENBERG_ENDPOINT=http://localhost:3000
Yes unfortunately the upstream project decided to keep it this way. We had a discussion at https://github.com/paperless-ngx/paperless-ngx/discussions/7032 but apparently they do not want to change this.
So after first login via the UI it will fail like this. Then an admin has to give the missing permissions to that user, then it works
Have you tried if creating a token via the Django admin interface works?
admin -> settings -> Django-Adminpanel
[image: 1728130465641-ff8759bf-2b05-4a68-b727-fff78cb04600-image-resized.png]
This seems to be the same as https://forum.cloudron.io/topic/12412/celery-stuck-in-restarting-loop/2 and https://forum.cloudron.io/topic/12195/high-cpu-utilization-since-update-1-25-1/18
I will lock this in favor of the others.