httpd-docs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jorge Schrauwen" <>
Subject Re: Apache docs wiki
Date Fri, 22 Sep 2006 15:56:14 GMT
Hi all,

Bit more info as to why:
I visit some popular httpd boards (, usually
users as about the same question.
How do I configure a DAV server, How do I password protect a folder, how to
I force location /someloc to be always ssl, how do I create Aliases... this
list goes on and on.

Usually links are provided to resource some counter dicting eachother, some
just don't work and so on.
So I had the idea of create a wiki for this that everyone could post to, fix
broken piece of code, extend them...

I chatted about this with some friends and the they linked the idea. But we
also agreed that hosting it ourselves wouldn't be get as much community
activity as a official one at httpd.a.o.

I'd also be willing to help moderate the wiki.

Here are some links that use the same code examples:
The need to upgrade from http to https

Due to a being a bit short on time today i can't provide more example but
just googling should turn up a few.


On 9/22/06, Rich Bowen <> wrote:
> This has come up before, so no doubt some folks have already made up
> their minds, having seen the subject line.
> Jorge Schrauwen, who has written a number of httpd tutorials,
> articles, etc., was asking on #httpd-dev about the possibility of a
> docs wiki, where people can provide configuration samples, ideas,
> suggestions, mini-howtos, which would eventually feed into the
> official docs. He's planning to do this anyways, but wondered if
> there was a way that he could do it within the confines of the
> existing docs project, rather than hosting it himself. Scratch an
> itch, and give back to the community at the same time.
> I'd like to propose that we create a portion of for
> this purpose, and give it a test run for a while, see if it works,
> and make a determination after a while on whether it is indeed
> valuable. I would be glad to be the (moderator? overseer? big
> brother?) whatever the term is, and check in on it for
> appropriateness and correctness of the contributions.
> I created specifically for this purpose
> - as a scratchpad for myself - and it has developed into a more
> useful resource than I planned, which is to say that folks other than
> myself are using it for reference. And the goal there is still to
> have this stuff feed back into the docs.
> Having an official place to do this prevents (or reduces) the
> proliferation of alternate doc sites with incorrect, misleading, or
> outdated information. At least, that's my hope.
> Thoughts?
> --
> Come to ApacheCon US 2006!


View raw message