On Wed, 2012-08-22 at 13:14 +0200, api984 wrote: > Hello, > > I am trying out SyncEvolution. Currently I would try to sync one way > from Radicale to Google Calendar. > > I read documentation. But its hard to get some examples or more detail > in docs.
The HOWTO section in the Wiki has more examples: https://syncevolution.org/wiki/howto Your specific use case is new, so there is no HOWTO for it. > I am trying to sync > > Radicale CALDAV to Google Calendar. Radicale is company local caldav > server for calendaring and it works pretty well. [...] > Sync would look like?: > > Radicale -> Local db (ical) > > Local -> google calendar > > > > Or it can go directly? You can also go directly. For that, set up CalDAV target-config@radicale and target-config@google as described in the man page (https://syncevolution.org/documentation/syncevolution-usage#caldav-and-carddav) and the Radicale entry (https://syncevolution.org/wiki/synchronizing-radicale). In the case of Radicale you only need one calendar source; make sure that you use set the "database" property for it. Then create a local sync config which uses the Radicale side as "local" storage and Google as target side: syncevolution --configure --template SyncEvolution_Client \ syncURL=local://@google-calendar sync=two-way \ uri=calendar \ google-calendar@radicale calendar I'm assuming that the source is called "calendar" on both sides. The "uri=calendar" is redundant in that case. > I am still learning and reading how to use syncevolution properly. > > I am using SyncEvolution 1.2.2 on Ubuntu 10.04. LTS (workstation). I recommend updating to 1.2.99.4. Binaries are available from syncevolution.org. > PS. Is there any way to install it on Centos 5.2 x64 (server)? The rpms from http://downloads.syncevolution.org/syncevolution/evolution/amd64-rpm/ might work, otherwise compile from source. -- 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
