31 Jan
2011
31 Jan
'11
7:48 p.m.
On 01/31/2011 07:18 PM, Paul Libbrecht wrote:
Hello list,
I have had a short attempt:
set GLOBAL read_only=true;
on the MySQL that runs my curriki and it kind of works.
A few exceptions are thrown at the beginning but otherwise it seems to render well.
The interest is that it could allow some of the web requests to be served by a database
that is a slave of the main database, in live synchronization with the master MySQL.
You mean that the public wiki reads data from the read-only database,
which is actually updated by cloning another read-write database updated
from a private wiki? That's an interesting idea for securing a public
server.
You should also set in xwiki.cfg:
xwiki.readonly=1
This might reduce some of the errors that you get, although there's a
lot of code that ignores this setting. It would be nice if you could
report (on jira) what exactly breaks so that we can fix it properly.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/