Thank you for enlightening me about this.
But in that case, wouldn't it be good to implement some kind of minimal wrapper that checks if the needed resources are accessible for the current user? And if not, the wrapper would just return a message about insufficient read privileges. Instead of the current wall of text consisting of the Python exception stack trace.
I know it is more of an upstream issue, but this should be very easy to implement even in Bash.
Just an improvement idea on my part. Feel free to do or not do anything with it. :)
Anyway, thank you for maintaining it. I am not currently a user of this, but I can see potential in this for myself at a later time.
Pinned Comments
shtrophic commented on 2025-04-14 20:22 (UTC) (edited on 2025-04-14 20:32 (UTC) by shtrophic)
For people not using
redis
: there is now an "automated patching mechanism" that will instead use the next best fork ofredis
that is available on your system as theRequires=
dependency in*.service
. This way, anyone can use their favorite fork of it. Keep in mind that upstream does not explicitly say that forks ofredis
work as well, and this further makes the builtpaperless-ngx-venv
package non-portable. Happy experimenting :)