Forums / Setup & design / eZ in a development/staging/production environment

eZ in a development/staging/production environment

Previous topic

Setup & design

Next topic

Author	Message
M S	Monday 20 February 2006 3:33:18 pm Hi: Our current website (no database) setup involves creating webpages in a sandbox area, using CVS to upload the pages to a staging server for review and then using CVS to upload the changes to the live server. This three tier architecture allows for review and prevents bad information from being displayed live. Now, I know that I can set up a edit/review/publish workflow (I believe I can) in eZ and also play with the visibility of items. I was wondering however, if there was a way to replicate my current system with eZ. If anyone has done this, please let me know and I'd be interested in talking more about it. Thanks Q
Ron Schöningh	Tuesday 21 February 2006 8:44:00 am I would like to advise you not to implement such an approach with eZ publish. The reason for this is that content management systems like eZ publish allow the definition of various roles in the publishing process. If you combine these roles (editor, moderator etc) in a workflow you will have a convient mechanism which will be much easier to maintain than the three tier approach you describe. This is one of the reasons to consider an advanced CMS like eZ publish. Myxt Web Solutions http://www.myxt.nl
Marc Boon	Friday 12 May 2006 3:40:10 am About this edit/review/publish workflow. How does that work in practice? Is it possible to review the entire site before publishing, like you do on a staging server? Or do you have to review every node by itself in the admin preview context? The latter would be highly undesirable. I am trying to implement a staging approach, where the staging server is reached by a (non-public) subdomain of the live site. After approval, the live site is updated by regenerating the static cache. The public production site's domain root is the folder containing the static cache, so this public site is truly static (no php or database access at all). I needed to add some url-rewriting rules for javascript, stysheets and images which reside in the design and var/storage directories, but these files are all completely static too. I have the impression that my solution is not the way eZ publish is supposed to work, but I don't know how to setup a staging server using workflows. Tips and ideas welcome!

Author

Message

M S

Monday 20 February 2006 3:33:18 pm

Hi:

Our current website (no database) setup involves creating webpages in a sandbox area, using CVS to upload the pages to a staging server for review and then using CVS to upload the changes to the live server. This three tier architecture allows for review and prevents bad information from being displayed live.

Now, I know that I can set up a edit/review/publish workflow (I believe I can) in eZ and also play with the visibility of items. I was wondering however, if there was a way to replicate my current system with eZ. If anyone has done this, please let me know and I'd be interested in talking more about it.

Thanks

Ron Schöningh

Tuesday 21 February 2006 8:44:00 am

I would like to advise you not to implement such an approach with eZ publish. The reason for this is that content management systems like eZ publish allow the definition of various roles in the publishing process. If you combine these roles (editor, moderator etc) in a workflow you will have a convient mechanism which will be much easier to maintain than the three tier approach you describe. This is one of the reasons to consider an advanced CMS like eZ publish.

Myxt Web Solutions
http://www.myxt.nl

Marc Boon

Friday 12 May 2006 3:40:10 am

About this edit/review/publish workflow. How does that work in practice? Is it possible to review the entire site before publishing, like you do on a staging server? Or do you have to review every node by itself in the admin preview context? The latter would be highly undesirable.

I am trying to implement a staging approach, where the staging server is reached by a (non-public) subdomain of the live site. After approval, the live site is updated by regenerating
the static cache. The public production site's domain root is the folder containing the static cache, so this public site is truly static (no php or database access at all). I needed to add some url-rewriting rules for javascript, stysheets and images which reside in the design and var/storage directories, but these files are all completely static too.

I have the impression that my solution is not the way eZ publish is supposed to work, but I don't know how to setup a staging server using workflows. Tips and ideas welcome!