Setting up a wiki

At the bottom left corner and bottom right corner of this page are links to Monobook and Dokuwiki. Monobook is the code that makes everything look pretty, Dokuwiki is the underlying code that drives the wiki. Using the respective links, you will find all the downloads you need together with installation instructions. The basic idea:

• put the wiki folder from Dokuwiki into your public_html folder.
• change the security settings of the wiki folder to allow public access (read and write).
• run install.php from your browser (gives the wiki a name, sets the administrator, make the wiki publicly viewable but not publicly edited, makes sure media gets saved to the right place etc.)
• put the Monobook folder in the correct location of the wiki folder (
• put a Monobook plug-in in the correct folder (the plugin runs the navigation sidebar).
• open your wiki home page from a browser and set preferences (eg. choose the monobook template, disable open registration, turn off “Compact CSS and Javascript files”).
• start creating pages.

Upgrading is very easy. Download all the folders/files for the upgraded wiki. Drag theses into the existing wiki folder that is in public_html. This will replace all out-of-date files with the newer files of the same name. This will not overwrite any content because content files are not present in a downloaded wiki package.

http://wiki.splitbrain.org/wiki:install:upgrade

• Change the navigation box: There should be an [edit] button. Otherwise go to public_html\wiki\data\pages\wiki\navigation.txt and change the list (or adjust permissions).
• Change the top left corner image: go to public_html\wiki\lib\tpl\monobook\user\logo.png, this image name and location is referenced in the code.
• Set permissions on the server http://wiki.splitbrain.org/wiki:install:permissions

The wiki stopped working once (the navigation menu wouldn't show up and images would not display). There was a problem with files being cached on the server. At OSU, user directories are stored on NFS volumes on the main login server, and mounted to the web server(s). If a network problem occurs, the file cache can be damaged, and cause odd behaviors. The cache was cleared the problem was resolved.