Researching how to link /admin/Account/Calendar and /admin/Account/AddressBook with the Nextcloud calendar and address book, I just got confirmed that stalw.art/Nextcloud use their own CardDav/CalDav and there is no integration in 0.16/NC33 either way?
I admit, I don’t like such duplication, as it naturally triggers some smart users trying to break out of our system defaults. And IMHO it neither makes much sense to reinvent the wheel and such appoint resources to work duplication?
Feature Idea: Integrate with Nextcloud, single address book/calender.
This is out of scope, Stalwart is a server, not a calendar/contact client that can integrate with other DAV servers. You should instead open a feature request on Nextcloud to use their web client to connect to Stalwart over DAV.
The original report is unclear to me. What do you expect to happen, exactly ? Do you want to disable the calendar feature in Stalwart? Do you expect a 2-way sync with NextCloud? Do you expect NextCloud calendar UI (not NextCloud CalDAV server) to access the Stalwart CalDAV server?
I’d say I am not alone as the first response shows. I understood stalwart to integrate tightly with Nextcloud? Or so the marketing says.
Then two carddav/caldav servers make no sense to me. So IMHO I address this here and shouldn’t be ping-ponged for “responsibility” to Nextcloud. Or is the tight cooperation between the two systems just noise? Yes, I will ignore the duplication, but then don’t promote that you tightly integrate.
For me for a user point-of-view and IT “veteran”, I’ve seen such announcements either lived by or being noise. Sad to see it’s noise. Else IMHO stalwart would “simply” not replicate a cal-/carddav but enable a common store. Like a setup of the Nextcloud link, then using Nextcloud cal-/card-/webdav “seamlessly”. And talk with Nextcloud to enable it both ways, so Nextcloud does the same with stalwart.
So @stalwart@ben - is that marketing noise or lived by?
Hey Barthel, I was not questioning the merit of your proposal. I agree with your objective. It’s just not clear to me what the best solution is.
I would say the best fix would be for NextCloud contacts, calendar and mail apps to be able to use another CalDAV/CardDAV server. That would be a change in NextCloud. I think that’s what @stalwart meant with his response above. So, you’d need to file the bug at NextCloud, not here.
Another solution would be to make a 2-way sync between the Stalwart CalDAV server and the NextCloud CalDAV server. That could be done either in NextCloud server, Stalwart server, or in a separate component. For example, there’s vdirsyncer, which seems to do exactly what you want. This is something you can do right now. I haven’t tried it myself, though.
Lastly, you use a client (e.g. Parula) to bring all these services together, and configure mail, calendar and contacts from Stalwart, whereas files are hosted by NextCloud via WebDAV. (Parula is my product and not a product of Stalwart.)
I’ve been testing the AppImage for a quite a while (to get away from the still bloated Betterbird) and it kept me bugging why mustang sounds so close to stalwart and why the theming/ui of the app so eerily similar to stalwart
Sorry for that misunderstanding. I don’t work for Stalwart, I am just a “community” member. Parula is my product and not a product of Stalwart. Any resemblance that you see is probably coicidence (or a reflection of similar philosophies). I like Stalwart, and we want to make Parula work really well with Stalwart and are therefore testing it throughly and remove any issues. I looked around the other posts here, but I am not affiliated with Stalwart in any way. I have adapted my post above to clarify further. Sorry for the confusion that I caused.