> I tried following these instructions and grafting this file at > https://gist.github.com/return42/47ac8aabd19eaad0f10979761d0611a1 into my > config. I have authentication set to pwauth, not a static file. Apache spawns > a login window when I use the uWSGI configuration, but it throws a 500 error > (due to PermissionError: [Errno 13] Permission denied: > '/var/lib/radicale/collections') when I use only mod_wsgi.
So I know I'm making a nuisance out of myself. But I hope that, once I understand what's going on and how to fix it, I can improve the code and/or documentation to make Radicale more useful for future generations. My DAV folders are permissioned to uid=radicale & gid=radicale & perm=rwxrwx--- (770). It should be documented whether this is too restrictive or permissive, since this _is_ an Internet-facing service. The above config works with the 'recommended' uWSGI implementation. However, I can't figure out which mod_wsgi apache.conf settings will get Radicale to run with radicale:radicale permissions, so Linux quite appropriately refuses to let it access the DAV folders. One suggestion is to change the DAV folder permissions to www-data:www-data (https://wiki.debian.org/Radicale#Deliver_Radicale_through_Apache) which strikes me as unsafe (fixing wiki documentation is also on my to-do list). I also discovered the undocumented (!) /etc/default/radicale file, which sets the "--daemon" option. Does this have to be disabled for mod_wsgi?
