Closed scavone closed 3 years ago
The configuration option you're looking for is PAPERLESS_CONSUMER_POLLING
.
Thank you! I had searched the documentation for document_consumer
but not inotify
. Obvious in hindsight. I really appreciate the quick reply. Made the change and it works like a charm!
When the webserver container would first start, it would consume files sitting in the mapped folder but subsequent files being dropped would remain and not be imported.
I did some digging in the issue trackers upstream and here and noticed that it has to do with inotify. The recommendation was to change the command in the upstream
docker-compose.yml
file to["document_consumer", "--no-inotify"]
Obviously that isn’t how this fork executes things but I do see that the command is executed on Line 9 in the paperless-consumer.service
What do you think would be the best way to implement the
--no-inotify
flag?