Manual:$wgReadOnly

Details
Functionally this setting is the same as  , but uses a variable instead of a file.

If set to a string in "LocalSettings.php",  disallows editing, displaying the string given as the reason. The reason provided is preceded by the contents of MediaWiki:Readonlywarning.

The above example locks the database and provides a readonlyWarning>MediaWiki:Readonlywarning|default statement on edit pages and also gives the included string  as an explanation for why the database was locked. Wikitext is allowed in this string and will be rendered when the read-only warning is shown which can be used to provide links or highlight upgrade notifications.

In contrast to its name, this settings does not make the database read only! Even if $wgReadOnly is set, extensions, API scripts and other cachable events can write data nonetheless.

DB caching
Caches that use the database cannot be written to during read only mode, which could prevent more than just editing (depending on the configuration, logging in or even viewing pages). This can be avoided by disabling cache, albeit at the cost of making your wiki slow. This can be accomplished with the following settings in LocalSettings.php:

If you want your wiki to be fast, while still not using the DB, you should consider using something like Memcached. See   and   for details. If you want to enable logins while the database is readonly, at least   needs to be set to some real non-DB caching mechanism.