Den 22. juni 2011 18:23, skrev Patrick Ohly: >> How should I >> determine which sources to ask SyncEvolution to create for the client >> config? Is it possible to find out using --print-config? > > Yes, --print-config --template will tell you that. Note that for an > existing context (like @default) it will include sources already > configured inside that context.
Allright, but since I don't build from master, I'm not sure what that's going to look like yet... >> 2) Sync method >> I suppose that syncURL, WebURL, username, password, and uri should go in >> the server config, and database (evolutionsource) should go in the >> client config. But when the user wants to set up a source for slow sync, >> one-way sync etc, where should it go? Server config? Client config? Both? > > Careful with the naming here. I prefer "source" config for the side that > talks to the server (source-config@yahoo) and "local" or "sync" config > for the side that is used for syncing (the one with local:// syncURL). Yes, I've seen that you prefer that, but I don't, since "source config" can be confused with "addressbook/calendar/etc config". (Besides, webdav/README says the local config should use the "SyncEvolution Client" template, which might also justify calling it client config.) > "database" is currently set automatically in the source config (recent > change on master). We still need to add support for listing the WebDAV > resources that could be set here. By "database" in the client config, I meant local storage (which local calendar to sync with the remove side). Anyway, you didn't answer my actual question: for configuring slow sync, one-way sync, or disabling sync, where should the "sync" configuration go? Server/source config? Client/local config? Both? Thanks, Ove _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
