WiKit and TclKit were designed to run ''out-of-the-box'', with no installation or configuration whatsoever.  The installation is just like for local use, but you will need to work around the limited permissions provided by some web servers.

There are two issues:
   1. Where to put the WiKit file and how to let it find TclKit.
   1. Accesssing and altering the database embedded in WiKit.

----
If your server does not let you run scripts under your own ID:
	* Make sure the WiKit file is executable and writable by all: '''chmod a+rwx wikit.tkd'''
        * Make sure WiKit is allowed to create a lockfile next to it (called ''wikit.lock'')

If your server requires CGI scripts to end in ".cgi":
	* Just rename "wikit.tkd" to '''wikit.cgi''', since WiKit will work under any name

If your script doesn't work because it can't find TclKit:
	* You'll have to write a small wrapper.  Here's a "wikit.cgi" script which worked for me:
	#!/bin/sh
	exec /home/jcw/bin/tclkit /home/jcw/wikit/wikit.tkd

If you're wondering how WiKit can act as both a CGI script and as a Tk GUI app: what it does is look for an environment variable called "SCRIPT_NAME".  If present, it proceeds as a CGI process, else it turns itself into a Tk GUI application.