[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Apache Configuration



Re,
> As (1) and (2) are being solved, (3) remains the only reason why
> Apache doesn't take the whole "market".
Not _only_, but yes, I've read many reports where Apache is called
hard-to-configure just because it lacks GUI. This seems to me a bit
unfair, because lack of GUI doesn't mean being hard to configure, as well
as presence of such doesn't mean easy to configure (take NT). But this is
reality, we have to conform ;).
 > 
> I thought about writing a module to support HTTP-based interactive
> run-time configuration for Apache. Of course, it must be very
> restrictive and secure: By default, it will deny any access from
> outside the same IP, and it will require a password, which will be
> compared to the password of the user who invoked the Apache (using
> the same mechanism of login and su).
i.e. root password most of the cases. Or better it would be to have
another password (just so root password won't travel via the Net
"secured" by Basic auth...)
> I don't want a simple interface which will have links to all the
> options at any point (e.g. links to all the directives in the root,
This one would be helpful also - for GUI-guys I mentioned before.
> links to all of the optional first arguments of the specific
> directive after choosing a directive, and so on). I am talking
> about a real friendly interface. In addition, a context sensitive
> help can be added easily; After all, there is already HTML
> documentation for each of the directives.
> 
> The only problem is that there are so many directives and options in
> Apache, so most of the people (including me) know only some of them.
well, httpd -h gives a list of config options. i.e. it does exist  
somewhere, and can be extracted. So module can do it, I suppose. And
should do so, i.e. directive list should in no way be hardcoded, and
should allow automatic or semi-automatic inclusion of new config
commands. Seems to be quite a bit of work ;)
> Although it reminds us how important is to have such an interface
> (since currently nobody uses these unknown options), it doesn't help
> me in developing this interface  :-(
And _developer_ surely has to learn them, nothing to do... ;)
> 
> Can anyone contribute to this voluntary project?  Someone who knows
> *all* the directives and options?   Does anyone have something to
> say about my idea?  I'll be glad to get feedback!
Well, O'Reilly's "Apache: The Definitive Guide" might be helpful. List of
all directives, and module writing guide.
As about volonteering - I would happily enter such a project, and take
some part of the work - in my copious free time ;) - if anyone
takes on himself to organise it.
Also, found on the net:
http://www.solucorp.qc.ca/linuxconf/	- configuration tool, claims to
have support for Apache. Didn't look at it - no time...
--
frodo@sharat.co.il	\/  There shall be counsels taken
Stanislav Malyshev	/\  Stronger than Morgul-spells
phone +972-2-5369213	/\  		JRRT LoTR.
http://www.sharat.co.il/frodo/   whois:SM719-RIPE@whois.ripe.net