[cvs] [Wiki] changed: SyncHowTo

[Chuck Hagenbuch]

chuck  Fri, 01 Jul 2005 10:03:38 -0700

Modified page: http://wiki.horde.org/SyncHowTo
New Revision:  1.4
Change log:  Some setup and cleanup info

@@ -1,7 +1,7 @@
 + How to configure a device to sync with Horde 3.1 (HEAD)
 
-Syncing is currently development-level code - you need to be able to at least read logfiles! Testing is welcome; please report to the sync list (sync at lists.horde.org), but please keep in mind that the code is still in heavy development.
+Syncing is currently developer-level code - you need to be able to at least read logfiles! Testing is welcome; please report to the sync list (sync at lists.horde.org), but please keep in mind that the code is still in heavy development.
 
 * The sync URL is http(s)://pathtoyourhordeinstall/rpc.php
 * Username/password: your Horde account data
 * Databases (sometimes called remote settings) must be calendar, tasks, notes, or contacts.
@@ -11,4 +11,27 @@
 tail -f /tmp/horde.log | grep "SyncML:"
 </code>
 * For sync4j outlook syncing, use at least !SyncClient PIM Outlook version 1.3.9 available from sync4j.org (v 2.2). The device ID must be sc-pim-outlook or anything containing sync4j so that the Horde backend can identify the connector.
 * For devices using WBXML (P800/P900 and Sync4j don't, most others do) you need a recent (>=0.9) version of the wbxml2 library installed.  See http://libwbxml.aymerick.com/.
+
+++ Sync clients being used succesfully:
+
+Synthesis client (v2.5.0.30) -> PDA -> USB serial cable -> Powerbook G4 running The Missing Sync (http://www.markspace.com/missingsync_palmos.php) -> Horde test installation
+
+++ Cleaning up when testing
+
+//**##red|DO NOT USE THIS IN PRODUCTION!##**//
+
+If you're debugging and want to clean out data between sync attempts, you can try this set of commands if you use mysql (or adjust appropriately for other backends):
+
+<code>
+delete from kronolith_events where calendar_id='YOUR CALENDAR';
+delete from horde_datatree where group_uid='syncml';
+delete from horde_datatree_attributes using
+    horde_datatree_attributes left join horde_datatree on
+    horde_datatree_attributes.datatree_id=horde_datatree.datatree_id where
+    horde_datatree.datatree_id IS NULL;
+</code>
+
+You can clear all session files (assuming the default backend) with <code>rm -f /tmp/sess_*</code>.
+
+You'll have a lot of entries in the datatree with a group_uid of 'horde.history'. You will lose information from more than syncing by clearing them out, but you can do so. It is also useful to clear out horde.log and /tmp/sync to get a better feel for what is from the current sync attempt and what is not.