I want to learn how to set up a server on my Windows 98 machine so I can run wikit under cgi. It looks like setting up the server is my first step. This page will document my learning process about servers. I am going to look at Personal Web Server first and see if I can get that going. Any tips? Point me in the right direction? --DGR 10/1/00

OK, I found SimpleServer:WWW for Windows at http://www.analogx.com/contents/download/network/sswww.htm and am installing it as my standalone server. --DGR 10/3/00

-----
As this is the tclers wiki, a link to [tclhttpd] is more than needed...
-----
May 10, 2002 - There are no doubt lots of ways to get there.  Here's the approach I would suggest:
   * get tclhttpd as a scripted document [http://mini.net/sdarchive/tclhttpd.bin]
   * get the tclkitsh.exe runtime [http://www.equi4.com/pub/tk/tclkitsh-win32.upx.exe] (note that you don't want the tclkit GUI version)
   * get the latest wikit, see "nwikit" at [http://www.equi4.com/wikit/]

Now, "tclkitsh tclhttpd" ought to start the web server (port 8015 is the default, I think).  You should be able to see it by browsing to http://127.0.0.1:8015/.

The way to start wikit, is to create a bat file, containing:
	@tclkitsh nwikit.bin %1 %2 %3
When launched as CGI, it will do the right thing (such as create a wikit.tkd to hold the wiki page contents).  Note that you need tclkit, not tclkitsh, if you want to use wikit in local Tk mode (i.e. "tclkit nwikit.bin").

The missing piece is that I'm not familiar enough with tclhttpd to say how one connects both pieces together... (if you are reading this and know how to make it all work together, please feel free to amend this page).

-[jcw]

----
December 16, 2002  I tried this.  Here are my immediate results:

tclhttpd appears rather difficult to turn into a .kit .  But it's already been done for a modified version:  http://mini.net/sdarchive/tclhttpd.kit  I'll try to follow JCW's advice after I get that kit working.


When I run tclhttpd from tcl and call wikit using exec like

 exec <path> tclkitsh.exe <path> wikit.kit

then the output doesn't ever get to the socket.  

There is a possible explanation for this in the ActiveTCL documentation.  exec under Windows will not send output to sockets, the output is sent to the console or discarded.  

When I take a working CGI file that does

 #!/bin/sh
 # \
 exec tclsh8.3 "$0" ${1+"$@"}

and remove the magic # lines at the beginning, then the document contains no data.  It fails just as wikit fails.  Under Windows, tclhttpd depends on this magic to avoid exec's.

I can see the wikit output as follows:  I redirect wikit output to a temporary file and later dump the file to stdio.

 exec > rrrr.txt ''path''/tclkitsh.exe ''path''/wikit.kit
 set in [open rrrr.txt]
 fcopy $in stdout
 close $in

It would be far better to integrate wikit into tclhttpd.  tclhttpd is designed to make it easy to add custom modules.  But wikit without threads was said to use CGI to avoid blocking problems.  So to avoid those problems when wikit is part of tclhttpd, it might be necessary to use threads.    Jonah Thomas

----
[CL] has set up tclhttpd on vanilla Win* machines several
times, and found CGI configuration a snap.  The only detail
he remembers for today, though, is that reading the tclhttpd
documentation sufficed.  Perhaps he'll return later with
a fuller explanation.