On Sun, 2011-01-02 at 15:00 +0100, Patrick Ohly wrote:
Here's how you can synchronize multiple databases per peer (using
a second calendar as example):
* on the server side, configure a second calendar in the default context:
syncevolution --configure \
--source-property evolutionsource=<name of second calendar on
server> \
--source-property "type=Evolution Calendar" \
@default calendar2
* on the client, enable the second calendar:
syncevolution --configure \
--source-property evolutionsource=<name of second calendar on
client> \
--source-property "type=Evolution Calendar" \
--source-property sync=two-way \
<config name> calendar2
* Now synchronize using the <config name> client config.
Thanks for the fast reply!
In addition to the recipe you provided, I had to explicitly set the
uri's on both sides, and enable the source on the server side.
-- John