Ooops

While you are right in general, you are creating a file with a <user>:<hased password> line. Have fun searching the world for where I might have actually used it.

The option to password protect it are in the (usually /etc/radicale/)config file und [auth].

For proper security you could use

type = htpasswd htpasswd_filename = /etc/radicale/users htpasswd_encryption = bcrypt

then create a users file with apache tools (htpasswd -c -B users User1) or one of the million online htpasswd file creators.

So one in five doesn’t do proper backups. That’s much better than expected… 😅

Isn’t that the whole point of containerised solutions? Having some pre-setup, auto-updating solution with very little requirement to dive into the details like what your database is and which dependencies you need to manage…