[Zope] CMS Publishing

Dieter Maurer dieter@handshake.de
Wed, 8 Jan 2003 21:45:38 +0100


Sameer Maggon wrote at 2003-1-8 15:51 -0800:
 > In some CMS we have different environment for Development (Authoring),
 > Staging and Production. The CMS Database that resides in the Development
 > setup is usually more bulky than the database in the production and staging
 > site. Can any body tell me how Zope fits into this situation, is there any
 > component that takes care of this?
A strange situation for a CMS:

  Usually, the development site contains very few content while
  the production site contains lots of it.

 > My major concern is that, it might be that my repository contains huge
 > number of images but actually the site uses only some of them. So when
 > actually deploying a site, the system should resolve those images and put
 > the required files.
I do not understand your concern (see above).

We separate infrastructure, configuration and content (in a
CMF (Content Management Framework) context).

  Infrastructure is kept in the file system and synchronized via CVS

  Configuration is kept in the ZODB and synchronized via ZSyncer

  Content is kept in the ZODB and is not synchronized at all
  (as the content in the development, test and production sites
  is (and should be) different).
  Sometimes we move content from the production to the testing side
  via "export/import".


Dieter