[cube00]

I've been using Radicale for a few years now and it has been fantastic. Extremely lightweight but also quite flexible with its permissions model since we have a shared family calendar.

The backend storage is simply ics/vcf files and while I'm sure it's not the most efficient if you had a large number of users, for our small group it's been perfect and very satisfying knowing your data is there in plain text files.

Although if I'm honest I'm just cheap and wanted to get by on the smallest VM offered by my cloud provider and NextCloud was too demanding for that.

[jamessb]

> Extremely lightweight but also quite flexible with its permissions model since we have a shared family calendar.

How are you doing this?

A while ago I skimmed the documentation for a couple of CalDAV servers to try and figure out how I could self-host a shared calendar, but couldn't see an easy way to do this.

I've just done some more searching, and it seems there are two suggested ways to do this with Radicale:

* create a separate account for the shared calendar, and tell everyone who needs write access the password

* create the calendar in one use's directory, and add a symlink to it in the user directories for any other users who need write access.

Both of which seem like a bit of hack compared to bring able to explicitly state that a list of users have write access to a calendar in a config file or through a UI.

[cube00]

I created a collection with the name of our domain name and then used this example[1] to regex the domain out of the user's login email address to allow them access to the shared collection.

[1]: https://github.com/Kozea/Radicale/blob/497b5141b066d266c318e...