> or else extend Strawberry Perl into Raspberry > Perl that is Strawberry for IIS or something along those lines. yummy :-)
At the bottom of I'd like to make a slightly different proposition, but first please help to understand something. Why don't more people ask for a good solution to run perl websites on windowz? The emphasis of this sentence is on "good solution", not on "Perl" or on "Windows". Take this as immutuable requirements. Seriously I don't understand that point. Because from what I can seen you only had ONE stack that really helps you doing this. IIS / Strawberry Perl / FCGI -- Why IIS and not Apache? Because if you work for a real Windows shop you know that this question is simply non-existent .... -- Why Strawberry and not Activestate (installs a quite usable isapi extension for perl) CPAN -- Why FCGI and not CGI or mod_perl AFAIK mod_perl doesn't exist for IIS and CGI is not an option for running web apps. You see, seems like there is really just one solution! I simply cannot believe, that I'm the only one that want to run a perl web app on windows. Proposition for a FCGI/Perl INSTALLER (fcgiperl.msi) ========================================= 1. Checks if the FastCGI package from Microsoft is installed, if not it automatically installed it. 2. Register "Perl" in FastCGI configuration 3. Setup the extension configuration (.pl -> c:\strawberry\bin\perl.exe) on the vhost (website) What do you think? Or are there other good solutions besides fcgi? thanks. 2009/1/23 David Golden <xda...@gmail.com>: > On Fri, Jan 23, 2009 at 3:58 AM, Ben Jakb <ben.j...@gmail.com> wrote: >> >> I'm wondering why it seems like nobody cares how to setup Strawberry >> Perl with fcgi on iis. As far as I know the necessery hooks and >> configurations aren't done automatically when run the Strawberry Perl >> installer. I think this is a plus when you go with Activestate Perl >> because you have cgi and isapi configured automatically. > > I'm not sure I follow what you mean by "hooks and configurations" -- but I > admit I know squat about IIS. If you can explain the necessary changes and > if they don't conflict with other user needs, then it should be feasibly to > include them in the future, or else extend Strawberry Perl into Raspberry > Perl that is Strawberry for IIS or something along those lines. > > -- David >
