CardDAV server as backend?
mundschenk-at opened this issue · 13 comments
I know this is still WIP, but it would be great if there was an option to use an existing CardDAV server as the backend (specifically: ownCloud/Nextcloud).
@mundschenk-at I plan to add support for CardDAV but through a synchronization mechanism. What do you think?
Sure, as long as you can connect to the existing CardDAV server, I'm happy
In your use case, which component would the master? Modoboa or ownCloud?
ownCloud (because that's what all my other devices sync to).
Ok, so a one way sync (owncloud -> modoboa) would be enough for you?
It would work. A two-way sync would be better.
Hm i wonder, you have the radicale extension already. so you have the backend for caldav and carddav.
But i also like the idea to use an existing backend.
From my point there could be something like
Like this contacs extension support either local radicale or remote caldav server
and the radicale extension should be the "calender" extension with local radicale or remote carddav server.
Anyway I like to see contacts in the webmail.
Thanks for the good work!
The radicale extension is just a way to manage ACL on calendars, it does not deal with caldav or carddav. Anyway, Radicale's roadmap is not really clear to me, a big refactoring has been started and should be done with 2.0 but I don't know when it will be released so I don't want to make any plan right now.
Ah, then CardDAV for the address book would have to be a separate thing.
yes, that's my idea.
IMHO, neither owncloud nor modoboa should be the master. They should both talk to a carddav server.
@tuxis-ie I'm not sure what you mean. ownCloud is a CardDAV server.
@mundschenk-at CardDAV support has been introduced by 0.7.0 (using Radicale as backend server).