Jaldhar H. Vyas wrote:
On Fri, 16 Jan 2009, Lyle wrote:
Also if you are using IIS you'll want to start your scripts like:-
....
You know what? You should wrap this and any other IIS quirks into a
CGI::Application::Plugin::IIS and upload it to CPAN.
The problem is that you need this code in your instance script as well,
or at least:-
BEGIN {
use FindBin qw ($RealBin $RealScript);
use lib $FindBin::RealBin;
chdir $RealBin;
}#BEGIN
As if your app modules are outside the default perl lib folders (which
they probably are) then your instance wont get to find them in the first
place :/
I myself have a folder with all the cpan deps (including CGI::App) that
I'm bundling along with my app. I start my instance script with:-
BEGIN {
use FindBin qw ($RealBin $RealScript);
use lib $FindBin::RealBin;
use lib "$FindBin::RealBin/cpanlib";
chdir $RealBin;
}#BEGIN
If I made a plugin that did this, then I'd need to have this anyway to
pickup the plugin if you get what I mean??? :-\
I'm moving a very large cgi application over to CGI::App, anything I
find myself doing that I think others will find useful I'm making into a
plugin. Such as I18N, and I've just finished a YAML plugin. Thanks for
your support an encouragement :)
Lyle
##### CGI::Application community mailing list ################
## ##
## To unsubscribe, or change your message delivery options, ##
## visit: http://www.erlbaum.net/mailman/listinfo/cgiapp ##
## ##
## Web archive: http://www.erlbaum.net/pipermail/cgiapp/ ##
## Wiki: http://cgiapp.erlbaum.net/ ##
## ##
################################################################
