Hello, as the new admin/grunt/bofh for xwiki.com, i'll have soon to perform some administrative stuff on a running xwiki installation. During past experiences with such database intensive applications, i found out that most of the downtimes can be avoided by simply putting the whole server in read-only mode. I've put up a topic with requirements and implementation notes here : http://www.xwiki.org/xwiki/bin/view/Dev/ReadOnlyServer let me know what are you thoughts. I'm specifically looking for the best idea to appropriately explain users they are running on a read-only server. Thanks in advance, Erwan
a great idea! solves the backup problem in an elegant way! why did i not have it myself? reason: if somebody clicks some "edit" thing, the message entered when switching to read-only mode shows up. -solo. On 6/25/05, Erwan Arzur <[email protected]> wrote:
Hello,
as the new admin/grunt/bofh for xwiki.com, i'll have soon to perform some administrative stuff on a running xwiki installation. During past experiences with such database intensive applications, i found out that most of the downtimes can be avoided by simply putting the whole server in read-only mode.
I've put up a topic with requirements and implementation notes here :
http://www.xwiki.org/xwiki/bin/view/Dev/ReadOnlyServer
let me know what are you thoughts.
I'm specifically looking for the best idea to appropriately explain users they are running on a read-only server.
Thanks in advance,
Erwan
-- You receive this message as a subscriber of the [email protected] mailing list. To unsubscribe: mailto:[email protected] For general help: mailto:[email protected]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
participants (2)
-
Erwan Arzur -
solo turn