On Mon, 2012-04-23 at 11:23 +0200, Roth wrote:
> I have problems with the configuration for the sync of more than the
> default calendar or addressbook with funambol 10.0.0.
>
> I followed the instructions and have several users on the funambol
> server, each for one calendar.
>
> But with the config.ini I have problems.
>
> Can someone please give me a valid config.ini example for a calendar and
> addressbook for the 10.0.0. version?
For the default databases:
syncevolution --configure \
syncURL=http://<your host>/sync \
username=<user A> \
password=<password A> \
funambol calendar addressbook
For the additional address books and calendars:
syncevolution --configure \
syncURL=http://<your host>/sync \
username=<user B> \
password=<password B> \
calendar2/database=<calendar name> \
calendar2/uri=card \
calendar2/syncFormat=text/calendar \
calendar2/forceSyncFormat=1 \
addressbook2/database=<address book name> \
addressbook2/uri=event \
funambol2 calendar2 addressbook2
Leave out or add other databases as you like. The non-standard settings
(uri, sync format) cannot be taken from a template (name doesn't match),
and therefore have to be specified explicitly here.
Note that this is based on your comment that you already have multiple
users on the server. Isn't it possible to configure the server so that
each user can have more than one database of a kind, under different
uris?
> With the following I get the following error:
>
> First ERROR encountered: cannot bump config version in old-style config
>
> # config.ini #
> sync = two-way
> type = calendar:text/calendar!
> evolutionsource = Office
> uri = caloffice
>
> Or is meanwhile another more elegant solution for the sync of more than one
> calendar?
You seem to be using very old HOWTOs for SyncEvolution. Would you mind
helping other users by summarizing your setup in the syncevolution.org
Wiki?
--
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
