Hi,
the database on the production server cannot be read-only, even its
you won't do any changes on it Jahia still needs to write a few
things in the DB. You can still however replicate you DB from local
master to production DB, but how frequently will the syncrro between
the 2 mysql take place ?
Basically, when you write something on the local server, Jahia will
flush some internal caches, and this needs to be transmitted to the
production server through the JMS server, but if the data in the
production mysql DB have not yet been updated, you may not have the
correct data displayed.
Michel
I am setting up a cluster of Jahia servers, one for authoring and
one for production. I have read the Jahia Clustering manual and was
wondering whether it is possible to do the folllowing:
The authoring server connects to localhost mysql database which is a
master that replicates to the production server. This jahia
instance both reads and writes content.
The production server connects to localhost mysql database (read
only) which is replicated from authoring. No changes will be done
on the production server - only reading.
Will the production server have any problems with the read only
nature of the underlying database?
Thanks
