Jaroslav, I've been rather happy with Zsync. It will tell you when files are different versions between source and server. You could set up Zsync'ing to be bidirectional (e.g., DEVEL --> PROD and PROD --> DEVEL), then you'd go into whatever instance you wish to push the changes from. It is a push mechanism, but it's amazingly useful and robust. After adding the appropriate methods in my Zsyncer, I was actually able to use it to copy an entire site from one server to another. (In this case, it caused a nasty loop because I had a Virtual Site Root and Squid sitting in front of it, but that was my configuration, and I was able to fix it.) In our case, we have DEVEL-->TEST-->PROD, and occasionally I set PROD-->DEVEL. (I turn it off when not needed.) --Adam -----Original Message----- From: Dieter Maurer [mailto:dieter@handshake.de] Sent: Thursday, September 12, 2002 2:42 PM To: lsh@wo.cz Cc: zope@zope.org Subject: Re: [Zope] Collaborative syncing? Jaroslav Lukesh writes:

I was install and try Zsync (latest on Zope 251/W32), it is nice, but I do > not know to make simple sync in case when source and target was changed > each different file and have some files more or deleted. ZSyncer requires that changes are only made at one place.

ZSyncing is an unidirectional process only. Dieter _______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )