Date: Thu, 11 May 2006 13:08:11 +0200 From: Clement Laforet <sheepkiller@cultdeadsheep.org> To: Doug Barton <dougb@FreeBSD.org> Cc: ports@FreeBSD.org, pav@FreeBSD.org Subject: Re: HEADS UP for maintainers of web applications Message-ID: <20060511110811.GF79700@goofy.cultdeadsheep.org> In-Reply-To: <44630121.6030303@FreeBSD.org> References: <1147338576.799.9.camel@pav.hide.vol.cz> <44630121.6030303@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--iBwuxWUsK/REspAd
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Thu, May 11, 2006 at 02:17:21AM -0700, Doug Barton wrote:
> Pav Lucistnik wrote:
> > Hi people,
> >=20
> > it will soon become mandatory to stop installing web applications into
> > Apache specific directories, like ${PREFIX}/www/data,
> > ${PREFIX}/www/cgi-bin etc.
>=20
> How did those directories become "apache specific," and where was that
> decision and the prohibitive policy discussed and agreed to?
As Pav said previously, they are installed by apache. We have reasons
to get rid of this:
- Apache is not the unique web server. lighttpd seduces many people=20
- Web application are bigger and more complex.
- Where are installed your web apps/front end?
${PREFIX}/share/${PORTNAME} like nagios or cacti?
So you have to hack apache 2* conf. It's far from being=20
intuitive.
${PREFIX}/www/data/${PORTNAME}?
data is not in MTREE...
${PREFIX}/www/${PORTNAME}?
I'm also thinking about making apache ports I maintain more flexible=20
is the post-install stage, I'd like to see more automated tasks,=20
specially for installations of modules, support of mac_bsdextended(4),=20
out-of-the-box apache configuration for webapps and such.
With a "strict" hierarchy, we can do it.
OTOH, www/apache22 doesn't support old layout, and many users
complained, because they were stuck with apache2* ports ACL (it's
locked to DocumentRoot which is ${PREFIX}/www/apache22/). This
situation sucks and I'm the one to blame. But I don't think I'll go
back to ${PREFIX}/www/{data,cgi-bin,icons} and its symlinks mess.
I'll surely add a misc/webhier or so to fix this issues, and it will
surely help non-apache webservers ports to provide a coherent web
hierarchy... ... and fix the ugly cgi-bin issue too (cvsweb problems)
clem
--iBwuxWUsK/REspAd
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)
iD8DBQFEYxsbsRhfjwcjuh0RAoX2AKDbSpnaYrmN7M5szcU9f+FlGUkcfQCg8Wng
IWJ0miJfSP+fL4BGTQuQdjs=
=jvn8
-----END PGP SIGNATURE-----
--iBwuxWUsK/REspAd--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060511110811.GF79700>