Hi all,
I've been gearing up for mod_perl'ing a few of our sites. We run several virtual
hosts concurrently, and I am in a bind with include paths.... I know this story sounds
familiar, as i have witnessed similar discussion on this list before.
Except that I'm not running Apache::Template.
I'm actually running my code as a subclass of CGI::Application, and running the whole
thing under Apache::Registry. Each site actually has two sets of include paths,
depending on if the user is accessing the user portion of the site or the
administrative portion of the site.
I am not particularly intersted in binding my application tightly to Apache (yet).
This is why Apache::Registry and Apache::DBI are my friends - giving me speed
increases without my need to change any code. Similarly, I'd love to be able to do
something like this for each virtual host:
PerlModule Apache::DBI
PerlModule Apache::Registry_plus_Template
<FilesMatch "\.cgi$">
SetHandler perl-script
PerlHandler Apache::Registry_plus_Template
Options ExecCGI
PerlSendHeader On
</FilesMatch>
<Location /admin >
TT2IncludePath /usr/local/tt2/templates
TT2IncludePath /home/abw/tt2/lib
</Location>
<Location / >
TT2IncludePath /usr/local/tt2/templates
TT2IncludePath /home/abw/tt2/lib
</Location>
so that my code still does not know what's going on as far as being run by apache.
Thoughts? Past experience?
thanks,
Stephen
_______________________________________________
templates mailing list
[EMAIL PROTECTED]
http://lists.ourshack.com/mailman/listinfo/templates
