Hi all,
I've been searching like mad through the docs for how to do something
that I know must be really simple. Let's say that I've added something
like that to httpd.conf:
PerlModule Some::Application
ServerNamesome.application
DocumentRoot /some/non_standard/path
Hi all,
I've been searching like mad through the docs for how to do something
that I know must be really simple. Let's say that I've added something
like that to httpd.conf:
PerlModule Some::Application
ServerNamesome.application
DocumentRoot /some/non_standard/path
On Fri, 30 Dec 2005 10:32:49 -0800
Curtis Poe <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I've been searching like mad through the docs for how to do something
> that I know must be really simple. Let's say that I've added
> something like that to httpd.conf:
>
>PerlModule Some::Application
>
On 12/30/05 1:39 PM, "Frank Wiles" <[EMAIL PROTECTED]> wrote:
> On Fri, 30 Dec 2005 10:32:49 -0800
> Curtis Poe <[EMAIL PROTECTED]> wrote:
>
>> Hi all,
>>
>> I've been searching like mad through the docs for how to do something
>> that I know must be really simple. Let's say that I've added
On Dec 30, 2005, at 10:39 AM, Frank Wiles wrote:
I'm not sure if it's what you're after, but have you thought about
using an Include in your httpd.conf?
I'll look into see what's involved with that. In the meantime, what
I'm basically trying to do is allow a user to download our app and:
Curtis Poe wrote:
> On Dec 30, 2005, at 10:39 AM, Frank Wiles wrote:
>
>> I'm not sure if it's what you're after, but have you thought about
>> using an Include in your httpd.conf?
>
>
> I'll look into see what's involved with that. In the meantime, what I'm
> basically trying to do is al
On Dec 30, 2005, at 11:06 AM, Michael Peters wrote:
Admirable goal, but may I suggest an alternative way to look at it.
Instead of
working with an existing apache (which may or may not have mod_perl,
mod_* or
may have config directives which will conflict with your assumptions
etc) why
not ha
On Dec 30, 2005, at 10:39 AM, Frank Wiles wrote:
Many distros now setup Apache defaultly to "Include conf.d/*" so
you can "drop in" configs like this without having to muck with
the original/main httpd.conf.
I compiled my from source and it doesn't appear to do this. However, I
see that
On Fri, 30 Dec 2005 11:40:54 -0800
Curtis Poe <[EMAIL PROTECTED]> wrote:
> On Dec 30, 2005, at 10:39 AM, Frank Wiles wrote:
> > Many distros now setup Apache defaultly to "Include conf.d/*" so
> > you can "drop in" configs like this without having to muck with
> > the original/main httpd.con
On Dec 30, 2005, at 12:53 PM, Frank Wiles wrote:
Short of the other suggestion of bundling your own
apache/mod_perl/etc
I don't think you're going to be able to able to easily get around
having the user do almost nothing. I don't think many users would
be confused by adding one line of
Hi all,
However, what I need to be able to do is let someone
have a running mod_perl 2 setup and dynamically "pull in" the above
information from an external file or add that information via Perl (in
other words, I don't want to touch the default httpd.conf file). How
the heck do I do that?
Sin
> "Curtis" == Curtis Poe <[EMAIL PROTECTED]> writes:
Curtis> Hi all,
Curtis> I've been searching like mad through the docs for how to do something
Curtis> that I know must be really simple. Let's say that I've added
Curtis> something like that to httpd.conf:
Curtis>PerlModule Some::Appli
On Fri, 30 Dec 2005 13:07:53 -0800
David Wheeler <[EMAIL PROTECTED]> wrote:
> Does that make things clearer? Is there an equivalent to
> $Apache::ReadConfig::PerlConfig in mod_perl2, perhaps? Or better
> yet, is there now an API for dynamically configuring Apache from
> mod_perl2?
Much. I wa
On Fri, 2005-12-30 at 11:30 -0800, Curtis Poe wrote:
> We're hoping to avoid bundling Apache2 because that would contradict
> the design goal. Specifically, if someone has an existing mod_perl 1,
> mod_perl 2, FastCGI or other server, we'd like things to, as much as
> possible, "play nicely" wi
14 matches
Mail list logo
