Oh, and it may require like 4 or 5 patches to box code. Forgot about that. It's fully functional tho, a little unpolished, a lot unpolished. But everything works. @girish and I will work together to integrate it properly at some point after 6.0. My patches run at "start" time, so the fact they're inefficient isn't too big of a deal, but just know that somewhere down the line, @girish and I will add it properly into a stable version of Cloudron.
no way to integrate with cloudron mail like the Rainloop app in Nextcloud.
On that specific point, Nextcloud Mail does fine in my experience if the users have their cloudron email as their primary email, then you can do similar to the following (my.demo.com used in place of mail server name):
So it can depend a lot on your setup, but I'll freely give you that no sieve support is incredibly frustrating, plus I constantly can't find features that I feel like should be there, and even when it's "working" the visual design is so weird to me that things still feel wrong. I mean, I'd give it like a 4/10 and "would not recommend to a friend" but for some users/clients...it's evidently good enough?
The rolling average in my experience is definitely hot garbage, but sometimes it's acceptable garbage.
thats unfortunately a bit impractical to do. kwmbridge requires a large range of udp ports so running it in a container with forwarded ports is quite inefficient (because there is also quite a memory overhead in Docker in this case).
But it should be easy to make the app configurable enough to have kwmbridge running on a dedicated host and simply hook up to kwmserver inside of the app. having (multiple) external kwmbridge endpoints is kind of the setup we are expecting anyways.
The COVID-19 pandemic is (almost everywhere) increasing and measures for working from home are again and/or still there. The public Jitsi service is overloaded so it's very very welcome after all these months to have a Cloudron version of Jitsi-server.