Switching Painlessly from IIS to Apache?
Sheik Yerboutii asks: "The recent downtime caused by the Code Red and NIMDA worms
has prompted my Manager to start considering moving away
from IIS to Apache. I've been tasked with finding out just how difficult it will be to move to the new webserver. I've got to find out things like how to install and configure it (relatively easy, it's all documented at www.apache.org) but also, things like what do we de now that we've been working in VBScript ASP for about 6 moths?" We posted a similar question to this one,
just over a year ago. Any changes or additions to the advice given in that discussion?
"I've read that Apache::ASP exists and that's got something to
do with mod_perl but now I'm going in circles figuring out how to make this thing work. I also can't find straight answers on things like if we make the cut over, will we have to convert the VBScript ASP to Perl ASP?
Can anyone relay their experiences with cutting from IIS to Apache? Running ASP with Apache? Most importantly, what are the best resources available for Apache administrators? (hopefully something with a discussion forum)"
The Apache::ASP will, AFAIK, only work with PERL ASP code. ChiliSoft will do VBScript ASP code.
i.e. you either use ChiliSoft or do a rewrite of your code base.
The ActiveScripting people have some good options under Windows that might be helpful if you want to maximize code reuse.
Gentoo Sucks
No, I don't work for them, but the $500 I spent was well worth it. If you want to see it in action, e-mail me privately and I'll give you a login to poke around.
The non-profit that I work for can't afford to add a bearded Unix guy to the payroll. The IT staff is me and couple people who mainly know Windows and a little Netware.
.conf files doesn't excite them.
The rest of the group would rather just keep patching IIS every couple weeks, because the setup is trivial point and click. Twiddling with
Suggestions?