Kumu technical about

From Help With Kumu Wiki

---

Revision as of 23:49, 21 February 2013

How the Kumu wiki server works.

Brock University's kumu wiki server was designed to allow members of the Brock University request wikis that are based on the popular Mediawiki software that powers Wikipedia. Requests are promptly processed by members of the CPI and a wiki is created through a web-based workflow. Here are basics of how the kumu wiki server works.

The system needs an update, but here are the basics.

How Wikis Are Served

There are currently over 400 wikis. This corresponds to over 400 databases, but only one copy of the Mediawiki software.

When a request is created one of the Kumu Wiki Settings that requesters are asked for is a URL/namespace (which is automatically created, but can be modified by the requester). In the Apache web server configuration an alias is entered between the URL/namespace and the Media wiki source.

When a visitor to the wiki request a wiki page/article the alias directs the Apache server to load the Mediawiki application. The Mediawiki localsettings.php file does not contain the conventional configuration settings, instead it contains an include to a common configuration file and a common collection of function.

Two of the included functions are:

1. get_local_wiki() - parses the URL to get the namespace for the wiki
2. setup_wiki($namespace) - takes the namespace and looks up the settings and sets the global variables that would normally be found in localsettings.php

The settings loaded by setup_wiki() includes those outlined in Kumu Wiki Settings and things like the database name, which matches the namespace.

How Wikis Are Created

Members of the Brock University community can request wikis at https://kumu.brocku.ca/request/ . Requesters are asked to input information such as those found in Kumu Wiki Settings. A recent development has been the ability to request a number of wikis en mass. This is to allow for a number private groups to collaborate in a wiki that will likely be shared after the work is done - a use never anticipated when the system was created.

The request comes to the attention of the CPI.

If the request can be approved the approval processes automates the following:

• Adding an alias to the Mediawiki source based on the namespace/ULR
• Creating the unique database and copying the basic contents from an SQL export
• "Injecting" the requester into the wiki
• Notifying the requester

Other Modifications

• A custom IP banning system that makes use of http://stopforumspam's database
• A common spam terms list
• Brock University CAMPUS ID-based authentication
• The ability to allow requesters to modify Kumu Wiki Settings and to allow a delegate
• The ability to "inject" users