On Thu, 2013-01-31 at 13:55 +0100, HESPUL - Fabien MICHEL wrote:
> Hello,
>
> I'm seeking for a way to have two caldav calendars on differents servers
> synced each other.
>
> In my case, it concern a calendar on Google calendar and a calendar on
> an Apple ical server.
> They both support caldav protocol.
>
> Do you think syncevolution be able to do this ?
Yes, that might be doable, although it has not been tested.
Follow the steps in the README for configuring an @ical context where
you access the iCal server. Something like this:
syncevolution --configure \
databaseUser=123456 \
"databasePassword=!@#ABcd1234" \
backend=caldav \
database=http://example.com/calendar/123456/ \
@ical \
calendar
Then also configure a source for Google calendar:
syncevolution --configure \
[email protected] \
"databasePassword=!@#ABcd1234" \
backend=caldav \
database=https://www.google.com/calendar/dav/[email protected]/user/?SyncEvolution=Google
\
@google-calendar \
calendar
Finally, set up a sync config and sync:
syncevolution --configure \
peerIsClient=1 \
syncURL=local://@google-calendar \
uri=calendar \
sync=two-way \
google@ical calendar
syncevolution --sync slow google@ical calendar
syncevolution google@ical calendar
In this setup, the "local" side that gets mentioned in the output is the
iCal data. I've chosen to do it this way around because accessing and
modifying data in Google is often more complicated due to various
workarounds for Google quirks, and data access is more frequent on the
server side.
Note that I have not tested this. What could ruin the whole concept is
that Google insists on frequent updates of the SEQUENCE property of an
event. I am not sure how well the iCal side will tolerate that.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution
