Thanks for roadmap inclusion. We are using something similar with a different product and it is incredibly useful. Having this on Cloudron would greatly improve product overlap. in our current case, the publication is for read-only purpose mostly so this is what I would suggest initially. Although there might be some benefit to having the possibility to publish a given set of calendar publicly, with editing capabilities (e.g. collaboration with external non cloudron-based third party etc..)

Sorry, this could be a result in anonymizing it. I edited all entries manually in the end... -.- There is a version 6 actually. I think I'll try the update now. ^^

@nebulon Thank you! I think I have something working in n8n, but hit a snag when trying to auth and I think I can make it work. Once the App Password portion is fixed in 9.2, if this works using n8n, I'll post the n8n template to accomplish this.

This is fixed with latest release now

So currently the app will resync the external calendar every 30min. This is just hardcoded for the moment and I am not sure if it is really useful to expose custom intervals or so, seems very geeky.

Forgot to mention, this is already fixed with https://git.cloudron.io/platform/box/-/commit/053f26cd02ccc0b5b840e7bf358fe1d47e1e4b75 but pending the 9.2 release

I started the update manually and the issue is solved. THX.

The app supports a caldav endpoints so if you have a system which can sync this into some other provider it should already work. Currently the Calendar app itself does not have any way to actively reach out into other services. I guess the question here is which part in your setup is the single source of truth regarding the events. That one would be the server and the rest become clients. Wondering what the use-case is to have two such event stores itself. (Same answer really to the contacts topic)