Hi, > Not to be impatient, but is there a working patch or workaround exists for > this? An AI bot and I have spent hours trying to figure this out, and it's > come up empty. This makes sense as I seem to be the only person on Earth > struggling with this. > > I can create the uwsgi-app@radical socket and service, and I've changed > /etc/apache2/conf-available/radicale-uwsgi.conf to use the systemd sockets. > I'm getting permission errors like I did 3 months ago. AI believes the file > permissions are correct (I haven't changed them since this was last working) > but something's going wrong with uWSGI. > > I've tried to graft > https://salsa.debian.org/freedombox-team/freedombox/-/merge_requests/2768 > into my setup without touching the python files. That's probably part of the > problem. > > Anyhow, is there a known working radicale configuration with systemd?
The documentation patch I posted above gave me a working installation of radicale. If you still have permission error, maybe I can help you with some clue about the owner of radicale data and the systemd configuration used to run radical (e.g. systemctl cat [email protected]) and maybe an explicit error message. Alex
