ZSyncer & CMF: Happy Together ??
Is ZSyncer intelligent enough to deal with CMF sites? -- Edward Muller - http://www.interlix.com - "Open Source Specialists" Dedicated Zope Hosting - Web Hosting - Open Source Consulting Network & PC Service & Support - Custom Programming Phone: 417-862-0573 - Cell: 417-844-2435 - Fax: 417-862-0572 Jabber: edwardam@jabber.interlix.com - AIM: edwardam453 - ICQ: 287033
On Thu, Sep 18, 2003 at 03:27:42PM -0500, Edward Muller wrote:
Is ZSyncer intelligent enough to deal with CMF sites?
Hi Edward! ZSyncer doesn't do anything special with CMF site objects. I haven't tried syncing a whole CMF site recently, don't remember if there are any special issues there. It should "just work" (but see caveats below). Try it and be sure to let me know if something goes wrong. As for cmf content, recent CVS of ZSyncer (on sourceforge) does one special thing: using DublinCore timestamps instead of the low-level ZODB timestamp. This greatly improves the reliability of reporting the ok / out-of-date status. I wouldn't sync a whole CMF site or any other folderish object if it contains a very large amount of data. Remember that zsyncer works by exporting the object (to a cstringIO instance instead of a real file), transferring the result across the network, and importing it on the remote server - all in a single request. This can fail if you don't have enough RAM to do the job. Or it can just take an insanely long time due to heavy swapping. It can also succeed but *seem* to fail if your browser times out waiting for the response to come back. IE especially times out easily; I think the longest successful sync I ever managed took about an hour with mozilla. Usually I try to sync in smaller chunks. -- Paul Winkler http://www.slinkp.com Look! Up in the sky! It's THE KATANA! (random hero from isometric.spaceninja.com)
Edward Muller wrote at 2003-9-18 15:27 -0500:
Is ZSyncer intelligent enough to deal with CMF sites?
Partially... Usually, you have the need to separate configuration, scripts and data/content. While configuration and scripts usually should be synced, data/content often should not (as a production site often has different data/content then a development or test site). ZSyncer has not problem to sync a complete CMF site. However, when you need to separate configuration/scripts on one site and data/content on the other, you cannot sync a complete CMF site (as it mixes all of them). On my Zope page <http://www.dieter.handshake.de/pyprojects/zope> you find a ZSyncer patch that allows it to sync most CMF tools. We use this to sync our portals between development, quality assurance and production sites. Works quite well with "portal_catalog" as an exception. "portal_catalog" intrinsically mixes configuration and content. Dieter
On Fri, Sep 19, 2003 at 09:01:22PM +0200, Dieter Maurer wrote:
On my Zope page
<http://www.dieter.handshake.de/pyprojects/zope>
you find a ZSyncer patch that allows it to sync most CMF tools.
Do you mind if I merge this with zsyncer cvs? I might not get to it soon, but I'm interested in this patch.
We use this to sync our portals between development, quality assurance and production sites. Works quite well with "portal_catalog" as an exception. "portal_catalog" intrinsically mixes configuration and content.
i'd say the same for portal_skins. The configuration (skin paths) is stored as properties of portal_skins and I'd *really* like to be able to sync that independently of the contents. -- Paul Winkler http://www.slinkp.com
Paul Winkler wrote at 2003-9-19 16:26 -0400:
On Fri, Sep 19, 2003 at 09:01:22PM +0200, Dieter Maurer wrote:
On my Zope page
<http://www.dieter.handshake.de/pyprojects/zope>
you find a ZSyncer patch that allows it to sync most CMF tools.
Do you mind if I merge this with zsyncer cvs?
Sure, I do not!
I might not get to it soon, but I'm interested in this patch.
No problem at all.
We use this to sync our portals between development, quality assurance and production sites. Works quite well with "portal_catalog" as an exception. "portal_catalog" intrinsically mixes configuration and content.
i'd say the same for portal_skins. The configuration (skin paths) is stored as properties of portal_skins and I'd *really* like to be able to sync that independently of the contents.
My colleagues never reported a problem syncing "portal_skins" but this may have different reasons. Dieter
On Mon, Sep 22, 2003 at 05:46:42PM +0200, Dieter Maurer wrote:
Paul Winkler wrote at 2003-9-19 16:26 -0400:
On Fri, Sep 19, 2003 at 09:01:22PM +0200, Dieter Maurer wrote:
On my Zope page
<http://www.dieter.handshake.de/pyprojects/zope>
you find a ZSyncer patch that allows it to sync most CMF tools.
Do you mind if I merge this with zsyncer cvs?
Sure, I do not!
great, thanks!
My colleagues never reported a problem syncing "portal_skins" but this may have different reasons.
It syncs just fine. The problem is that you can't separate its configuration from its contents. This is a pervasive problem with zsyncer (and .zexp backups)... often I want to separate "contents" from configuration and it's not possible. I'm still looking for a general solution here. -- Paul Winkler http://www.slinkp.com Look! Up in the sky! It's CURMUDGEONY CRANBERRY DEATHSNAKE! (random hero from isometric.spaceninja.com)
participants (3)
-
Dieter Maurer -
Edward Muller -
Paul Winkler