I'm trying to configure the SyncEvolution server to replace the service I was getting from ScheduleWorld. I've run into a problem that's not covered by the HOWTO.
I have multiple Evolution calendars and todo lists. With ScheduleWorld, I configured my clients so that each calendar/todo category had its own context. Each context had a unique deviceID, and then within that context's configuration, I specified the category in the evolutionsource property. On the server side, that translates to multiple peers per client, one for each category. I've been trying to use the Evolution databases as the backing store on the server side. However, I'm running into problems specifying the evolutionsource property. It appears that evolutionsource can only be specified in the default/sources directory, and is ignored if I specify it in the peers/foo/sources directory. I tried making each category a different context (on the server side), but it appears that SE only finds device IDs that are within default/peers. Is there a way that I can configure the server so that it uses the Evolution database? If not, will the filesystem database allow me to do what I need? -- John _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
