Re: multiple developers on one Sever

[prev] [thread] [next] [Date index for 2004/12/22]

Arun pandey schrieb:

>I guess the problem might be with your PerlHandler, coz Apache::Registry,
>caches all scripts, as a result certain global values will remain
>persistent. In such a case you might want to use Apache::PerlRun instead ,
>which  mimics mod_cgi  by flushing the namespace at the every start of
>request.
>
>
>  
>
I understand this - but I want to use Apache::Registry for 
performance-reasons. How can I get different configurations in different 
Versions of my system?
Should I use something like Config::Tiny?
Or can I use Apache::PerlRun just for my config.pl - which I include via
require 'config.pl';
?

Henning


>Thanks
>Arun
>
>
>
>
>
>
>----- Original Message ----- 
>From: "Henning Meyer" <Henning_Meyer@xxx.xxx>
>To: <modperl@xxxx.xxxxxx.xxx>
>Sent: Monday, December 20, 2004 11:10 PM
>Subject: multiple developers on one Sever
>
>
>  
>
>>Hello,
>>I've got a mod_perl-Apache running, which hosts multiple
>>developement-versions (of multiple CVS-developers) of a webapp.
>>Therefore I've got this apache-config:
>><Location ~ /dev/project.*/web>
>>    Options +Includes
>>    XBitHack on
>></Location>
>><Location ~ /dev/project.*/web/+cgi-bin>
>>    SetHandler perl-script
>>    PerlHandler Apache::Registry
>>    PerlModule Apache::DBI
>>    PerlSendHeader On
>>    Options ExecCGI +Includes
>>    Order allow,deny
>>    Allow from all
>>    AllowOverride None
>></Location>
>>
>>Each version has its own config (like a seperate DB per developer). This
>>    
>>
>is
>  
>
>>done by:
>>require 'config.pl';
>>in each of the mod_perl-scripts.
>>config.pl looks like this:
>>
>>#!/usr/bin/perl
>>use strict;
>>package myconf;
>>use vars qw(%c);
>>%c = (DB=>"henningsDB"}; # or tutmannsDB in tutmanns config.pl
>>1;
>>
>>The point is, that in each version everything may be the same except of
>>    
>>
>the
>  
>
>>config.pl.
>>But: Apache and mod_perl seem to mix up the configurations. The reason
>>    
>>
>seems
>  
>
>>to be, that the configuration is just read once the process starts, and
>>    
>>
>not
>  
>
>>each time a script is executed.
>>What is a good workaround? Local ini-Files? Or something even better?
>>
>>Thanks
>>
>>Henning
>>
>>
>>-- 
>>+++ Sparen Sie mit GMX DSL +++ http://www.gmx.net/de/go/dsl
>>AKTION für Wechsler: DSL-Tarife ab 3,99 EUR/Monat + Startguthaben
>>
>>-- 
>>Report problems: http://perl.apache.org/bugs/
>>Mail list info: http://perl.apache.org/maillist/modperl.html
>>List etiquette: http://perl.apache.org/maillist/email-etiquette.html
>>
>>    
>>
>
>
>  
>


        -- 
        Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html