Skip to Content.
Sympa Menu

sm-discuss - Re: [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: Re: [SM-Discuss] clean up httpd.conf and adding and removing websites
  • Date: Mon, 28 Feb 2005 17:27:05 -0500 (EST)


>I very much dislike the Debian Way for doing apache. ;) What I'd
>rather is a layout such as this:
>/etc/httpd/
> /<config files for apache>
> /modules/
> /<spell>/
> /<spell>/<config files for spell (e.g. php)>
>
>Perhaps remove the /modules/ abstraction to just have
>/etc/httpd/<spell>/.
>
>Any package other than httpd that would like to install config files
>will install them to /etc/httpd/modules (e.g. subversion, php, etc.)
>and the user would have to add the proper "include modules/<conf
>file>" to /etc/httpd/httpd.conf, rather than having extra
>config_queries that ask the user if they want to enable it and having
>symlinks and directories reminiscent of the /etc/rc.d days.
>
>As for the DocumentRoot installation, I like the idea of not having
>packages install themselves to Apache's default DocumentRoot
>(/usr/share/apache{,2}/htdocs), and thus being accessible before the
>admin might have the chance to properly configure and secure it (e.g.
>php{my,pg}admin).

Okay, so what I think we figured out a little on the mailing list and a
little on irc... here's the break down

/etc/httpd/
/httpd.conf
/modules/<config file for modules> (eg mod_php)
/sites/<config file for sites> (eg php{my,pg}admin)

No symlinks anywhere and the modules won't directly edit httpd.conf (fix php
spell) the spells would simply add the config files to their appropriate
place.

This puts the load on the user to include the proper files in httpd.conf or
we can develope a telapache script that would edit/change it's own
telapache.conf that can be included in httpd.conf.

Apache document root, spells will install to /usr/share/apache{,2}/httpd.d
directory, this puts the load on the user to edit the httpd.conf or link from
the apache root to the script directory or telapache script could also handle
this.

I would like to edit httpd-dev spell in devel because it is a dev apache and
not "stable" apache, besides I don't think anyone else but me uses it... ;)

- David

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




Archive powered by MHonArc 2.6.24.

Top of Page