Hi Debian Flo, Quoting Debian Flo (2020-12-25 23:41:16) > * What led up to the situation? > > Installing radicale. On buster, I found out that this doesn't change in > testing or unstable. > > * What exactly did you do (or not do) that was effective (or > ineffective)? > > I did not installed libapache2-mod-proxy-uwsgi and I have changed > filesystem_folder in /etc/radicale/config. > > * What was the outcome of this action? > > Radicale did not work. And it took me days to find out that > libapache2-mod-proxy-uwsgi needed to be installed. > And it didn't work because I have changed the filesystem_folder without > changing /etc/uwsgi/apps-available/radicale.ini. > > * What outcome did you expect instead? > > I expected that (after necessary configuration) Radicale would work more or > less out of the box. > > I have three suggestions: > 1) the suggested way is to run Radicale with Apache and UWSGI. Therefore, > libapache2-mod-proxy-uwsgi is necessary and not to be marked as suggested.
Using Radicale with uWSGI is _suggested_ and therefore the package _suggests_ libapache2-mod-proxy-uwsgi. if instead treating libapache2-mod-proxy-uwsgi as necessary, using Radicale with uWSGI becomes mandatory, which is not intended. I agree that it makes sense to improve the package to better work out-of-the-box, but I disagree that the way to do that is to reduce flexibility of the package: It is usable with uWSGI or without uWSGI. I am interested in discussing how the package could be made easier to use *without* limiting the ways it can be used. I hope you will be interested in discussing that. > 2) there must be a hint that changing filesystem_folder in > /etc/radicale/config needs changes in /etc/uwsgi/apps-available/radicale.ini > and maybe in the home directory of user radicale. I disagree that consequences of each specific deviating from the default setup needs to be documented in the package. I am sorry that you made a change that you did not (until several days struggle) realize had consequences at other configurations as well Concretely, I consider the change of data location too fundamental to sensibly document. Similar to how sudo only warns broadly about the risks of being root but does not document all the risks - e.g. does not say "don't do 'rm -rf *' while standing in the root directory" or "don't use sudo while drunk, because you might mistype commands". > 3) the description in radicale.README.Debian needs to be extened. I am > willing to contribute an explaination that would have empowered myself to > have the service up and running in a short time. This should be helpful for > others, too. Please share your suggestions for improvements. Or maybe begin by sharing which ideas for improvements you have - because it sounds like you would like far more detailed documentation than I am willing to maintain, so probably better that we discuss the _ideas_ that you have before you spend too much time turning your ideas into concrete text. Thanks for taking the time to share your issues with the package. I hope that your ideas for improving the package documentation are less radical than the other issues you had, and I look forward to hear more about them. Kind regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
