NOTICE: You are viewing a page of the openwetware wiki. Our "dewikify" feature makes a wiki page appear as a normal web page. In April 2017, this feature will GO AWAY and this URL will redirect to the source URL on our wiki. We're sorry for the inconvenience.

Subwikis is a different solution from having private pages on openwetware but I believe it solves all the problems with private pages (and more). It also touches on the issue of the openwetware software distribution. The basic idea is to host wikis for others. Subwikis on OpenWetWare is technically possible and already implemented using unified OWW login (through OpenID).

We have * be a place for subwikis. People can request a subdomain, let's say SUBWIKI so they can go to to get to their wiki. The subwiki can be setup however one wants such as its permissions. A subwiki can be completely private (i.e. requires login just to read), can be like openwetware which requires login to edit but the user list is controlled by someone else (so essentially a lab can lock down pages that only they can edit), or can be accessible to anyone with an OWW account. For example, check out the test wiki. This wiki requires log in to read but everyone with an OWW account can log in to view and edit that wiki. The test wiki demonstrates the OWW login mechanism and separate permissions and database.

On the technical side, creating and managing the wiki is easy. To create a wiki, run on the server /data/web/admin/ <wikiname> <oww_user> where wikiname is the new wiki name (e.g. test) and oww_user is the OWW username that will become the sysop of the wiki (e.g. austin). The script does the following: create a new mysql user/password, a new directory to store the subwiki's file uploads (images directory), and a wiki configuration file that includes the database username/password. The subwiki uses the same mediawiki installation as openwetware and inherits the same configuration file (including extensions). Of course anything can be overriden by the wiki specific configuration file, but the default is to create an empty, completely separate wiki in terms of database and uploads, yet uses the exact same code base and shares the same settings.