httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Octavian R√Ęsnita <orasn...@gmail.com>
Subject Re: [users@httpd] Re: GUI for configuring Apache httpd by editing httpd.conf
Date Mon, 16 Feb 2009 19:46:50 GMT
I think that we should not discourage anyone that wants to create such a 
tool.
It can be used by beginners that learn how to configure the server with a 
GUI, then find how the httpd.conf is created, but this only if that tool can 
do absolutely everything a text editor can do.

If that tool can't do absolutely everything, than it is an evil tool for the 
beginners because it will make them think that what it can do is everything 
Apache can do, or they won't care that there are possible more advanced 
configurations, which is not good.

It is just like a kind of beeing pleased with what Ruby on Rails can do, 
without reaching to know how more things Catalyst framework can.

Octavian

----- Original Message ----- 
From: "Krist van Besien" <krist.vanbesien@gmail.com>
To: <users@httpd.apache.org>
Sent: Monday, February 16, 2009 8:44 PM
Subject: Re: [users@httpd] Re: GUI for configuring Apache httpd by editing 
httpd.conf


> On Mon, Feb 16, 2009 at 6:26 PM, Peter Schober
> <peter.schober@univie.ac.at> wrote:
>
>>  It's certainly not for me. But other than stating the reasons why I
>> think this is not practical and helpful in the real world, why should
>> I try to convice others to /not/ write duch a thing? Because "some
>> things should not be easy"?
>
> Thinks should be easy. That is the point. Given the aim of the apache
> webserver, and its intended audience the current way of configuring
> apache is by far the easiest.
>
> Apache is a tool for webserver admins, not for average computer users.
> With apache if I need to explain to one of our operators how to deploy
> a change to all our webservers all I need to know is if said person
> has basic unix knowledge (which is the case, or we wouldn't let them
> near our servers) and all I need to provide in my workorder is "copy
> atached file to /etc/apache2/sites_available and then execute
> apache2ctl graceful.
> With a gui I either need to know if the target of my workorder is
> familiar whith the gui, and if I'm not sure I have no other option of
> writing a complete walk through, with screenshots. That I consider a
> waste of my time.
> So my preference for the command line and text files has nothing to do
> with elitism or nostalgia. It has everything to do with two things
> that are very important in a production environment: Simplicity and
> repeatability.
>
> Krist
>
>
> -- 
> krist.vanbesien@gmail.com
> krist@vanbesien.org
> Bremgarten b. Bern, Switzerland
> --
> A: It reverses the normal flow of conversation.
> Q: What's wrong with top-posting?
> A: Top-posting.
> Q: What's the biggest scourge on plain text email discussions?
>
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
>   "   from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
> 


---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


Mime
View raw message