Re: Ease of installation

Jim Hart wrote:
> Hi all,
> 
> One relatively easy thing to do to make awkiawki installation
> clearer is to develop multiple sets of instructions. For
> example, INSTALL.Apache, INSTALL.thttpd. Or, perhaps the
> install instructions should be a set of HTML pages with
> different sections for the different Web servers, and different
> options for different kinds of installs. Thoughts?

Certainly. And while investigating the various install options, we
could also describe, and clear up, the "wiki page Google indexing" 
problem. AFAICFO (as far as I could find out) Atte's pages are not 
indexed by Google, neither are mine, but Jim's and Johan's are. I 
think we should begin by comparing exactly how we did it.

> The current INSTALL file assumes, for example, that one has
> access to the cgi-bin directory. In a hosted situation, this
> isn't true. Even when not hosted, Jan chose to put his awki.cgi
> and awki.conf in /var/www/mywiki/. 

Yes, because I wanted to install multiple independent wikis each 
with their own configuration, and this was the only way I could 
think of. But I am not at all sure I did it the "best" way (Jim 
uses another way). To tell the truth, I experimented until it 
seemed to work!

>(I presume he configured Apache to allow CGIs in that directory.)

Of course. But there are various ways to do this, also.

> There should be instructions for how to set awkiawki up in 
> situations where one doesn't have access to cgi-bin.

Clear instructions about installing, and the various options, 
would make awkiawki much more valuable to users.

Regards, Jan


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click