Difference between revisions of "Mediawiki on biowikifarm"

From Biowikifarm Metawiki
Jump to: navigation, search
(Created page with 'Mediawiki setup on this server is different from many other installations. # The code is checked out and upgraded using Subversion commands. Two checkouts exist: ## /usr/share/m...')
 
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
Mediawiki setup on this server is different from many other installations.  
 
Mediawiki setup on this server is different from many other installations.  
# The code is checked out and upgraded using Subversion commands. Two checkouts exist:
+
# The code is checked out and upgraded using git Subversion commands. several version specific checkouts exist, e.g.
## /usr/share/mediawiki/ for most wikis on the farm ("production version")
+
## /usr/share/mediawiki26/  
## /usr/share/mediawikistaging for testing upgrades. Only http://biowikifarm.net/test/ is using this.
+
 
# It is a wikifarm, meaning many installations share the same codebase.  
 
# It is a wikifarm, meaning many installations share the same codebase.  
 +
 +
The following information is still partly correct, but not verified after changing from subversion to git and using version-specific checkouts.
  
 
==The code branch==
 
==The code branch==
  
 
Most parts of the checked out code should not be modified or patched, not even for a short time. Doing so would create local pending changes for subversion, and we '''do not commit ever'''. So the file will often be just excluded from the next version upgrade, causing all kind of interesting problems.
 
Most parts of the checked out code should not be modified or patched, not even for a short time. Doing so would create local pending changes for subversion, and we '''do not commit ever'''. So the file will often be just excluded from the next version upgrade, causing all kind of interesting problems.
 
However, some folders for extensions that are not available in the main mediawiki subversion repo can be freely changed. These are
 
* /usr/share/mediawiki/NonSvnExtensions/
 
* /usr/share/mediawikistaging/NonSvnExtensions/
 
  
 
In there you also find our "own" extensions, the  
 
In there you also find our "own" extensions, the  
Line 33: Line 30:
 
==Extensions==
 
==Extensions==
  
All mediawiki.org-subversion-managed extensions are already available as code in /usr/share/mediawiki/extensions. However, each extension requires an extra link inside /usr/share/mediawiki/phase3/extensions pointing to the corresponding folder in /usr/share/mediawiki/extensions. See [[Mediawiki installation]] for further information.
+
All mediawiki.org-subversion-managed extensions are already available as code in /usr/share/mediawiki/extensions. However, each extension requires an extra link inside /usr/share/mediawiki/phase3/extensions pointing to the corresponding folder in /usr/share/mediawiki/extensions.  
 +
 
 +
'''See [[Mediawiki installation]] for further information!'''
 +
[[Category:MediaWiki]]

Latest revision as of 15:12, 23 March 2017

Mediawiki setup on this server is different from many other installations.

  1. The code is checked out and upgraded using git Subversion commands. several version specific checkouts exist, e.g.
    1. /usr/share/mediawiki26/
  2. It is a wikifarm, meaning many installations share the same codebase.

The following information is still partly correct, but not verified after changing from subversion to git and using version-specific checkouts.

The code branch

Most parts of the checked out code should not be modified or patched, not even for a short time. Doing so would create local pending changes for subversion, and we do not commit ever. So the file will often be just excluded from the next version upgrade, causing all kind of interesting problems.

In there you also find our "own" extensions, the

  • IdentificationTool
  • TemplateParameterIndex, and
  • MobileKey. The latter exists in three folders:
    • MobileKey (backup only, not active)
    • MobileKeyV1 (conservative version, to be changed only very carefully, reachable as special page!)
    • MobileKeyV1 (to become a "new" version, reachable as special page!)

Pages to reach the Mobile Key are, e.g., http://www.keytonature.eu/wiki/Special:MobileKeyV1 and http://www.keytonature.eu/wiki/Special:MobileKeyV2 or http://www.offene-naturfuehrer.de/wiki/Special:MobileKeyV1 and http://www.offene-naturfuehrer.de/wiki/Special:MobileKeyV2

The www-root

The www-root is /var/www. Inside we directly have root folders, plus folders for the virtual host. All folders starting with v mean virtual host (e.g. v-on and v-k2n). Most wikis are in a single-letter folder inside a virtual host folder, e.g. /var/www/k2n/w. Some wiki are setup for the apache root, these "root wikis" are metawiki (this one, http://biowikifarm.net/meta/), testwiki (http://biowikifarm.net/test/ - the ONLY wiki running against /usr/share/mediawikistaging/)

Inside the wiki folders you find mostly symbolic links to the code-checkout. However, LocalSettings.php, the cache and media folder are local to each wiki. This creates the "wikifarm". Note that because of this setup, maintenance scripts need to be run with special parameter, see Mediawiki_maintenance for examples.

Also note, that significant information is shared by all wiki. This information is stored directly in the www-root, in MediaWikiCommonSettings.php, which is linked into each LocalSettings file.

Extensions

All mediawiki.org-subversion-managed extensions are already available as code in /usr/share/mediawiki/extensions. However, each extension requires an extra link inside /usr/share/mediawiki/phase3/extensions pointing to the corresponding folder in /usr/share/mediawiki/extensions.

See Mediawiki installation for further information!