Setting up Zope in a development/production environment
Hi: The way our current website works is via changes made in a sandbox area and then using CVS moved to a staging area (same server as sandbox). After approval of changes visible in the staging area, the changes are then, using CVS, moved to the production server (different from staging server) where they're visible on the public website. Now Zope/Plone use the various permission controls to mimic the above but I would like to find out how to create the above design/staging/production environment using Zope/Plone. Thanks. Q
Qass wrote:
The way our current website works is via changes made in a sandbox area and then using CVS moved to a staging area (same server as sandbox). After approval of changes visible in the staging area, the changes are then, using CVS, moved to the production server (different from staging server) where they're visible on the public website.
Now Zope/Plone use the various permission controls to mimic the above but I would like to find out how to create the above design/staging/production environment using Zope/Plone.
There's a versioning/staging solution for CMF/Plone which needs some work though. I don't know what shape the CMFStaging Product is currently in, but PloneStaging is ways out of date. If you'd like to use it - prepare to invest some time :) http://svn.zope.org/CMF_Extras/trunk/CMFStaging/ (needs ZopeVersionControl) http://cvs.sourceforge.net/viewcvs.py/collective/PloneStaging/ HTH, Igor
Qass wrote at 2006-1-30 16:12 -0600:
... Now Zope/Plone use the various permission controls to mimic the above but I would like to find out how to create the above design/staging/production environment using Zope/Plone.
You keep this style for all kinds of infrastructure (code, templates, scripts). For content and configuration, you might have a look at "ZSyncer". -- Dieter
participants (3)
-
Dieter Maurer -
Igor Stroh -
Qass