Manage rights

defaults/main.yml

@@ -8,3 +8,28 @@ radicale_users: []
 # Example:
 #  - name: toto
 #    password: <secret>
+# password is either the plain-text password, hashed at deploy time (SHA-512
+# crypt, stable per-user salt so the file stays idempotent), or an existing
+# htpasswd hash ($apr1$, bcrypt $2y$, $5$, $6$, argon2), written as is.
+
+# Access rights. Empty: built-in "owner_only" model. Otherwise a rights file is
+# deployed and used ("from_file"); sections are evaluated in order, the first
+# matching one wins. See https://radicale.org/v3.html#authorization-and-rights
+radicale_rights: []
+# Example (same as owner_only, plus anonymous GET on one calendar):
+#  - name: root
+#    user: ".+"
+#    collection: ""
+#    permissions: R
+#  - name: principal
+#    user: ".+"
+#    collection: "{user}"
+#    permissions: RW
+#  - name: calendars
+#    user: ".+"
+#    collection: "{user}/[^/]+"
+#    permissions: rw
+#  - name: public
+#    user: ".*"
+#    collection: "toto/public"
+#    permissions: i