|File backend structure configuration.|
|Introduced in version:||1.19.0|
|Removed in version:||still in use|
|Default value:||array() (FSFileBackend is registered in another way)|
|Other settings: Alphabetical | By function|
This is an array ofconfiguration arrays. Each backend configuration has the following parameters:
- A unique name for the backend
- The file backend class to use
- A unique string that identifies the wiki (container prefix)
- The name of a lock manager (see $wgLockManagers)
- Additional parameters are specific to the class used.
- Taken from DefaultSettings.php
There are two particularly important aspects about each backend:
- Whether it is fully qualified or wiki-relative.
By default, the paths of files are relative to the current wiki, which works via prefixing them with the current wiki ID when accessed. Setting 'wikiId' forces the backend to be fully qualified by prefixing all paths with the specified value instead. This can be useful if multiple wikis need to share the same data. Note that 'name' is not part of any prefix and thus should not be relied upon for namespacing.
- Whether it is only defined for some wikis or is defined on all wikis in the wiki farm. Defining a backend globally is useful if multiple wikis need to share the same data.
One should be aware of these aspects when configuring a backend for use with any basic feature or plugin. For example, suppose an extension stores data for different wikis in different directories and sometimes needs to access data from a foreign wiki's directory in order to render a page on given wiki. The extension would need a fully qualified backend that is defined on all wikis in the wiki farm.