[opencms-dev] Dynamic remote deployment (publishing) architecture

[Dan Liliedahl]

We have created a module that does exactly that.  It allows for 2 systems -
one on staging and one on production with separate databases.  We do this
because most people do not want their staging and publishing systems to use
the same DB.  Publishing occurs across the firewall.  If you do this
yourself, you will need to do custom version of the CmsVfsDriver class and
will need to change settings in the opencms.properties file to use it.  Our
module is currently in alpha until we release for our client.  At that point
we may make it available for others.

 

Cheers,

Dan

 

  _____  

From: opencms-dev-bounces at opencms.org
[mailto:opencms-dev-bounces at opencms.org] On Behalf Of Li Hai Tao
Sent: Friday, May 27, 2005 1:51 AM
To: opencms-dev at opencms.org
Subject: [opencms-dev] Dynamic remote deployment (publishing) architecture

 

Hi 

 

I am newbie to OpenCms, but i have played around with other commercial CMS
for one and half year. 

 

Now i am evaluating some java open source CMS and it looks OpenCms is better
than others. But when i went through its documentations, i didnot find
enough information about dymamic remote deployment or publishing
possibility. What i mean, instead of authoring and publishing in one
machine, seperate them into two or more machines.

 

Maybe there are three machines, two nodes for publishing behind IIS or
Apache with load balancing, one node exclusively for authoring. Once content
editors decide to publish their new web content, they publish them to two
remote nodes instead of his/her local machine. Last time, when i use the
commercial product, i can easily achieve this by proper settings.

 

I am thinking if i share the database between those three machines to
achieve this purpose. 

 

Can anyone enlighten me for this possibility and how ?

 

Thanks 

 

Ron 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://webmail.opencms.org/pipermail/opencms-dev/attachments/20050527/0f93fadc/attachment.htm>