Re: [SyncEvolution] problem syncing calendar between Nokia N900 and owncloud calDav calendar
Den 12. mars 2012 17:50, skrev karlitos:
Should I use the --sync-property command or is it correct to use for
example
username=**** like in the article ?
In SyncEvolution 1.2, the "--sync-property" part became unnecessary, but
for backwards compatibility reasons, it still works. It's up to you
whether to use it.
I am not quite sure how to set the syncURL in the first command
propperly. In my
setup I used
syncURL=http://192.168.178.4/owncloud/apps/calendar/caldav.php/calendars/karlito
s/calendar , so for the first command (yncevolution --configure --template
webdav) I use the URL part before the username ?
Like
syncURL=http://192.168.178.4/owncloud/apps/calendar/caldav.php/calendars/ ???
Maybe? Whatever your CalDAV server expects, if you're going to rely on
SyncEvolution's autodetection. If you're thinking of the radicale
instructions, it seems they're overriding it with the "database" option
anyway, so the autodetect probably won't be used anyway.
At the end of the database URL - should there be a trailing / after
the calendar
name ? The wiki article says yes, but in my
first config I
did not use it.
Use it. From what I understand, Radicale gets particularly upset if you
don't, but you should probably use it with all other CalDAV servers too.
The deviceId and all the other propeties, used by me in the first
config, are
they not needed ?
Ordinarily not. SyncEvolution has quite sane defaults, but your mileage
may vary. You can use them if you like.
syncevolution --configure \
database=http://192.168.178.4/owncloud/apps/calendar/caldav.php/calendars/karlit
os/private \
backend=caldav \
evolutionsource=default \
target-config@owncloud private-cal
The target-config is for configuring the remote database, so you cannot
use evolutionsource there. The evolutionsource should go into the local
configuration (i.e., the corresponding "SyncEvolution Client" stuff).