[opencms-dev] openCMS replication

[CLB]

Pavel,

 

IMHO, a good alternative is to protect some distinguished URLs (like the
login URL) using some IP filtering technique (e.g. in the firewall).

 

HTH,

--mariano

 

 

-----Mensaje original-----
De: opencms-dev-admin at opencms.org [mailto:opencms-dev-admin at opencms.org]
En nombre de Kovalev, Pavel
Enviado el: Miércoles, 28 de Julio de 2004 03:22 p.m.
Para: opencms-dev at opencms.org
Asunto: [opencms-dev] openCMS replication

 

I hope the requirements we have are not too unique so anybody could help
me to make a decision on right approach to the solution.

 

Our client wants to have authoring environment in the intranet without
access to opencms admin from internet. It looks like the only solution
for this to deploy 2 instances of opencms – one for intranet where all
editors would have access to admin and another for production. 

 

Questions are:

-          how to disable admin on the production while still utilize
opencms functionality for site processing

-          would database replication (Oracle in our case)  be the base
way to deliver the data to the production instance

-          any other possible solutions for our situation, that won’t
require such complex architecture [aside of static export]

 

Thank you,

Pavel Kovalev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://webmail.opencms.org/pipermail/opencms-dev/attachments/20040728/68cb9880/attachment.htm>