This section deals with deploying Codestriker under IIS, as a CGI script. These instructions were performed on a Windows 2000 machine, so hopefully this provides an indication as to what needs to be performed for other Win32 configurations. Startup the IIS configuration application by going to "Control Panel" -> "Administrative Tools" -> "Internet Services Manager". Like the Apache configuration, the webserver needs to be told where to find the Codestriker CGI script, and where to find the associated CSS and html help files.
Assuming you are deploying Codestriker under the "Default Web site", right-click this entry on the left hand frame of the window, and select "New" -> "Virtual Directory" -> "Next". Enter in codestriker into the Alias textfield, then click "Next". Then enter the cgi-bin directory of your unpacked Codestriker distribution into the "Directory" textfield, then click "Next". Make sure the "Execute" access permission checkbox is selected, then click "Next", click then "Finished".
It is important that the codestriker virtual directory is setup to be able to execute Perl scripts. Right-click the codestriker virtual directory and select "Properties". Click on the "Configuration..." button. Check that there is an entry for .pl files, and that the "Executable Path" entry looks like (substitute the path to your local Perl installation):
C:\Perl\bin\perl.exe "%s" %sIf there is no mapping for .pl files (which would be odd, since the ActiveState install does this for you automatically), add a new entry in with the above setting, limited to "GET,HEAD,POST". Make sure you enter the quotes, as shown above.
Follow a similar process for the codestrikerhtml directory. Right-click "Default Web site" and select "New" -> "Virtual Directory" -> "Next". Enter in codestrikerhtml into the Alias textfield, then click "Next". Then enter the html directory of your unpacked Codestriker distribution into the "Directory" textfield, then click "Next". Make sure the "Read" and "Browse" access permission checkboxes are selected, then "Next", then "Finished".
Ensure the security for the two virtual directories codestriker and codestrikerhtml are appropriate for your site. Right-click on each directory, and select "Properties", then the "Directory Security" tab. Click the "Edit..." button and make the appropriate changes for your deployment.
Right-click "Default Web site" and select "Start" if the website is not currently running, and test it.
Further information on setting up IIS with Perl CGI can be found from http://www.mhuffman.com/notes/cgi/cgi_config.html.