Looks like in Radicale 3.7, there is improved collection sharing? Has anyone tried using this?
I haven’t tried any sharing previously because it seemed like it wasn’t officially (or well) supported before, since you had to do some weird symlink hack.
Is sharing now more officially supported now? I looked at the UI, but I didn’t see anything mentioning sharing…



It’s IMHO poorly documented (in terms of visibility).
Since it is not enabled by default, you have to edit your config file with the ‘[sharing]’ section. There are two types, by map and token to conform to different usecases. There are also two different storage types, csv and files. Personally i chose map and csv way.
After adding your config and restarting the server, in the gui you can find a new button to share next to your calendar / carddav and in the bottom right menu an entry to accept invites issued by others.
I previously shared with the symlink too but since this update i got rid of it and used this new system and, well, it works for me (i’m sharing ro only calendar but you can assing [limited] permissions too).
Ahh, ok… I’m seeing the docs.
ShareType: type of share token: token-based share (do not require user authentication) map: map-based share (requires user authentication)Ahh, ok. So whether you need authentication or not.
And the docs for that…
CSV One CSV file containing one row per sharing config, separated by ; and containing header with columns from above. If given, properties are stored in JSON format in CSV. Files File-based configuration store is using encoded PathOrToken as filename for each config. File contains the data stored as "dict" in binary Python "pickle" format (same is also used for item cache files).So if you want plaintext vs binary storage.
Would you mind sharing your config, pretty please. 🙏
Here is the relevant section:
[sharing] type = csv database_path = /var/lib/radicale/collections/sharing.csv collection_by_map = true permit_create_map = trueJust FYI, my
filesystem_folderis defined as/var/lib/radicale/collections.BTW. The token based sharing, as I understand, still requires auth, just not an user auth but, well, a token one.