Skip to Content.
Sympa Menu

sm-discuss - [SM-Discuss] clean up httpd.conf and adding and removing websites

sm-discuss AT lists.ibiblio.org

Subject: Public SourceMage Discussion List

List archive

Chronological Thread  
  • From: "David Michael Leo Brown Jr." <dmlb2000 AT excite.com>
  • To: sm-discuss AT lists.ibiblio.org
  • Subject: [SM-Discuss] clean up httpd.conf and adding and removing websites
  • Date: Mon, 28 Feb 2005 12:42:03 -0500 (EST)


I know this has been talked about on and off before, but I would like to
seriously get this started.

Right now httpd.conf is very large and cluttered also we don't provide
choices to add phpmyadmin phppgadmin, and the like, to apache root or not.
However I wouldn't like to see more questions being asked of the user.

I propose to change the /etc/httpd directory adding directories
modules-available and modules-enabled along with sites-available and
sites-enabled, might recognize this from debian. The spells would add config
files to either sites-available or modules-available automatically then it
would be up to the user to copy or link the config files to the sites-enabled
or modules-enabled directories, the httpd.conf file would also by default
source all files in the sites-enabled and modules-enabled directories.

Also I propose the same sort of approach to apache root. Adding a directory
/usr/share/apache[2]/httpd.d where all sites would be installed then
requiring the user to link from there to where ever they want. (Seth I think
you were concerned about this)

Since apache is one of linux's biggest security risks (of the few security
risks that there are :) I think this approach would give more power to the
user and still provide unattented and safe installs without adding more
questions.

Let me know what you think, I'm sure most of you will ;)

- David Brown
dmlb2000*




_______________________________________________
Join Excite! - http://www.excite.com
The most personalized portal on the Web!




Archive powered by MHonArc 2.6.24.

Top of Page