wiki on windows

[Jeremy C. Reed]

On Thu, 11 Jan 2007, Josh Coffman wrote:

> I think it makes sense for us, versus some document in source control 
> that everyone needs to get latest on when it changes. I wasn't really 
> concerned about supported web browsers. I just don't want to have to 
> install and setup a lot of other services. We'd probably prefer a 
> file-based wiki more than one that uses another database.

I use simple ikiwiki.

But it does use the filesystem to save data and it uses your own choice 
of revision control system for your source control (like subversion, git, 
rcs, tla, arch). That is a great feature since users can access/commit 
changes without using the wiki interface if desired.

> I don't want to setup CGI and PERL and PHP and Apache on windows. 
> Especially on windows, I avoid installing too much software/services 
> because its just more to maintain and more potential security holes.
> 
> MoinMoin sounds about right because it only needs Python for use by a 
> small group. That's assuming IIS will know how to Python.

I think this is a partial misunderstanding.

The original email said "use/install on Windows". If you install on 
Windows then your Windows must be setup with a webserver (like you mention 
IIS) and to do CGI. Whether or not you use Apache is your own choice. But 
you must use Perl, Python, or PHP on the Windows webserver if that is what 
your chosen wiki backend uses.

Personally, I'd just use some cheap, headless box running open source 
Unix to provide the wiki for your Windows office.