Quoting can...@free.fr (2020-03-05 14:14:37) > In my config I have > > [auth] > type = htpasswd > htpasswd_filename = ~/.config/radicale/users
Thanks, that confirms my suspicion that customization was needed. > I just followed recommendations on the radicale web page for this. I did not mean to imply that you did anything wrong. Ideally the Debian package should be usable as-is (i.e. without adjusting config files) for both single-user and system-wide use. This bugreport points out a regression regarding that goal, but when looking into correcting it I spotted another earlier regression: auth type "remote_user" is only usable for system-wide use running as a proxy. > I think that personal config file overrides the system-wide one, so > there isn't really any need to worry about this. Yes, I could give up on trying to serve per-user use with the config file below /etc. That would be not be ideal, however. > The logging issue is really an upstream bug : correct behaviour would > be to check whether the user asked for different logging options, > before setting up the system-wide logging. This should work: radicale --logging-config ~/.config/radicale/logging ...but ideal would be that running radicale without custom options would work also for a regular user. > But really, I think you should create a special (system) user « > radicale » for a system-wide service. No need for root to serve an > addressbook, even if it is the system addressbook, no ? Unless you > want to modify it, but do you really want to use radicale for changing > the users on a system ? The Debian package does this already now: When I talk about system-wide use I mean started as a daemon running under a dedicated username. > Then then you can give it write access to /var/log/radicale, and give > it its own user config files, leaving /etc/radicale for only truly > common options. Yes, that is possible. Ideally, however, would be that the system-wide use would consult the config below /etc for _all_ its options. It is not ideal to tell a sysadmin to edit some options below /etc and other options below /var/lib/radicale > You probably also want to make it a package configuration question if > this service should be enabled no ? Or just leave it disabled by > default, after all it will not work out of the box anyway I think... ? Currently the radicale package installs a disabled-by-default service. Ideally the service would be enabled by default, with a question asking _how_ to enable it (systemd, uwsgi, self-contained) or disable it (e.g. when used per-user instead). Thanks for sharing your ideas, - 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
