Torsten Förtsch wrote:
On Sunday, May 29, 2011 19:40:59 cfaust-dougot wrote:
I wanted to know if there was anything wrong with using the same MP2
content handler with multiple Location directives in apache and using
$r->location() to determine the script that should be used in forms,
redirects e
On Sunday, May 29, 2011 19:40:59 cfaust-dougot wrote:
> I wanted to know if there was anything wrong with using the same MP2
> content handler with multiple Location directives in apache and using
> $r->location() to determine the script that should be used in forms,
> redirects etc.
Nothing wrong
Folks,
I wanted to know if there was anything wrong with using the same MP2 content
handler with multiple Location directives in apache and using $r->location() to
determine the script that should be used in forms, redirects etc.
We have someone that insists in having different URL's doing so
Perrin Harkins wrote:
You can also run separate mod_perl backends
I usually like this approach since it gives you a lot of control and let's you
manipulate (start, stop, etc) one instance without having to affect others. It
also gives you more scaling options as you can in the future easily
Hi,
> we're looking for a way to offer version handling to our serverside perl
> app.
You'll find many discussions of this in the mailing archive with
multiple options.
> My first ideas goes as:
>
>
> PerlSwitches -I /some/path/v2.0.0/
> PerlResponseHandler run
>
>
>
> Pe
Hello,
Apache is my weak hand so hope to clear some fog with your help.
we're looking for a way to offer version handling to our serverside
perl app.
Each database is tagged to a certain version of the application and
they should be upgraded individually to interfere as little as
possible w
David Arnold wrote:
All,
Is this OK?
# File: startup.pl
use lib qw(/home/darnold/modperl/);
use lib qw(/usr/local/apache/module/);
Sure but if you "use lib" twice all you need are single quotes instead
of qw():
use lib '/home/blah/';
use lib '/usr/local/';
1;
but even better:
use lib qw(/home/bl
Yes.
David Arnold wrote:
All,
Is this OK?
# File: startup.pl
use lib qw(/home/darnold/modperl/);
use lib qw(/usr/local/apache/module/);
1;
Where I've mkdir the module directory in /usr/local/apache.
Can't test at the moment until I figure out my last question.
Thanks.
Reclaim Your Inbox!
http://ww
All,
Is this OK?
# File: startup.pl
use lib qw(/home/darnold/modperl/);
use lib qw(/usr/local/apache/module/);
1;
Where I've mkdir the module directory in /usr/local/apache.
Can't test at the moment until I figure out my last question.
Thanks.
--
Report problems: http://perl.apache.org/bugs
D]
> Sent: Wednesday, February 04, 2004 10:15 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Handlers/locations
>
>
> I had the same issue when I installd modperl.
>
> My solution was to put everything Perlish in the "root",
> with plain HTML stylesh
I had the same issue when I installd modperl.
My solution was to put everything Perlish in the "root", with plain HTML
stylesheets and images under it. So it looked like this:
/htdocs/myapp <-- executable Perl
/htdocs/myapp/img <-- not executable
/htdocs/myapp/css <-- not executable
htdocs/my
> The best solution for me is to have all perl and html files in the root
> directory, and have the images under the /images/ subdirectory, and
> maybe the stylesheets in the /style/ subdirectory.
>
> What would be the best httpd.conf configuration to do that?
>
none of this is really a mod_per
Hi ppl,
I have setup Apache2/mod_perl and started writing perl scripts to
generate html code.
I have a /wood/ directory with two subdirs : /perl/ and /images/
Actually I have setup httpd.conf this way :
SetHandler perl-script
PerlResponseHandler ModPerl::Registry
PerlOptions +Parse
13 matches
Mail list logo
