You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 16, 2023. It is now read-only.
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?
The text was updated successfully, but these errors were encountered:
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!
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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?The text was updated successfully, but these errors were encountered: