See client/ExampleSettings.php for instructions.

Note that setting changesDatabase is trivial, but it relies on a multi-master configuration that is a bit involved to set up.

The WBC tables are being created on the repo. We need to figure out where this happens and why.

The WBC table is *supposed* to be created on the repo, and *only* on the repo. The clients use the changesDatabase setting to get access to that table - changesDatabase should be the name of the repo's database.

Err - the wb_changes table is supposed to be on the repo. of course, no wbc_xxx tables should be created there. But if that's what Denny is referring to, what does it have to do with this ticket?