[opencms-dev] Best Practices for Setting up 'staging' environment for Content?

[Kim, Allan]

Having looked at the same thing recently, I'd suggest:

1. Content availability dates and the Time Warp feature.

2. Serving your live content as static HTML, and using the Online project as your "staging" site

3. Totally speculative ... but you may be able to sync the two environments by manually starting/stopping MySQL replication

________________________________________
From: opencms-dev-bounces at opencms.org [opencms-dev-bounces at opencms.org] On Behalf Of Art Shectman [art at elephantventures.com]
Sent: Sunday, August 24, 2008 8:43 AM
To: opencms-dev at opencms.org
Subject: [opencms-dev] Best Practices for Setting up 'staging' environment      for Content?

Hi,
I'm a newbie to OpenCMS, and am trying to vet a design we are working on where content will need to be 'staged' prior to being made publicly available.  Basically we are trying to allow for the end client to be able to preview what content will look like at a future date, or 'post-release' when the current batch of to be approved content is released into our production environment.

The solution we are converging toward seems to be to maintain two instances of the CMS, one in staging where preview is driven from that we change the server date on to allow for 'future views', and then a complex synchronization script that syncs the current content snapshot of all the currently 'approved' content with the Production CMS while removing all 'unapproved' content.  These concepts are separate from the Published/Unpublished concepts in OpenCMS.

Has anyone set up something similar?  If so or even if not, any Project Architects out there that would want to do 2-3 days of consulting to help us vet our design?
Thanks in advance!
Art

Art Shectman

President
Elephant Ventures
http://www.elephantventures.com<http://www.elephantventures.com/>
C:917 714 3103
O:212 730 6710
F:917 591 2809