Date: Thu, 11 May 2006 09:38:13 -0500 From: "Larry Rosenman" <ler@lerctr.org> To: "'Lupe Christoph'" <lupe@lupe-christoph.de>, <pav@freebsd.org> Cc: ports@freebsd.org Subject: RE: HEADS UP for maintainers of web applications Message-ID: <00ba01c67508$88618b40$0202fea9@aus.pervasive.com> In-Reply-To: <1147356487.4463454775612@buexe.b-5.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Lupe Christoph wrote:
> Quoting Pav Lucistnik <pav@freebsd.org>:
>
>> it will soon become mandatory to stop installing web applications
>> into Apache specific directories, like ${PREFIX}/www/data,
>> ${PREFIX}/www/cgi-bin etc.
>
>> All web applications should be now installed into
>> ${PREFIX}/www/appname. Please keep it in mind when preparing your
>> next port update.
>
> Are you saying that a cgi-bin should go into ${PREFIX}/www/appname,
> too? That would require the sysadmin to set ExecCGI for all of
> ${PREFIX}/www.
>
> Perhaps you expand on this a little and tell me where the following
> should go:
> 1) HTML files that are to be server by ${HTTPD}
> 2) cgi-bin's that are to be executed by ${HTTPD}
> 3) Data that is not to be accessible either way like e.g. a htpasswd
> file.
>
Can we also get a clear definition on what each app (for example Gallery2,
phpPgAdmin, etc)
is supposed to supply to be able to be upgraded when Major Apache versions
(like 2.2) are introduced.
I've had a hell of a time setting up symlink hell for some of these, in
addtion to knowing where
TPTB want us to set up httpd.conf file(s) and equivalents, such that we can
*SAFELY* use portupgrade to keep
up with things.
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 512-248-2683 E-Mail: ler@lerctr.org
US Mail: 430 Valona Loop, Round Rock, TX 78681-3893
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00ba01c67508$88618b40$0202fea9>