Well, now I'll try to explain why I have asked such question. I
have
startup.pl with connect_on_init dunction.
Also, I want to use Apache::AuthDBI. And I want options for
Apache::DBI->connect(...) to be stored into httpd.conf
or another but the only place.
I think that I could declare vars into httpd.conf and then use
it in
startup.pl and Apache::AuthDBI.
Storing connection options such as login and password into
environment vars - not very good idea, I thik :)
Personally, I use ENV to set 'production#', 'dev#' id for the machines
the SQL passwords are hardcoded into the app, along with other
traditionally environment variables , in a perl config and are
accessed via something like this:
$server{ $EVN{server_id} }{ $varname }
while there are some disadvantages to this...
i have 1 line in my httpd.conf that includes a httpd.conf for my
modperl app, which I keep in svn along with the app
i only set 1 var in httpd.conf, and don't use that powerful (yet
bastardized integration of 2 things) mod_perl interface to httpd.conf
- its all in the app
and everything is in svn. in a single directory. clustering is as
easy as 'svn co' , oooh!
