Does anyone have any tips for setting up CMFStaging. I'm just starting to fumble my way through it and I've only found two posts with any real information about setting it up. Essentially my architecture is this: Three separate machines: DEV QA PROD We're running Plone and ZEO. We need to be able to develop templates et al on DEV, test on QA and eventually migrate those templates, workflows, security etc. to PROD. In PROD we have content authors who create new content (in real time) using a customized DCWorkFlow. We'd like to have the ability to keep the authors content separate from the application templates and security. I'm assuming to do that we just need seperate databases using a different mount point or do we have to use a product to accomplish that. Anyone with some real world experience doing something similar? _________________________________________________________________ Scope out the new MSN Plus Internet Software optimizes dial-up to the max! http://join.msn.com/?pgmarket=en-us&page=byoa/plus&ST=1
If you're using CMFStaging with Plone, using PloneStaging, a Plone wrapper for CMFStaging, from the collective project on sourceforge... You only need one ZODB though. Put your users folder in /staging or /staging/Stages (shouldn't matter which, I think) and customize permissions on each portal as you see fit. Jim On Tuesday, January 13, 2004, at 12:05 PM, Michael Havard wrote:
Does anyone have any tips for setting up CMFStaging. I'm just starting to fumble my way through it and I've only found two posts with any real information about setting it up.
Essentially my architecture is this: Three separate machines: DEV QA PROD
We're running Plone and ZEO. We need to be able to develop templates et al on DEV, test on QA and eventually migrate those templates, workflows, security etc. to PROD. In PROD we have content authors who create new content (in real time) using a customized DCWorkFlow. We'd like to have the ability to keep the authors content separate from the application templates and security. I'm assuming to do that we just need seperate databases using a different mount point or do we have to use a product to accomplish that.
Anyone with some real world experience doing something similar?
_________________________________________________________________ Scope out the new MSN Plus Internet Software optimizes dial-up to the max! http://join.msn.com/?pgmarket=en-us&page=byoa/plus&ST=1
_______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
-- Jim Roepcke Tyrell Software Corp <http://www.tyrell.com/>
Michael Havard wrote at 2004-1-13 20:05 +0000:
Does anyone have any tips for setting up CMFStaging. I'm just starting to fumble my way through it and I've only found two posts with any real information about setting it up.
Essentially my architecture is this: Three separate machines: DEV QA PROD
"CMFStaging" is not for this use case. Instead, it support DEV, QA and PROD stages for *content* (only) inside a single CMF instance. We approach your problem like this: * put everything possible (templates, scripts, products) into file system. Use CVS to manage these resources. "QA" and "PROD" use CVS to fetch "released" revisions from the CVS repository * use ZSyncer to sync configuration data in the ZODB from DEV to QA and from QA to PROD. * ensure a proper separation of content between DEV, QA, and PROD. All have their own content (which must never get mixed). QA occationally gets a fresh copy of PROD's content. -- Dieter
On Wed, Jan 14, 2004 at 10:37:35PM +0100, Dieter Maurer wrote:
* use ZSyncer to sync configuration data in the ZODB from DEV to QA and from QA to PROD.
* ensure a proper separation of content between DEV, QA, and PROD. All have their own content (which must never get mixed). QA occationally gets a fresh copy of PROD's content.
Oddly enough, this is identical to a proposal I wrote for my employer earlier this week :-) The last point would be helped by some improvements to ZSyncer that I've been mulling over. Whoops, I forgot to release 0.5.0 :-O -- Paul Winkler http://www.slinkp.com Look! Up in the sky! It's THE RANDOM-HERO DATABASE COMPTROLLER! (random hero from isometric.spaceninja.com)
On Wed, Jan 14, 2004 at 07:53:28PM -0500, Paul Winkler wrote:
Oddly enough, this is identical to a proposal I wrote for my employer earlier this week :-)
On second reading it's not really the same at all. Different needs. Never mind :-) -- Paul Winkler http://www.slinkp.com Look! Up in the sky! It's GARBAGE-COLLECTOR OCTO-SHOCK! (random hero from isometric.spaceninja.com)
On Wednesday, January 14, 2004, at 01:37 PM, Dieter Maurer wrote:
Michael Havard wrote at 2004-1-13 20:05 +0000:
Does anyone have any tips for setting up CMFStaging. I'm just starting to fumble my way through it and I've only found two posts with any real information about setting it up.
Essentially my architecture is this: Three separate machines: DEV QA PROD
"CMFStaging" is not for this use case. Instead, it support DEV, QA and PROD stages for *content* (only) inside a single CMF instance.
If CMFStaging's setup is anything like PloneStaging's setup (and I assume it is since I think it's just a wrapper around CMFStaging), then it's actually 3 CMF/Plone instances in one ZODB. /staging /staging and versioning tools and version repository /Stages /Development /plone (CMF/PloneSite instance) /Review /plone (CMF/PloneSite instance) /Production /plone (CMF/PloneSite instance) It works very well except that it doesn't support renaming or moving of items. We've used it in production. I wouldn't say it's the best possible solution for this but it does seem to work.
* put everything possible (templates, scripts, products) into file system.
Use CVS to manage these resources. "QA" and "PROD" use CVS to fetch "released" revisions from the CVS repository
* use ZSyncer to sync configuration data in the ZODB from DEV to QA and from QA to PROD.
Do you use workflow transition "after" scripts to do this syncing? If not, how/when do you trigger it? I admit it would be nice to have 3 separate Zope environments rather than just 1, since then you can test different code in DEV rather than needing a separate instance for testing new product code/templates/scripts and then migrating it to the production (three pronged) staging system.
* ensure a proper separation of content between DEV, QA, and PROD. All have their own content (which must never get mixed). QA occationally gets a fresh copy of PROD's content.
Makes sense. Jim -- Jim Roepcke Tyrell Software Corp <http://www.tyrell.com/>
Jim Roepcke wrote at 2004-1-14 22:00 -0800:
....
* use ZSyncer to sync configuration data in the ZODB from DEV to QA and from QA to PROD.
Do you use workflow transition "after" scripts to do this syncing? If not, how/when do you trigger it?
Configuration data is not controlled by CMF/Plone workflows (these workflows control "content" in the sense of CMF/Plone). Configuration data is synced from DEV to QA when a development cycle ended and the corresponding QA should start. QA is synced to PROD once the QA team released the result. Of course, this is workflow, too, but on a different (the development rather than the content) level. -- Dieter
participants (4)
-
Dieter Maurer -
Jim Roepcke -
Michael Havard -
Paul Winkler