-
Hello everyone, I am trying to get the consume folder to work, but I am completely stuck. I have paperless installed with the docker script on a Debian 12 'Bookworm' installation. Paperless itself works, and I can add .pdf files via the web-frontend. I have absolutely no luck at all with the consume folder, though. The goal is to have a network share both me and my girlfriend can add pdf files to and Paperless-ngx automatically consumes these. First, I am aware that I have to set PAPERLESS_CONSUMER_RECURSIVE to true when using subfolders. But: Where exactly? And is it really "true" or a 1/0 entry? I don't really understand the documentation at this point and I made the mistake to check forums and reddit for a solution and in the end I had like 20 different approaches... Then, next problem, I have a network share mounted directly into the consume folder (because the subdirectory approach did not work as described above) which is located in /home/username/paperless-ngx/consume. I can add files from a Windows PC, from my Linux laptop, and i.e. touch them directly on the paperless-system. All changes and added, deleted or created files show up on the other systems, but .pdf files never get consumed by Paperless. I don't understand why this has to be so bloody complicated. Setting up Paperless-ngx did take about an hour and now I am trying to get the consume-folder to work for three evenings straight... Any ideas as to what goes wrong or some kind of definitive guide anyone? Any help appreciated... |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 4 replies
-
Im not sure everyone would agree it's "so bloody complicated", but self-hosting is certainly more work than e.g. an App Store. There's an install script, docker-compose examples and everything above is covered in the docs (and many times in the discussions). You provided very little details so it's hard to know how to help.
|
Beta Was this translation helpful? Give feedback.
-
Well, I actually am a happy owner of Proxmox-Server, running host to multiple VMs for recursive DNS, Pihole, CA, Printserver, Docker host VM, NAS and yadda yadda. There's even a virtualized Windows 3.11 running. So yeah, I know that self-hosting takes time to get comfy with. But for whatever reason, Paperless gives me a really hard time. As I mentioned before, installation itself was no problem. But configuration... I don't know. Regarding to where I have to set configuration statements, I now understood it has to be in docker-compose.env. But why are there multiple possible options in the first place? That is... odd. Then for the boolean config, a tiny hint in the documentation that values can be 1/0 or true/false would have helped out A LOT. Then: Polling. This does not work for me. I restarted the VM and upon reboot, the files that were present in the consumption folder got consumed. I then added another pdf and... nada, zero, nothing. It does not get consumed... Why, oh Lord whyyyyyyyyyyyyyyyyyyyyyyyy?! Funfact: Overall documents at the moment is 66. But only 65 file tasks have been logged. Another mystery... |
Beta Was this translation helpful? Give feedback.
-
Log states this:
But I set in docker-compose.env: So what could cause this? |
Beta Was this translation helpful? Give feedback.
-
Errrrrrm, do I have to re-run all this docker-shizzle, i.e. is it not enough to just restart the VM to introduce new environment variables such as PAPERLESS_CONSUMER_POLLING=1? Will I lose everything that has been set up as of now, then, like groups, users and already imported files? |
Beta Was this translation helpful? Give feedback.
-
Turns out I simply had to do Seems that my problem was docker or my lack of understanding how to handle docker containers and changing environment variables in the first place. I'd really enjoy a new bare-metal installation guide as mentioned by @schweiger2 in #5822 to get Paperless running in the Debian 12 VM (or an LXC Container directly within Proxmox) without the docker layer... Anyways: Solved, thanks a lot! |
Beta Was this translation helpful? Give feedback.
-
This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details. |
Beta Was this translation helpful? Give feedback.
Turns out I simply had to do
docker compose down
and then get the containers up again withdocker compose up
to actually introduce changes made in docker-compose.env. Polling worked afterwards on the SMB share and settings, users and already imported files were persistent. This worked, so I quit out with CTRL+C and started the containers again in the background withdocker compose up -d
. For peace of mind I rebooted the whole VM and everything is working now.Seems that my problem was docker or my lack of understanding how to handle docker containers and changing environment variables in the first place. I'd really enjoy a new bare-metal installation guide as mentioned by @schweiger2 in #…