From: Stuart Herbert <stuart@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-core] Re: [gentoo-dev] [GLEP] Web Application Installation
Date: Tue, 5 Aug 2003 11:21:42 +0100 [thread overview]
Message-ID: <200308051121.42307.stuart@gentoo.org> (raw)
In-Reply-To: <20030805034656.GB19847@cherenkov.orbis-terrarum.net>
[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 2144 bytes --]
On Tuesday 05 August 2003 4:46 am, Robin H.Johnson wrote:
> Put me on the list as well, I've spent long enough writing PHP webapps
> that I know what is going on, and I'm hoping to spear-head the
> webapp-config tool once the debate it all settled.
Excellent. Anyone else feel like hacking webapps at all? How well covered
are we for supporting mod_perl and mod_python based apps right now?
> Also, so that Max and you know, I have definetly been following your
> discussion about the GLEP, eclass and webapp-config,
Good. You've got a lot of first-hand experience that I think's important to
ensuring that what we put in really hits the mark.
> One clarification however, multiple instances of webapps are NOT
> nessicarily across vhosts, in several cases, you may want multiple
> instances of a webapp on a single vhost or many other variants of that.
> The administrator would be telling us exactly where he wants us placed,
> and we can ask for more information as needed if we can't figure it out.
Good point. We'd need to test each webapp to make sure that it doesn't expect
to at a hard-coded place relative to the docroot. Some webapps, for example,
are hard coded to expect to be at the url http://<vhost>/, and break badly if
they're (say) placed at http://<vhost>/people/stu/.
> Part of this could possibly also be aided by a later config tool to
> create virtual hosts. I already have one that I use for my own setup,
> but it would need quite a bit of work for Gentoo purposes.
Maybe it's off-topic, but you'll probably have an answer that I don't. On my
boxes, I always use Apache's dynamic vhost support. Are there times/reasons
when dynamic vhost support isn't the way to go?
Best regards,
Stu
--
Stuart Herbert stuart@gentoo.org
Gentoo Developer http://www.gentoo.org/
Beta packages for download http://dev.gentoo.org/~stuart/packages/
GnuGP key id# F9AFC57C available from http://pgp.mit.edu
Key fingerprint = 31FB 50D4 1F88 E227 F319 C549 0C2F 80BA F9AF C57C
--
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-08-05 10:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-02 16:50 [gentoo-dev] [GLEP] Web Application Installation Troy Dack
2003-08-02 20:39 ` Robin H.Johnson
2003-08-02 23:11 ` [gentoo-dev] Re: [gentoo-core] " Max Kalika
2003-08-02 23:51 ` Stuart Herbert
2003-08-03 2:26 ` [gentoo-dev] " Max Kalika
2003-08-03 14:46 ` Stuart Herbert
2003-08-03 15:20 ` Max Kalika
2003-08-03 17:43 ` Stuart Herbert
2003-08-03 19:03 ` Max Kalika
2003-08-03 19:43 ` Stuart Herbert
2003-08-04 4:29 ` Max Kalika
2003-08-04 10:43 ` Stuart Herbert
2003-08-03 0:30 ` Austin Frank
2003-08-03 7:50 ` Tal Peer
2003-08-03 14:45 ` Don Seiler
2003-08-03 14:49 ` [gentoo-dev] Re: [gentoo-core] " Stuart Herbert
2003-08-05 3:46 ` Robin H.Johnson
2003-08-05 10:21 ` Stuart Herbert [this message]
2003-08-05 8:12 ` Troy Dack
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200308051121.42307.stuart@gentoo.org \
--to=stuart@gentoo.org \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox