X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits%2FCatalyst-Manual.git;a=blobdiff_plain;f=lib%2FCatalyst%2FManual%2FDeployment%2FIIS%2FFastCGI.pod;h=4c1140a40af8437fb46c729d8524727f7262b1d1;hp=ecf4c413f01083c363ddd366d58185c0861727e7;hb=689b0b148a6d4e4c6257618f412460d925c11659;hpb=506ff3c852f1f03006cef0a5f23166e6fd4b6ded diff --git a/lib/Catalyst/Manual/Deployment/IIS/FastCGI.pod b/lib/Catalyst/Manual/Deployment/IIS/FastCGI.pod index ecf4c41..4c1140a 100644 --- a/lib/Catalyst/Manual/Deployment/IIS/FastCGI.pod +++ b/lib/Catalyst/Manual/Deployment/IIS/FastCGI.pod @@ -4,13 +4,13 @@ Catalyst::Manual::Deployment::IIS::FastCGI - Deploying Catalyst with Microsoft I =head1 Microsoft IIS -It is possible to run Catalyst under IIS with FastCGI, but only on IIS 6.0 -(Microsoft Windows 2003), IIS 7.0 (Microsoft Windows 2008 and Vista) and -hopefully its successors. +It is possible to run Catalyst under IIS with FastCGI, but only on IIS +6.0 (Microsoft Windows 2003), IIS 7.0 (Microsoft Windows 2008 and +Vista), and (hopefully) its successors. -Even if it is declared that FastCGI is supported on IIS 5.1 (Windows XP) it -does not support some features (specifically: wildcard mappings) that prevents -running Catalyst application. +FastCGI is sometimes said to be supported on IIS 5.1 (Windows XP), but +some features (specifically, wildcard mappings) are not supported. This +prevents Catalyst applications from running on the server. Let us assume that our server has the following layout: @@ -24,10 +24,11 @@ Let us assume that our server has the following layout: =item Install FastCGI extension for IIS 6.0 -FastCGI is not a standard part of IIS 6 - you have to install it separately. For -more info and download go to L. Choose -approptiate version (32-bit/64-bit), installation is quite simple -(in fact no questions, no options). +FastCGI is not a standard part of IIS 6 - you have to install it +separately. For more info and the download, go to +L. Choose the appropriate version +(32-bit/64-bit); installation is quite simple (in fact no questions, no +options). =item Create a new website @@ -37,17 +38,17 @@ you need to go to the new website's properties. =item Set website properties -On tab "Web site" set proper values for: -Site Description, IP Address, TCP Port, SSL Port etc. +On the tab "Web site", set proper values for: Site Description, IP +Address, TCP Port, SSL Port, etc. -On tab "Home Directory" set the following: +On the tab "Home Directory" set the following: Local path: "d:\WWW\WebApp\root" Local path permission flags: check only "Read" + "Log visits" Execute permitions: "Scripts only" Click "Configuration" button (still on Home Directory tab) then click "Insert" -the wildcard application mapping and in the next dialog set: +the wildcard application mapping, and in the next dialog set: Executable: "c:\windows\system32\inetsrv\fcgiext.dll" Uncheck: "Verify that file exists" @@ -95,10 +96,11 @@ install any addons. =item Necessary steps during IIS7 installation -During IIS7 installation after you have added role "Web Server (IIS)" you need -to check to install role feature "CGI" (do not be nervous that it is not -FastCGI). If you already have IIS7 installed you can add "CGI" role feature -through "Control panel" > "Programs and Features". +During IIS7 installation, after you have added role "Web Server (IIS)" +you need to check to install the role feature "CGI" (do not be nervous +that it is not FastCGI). If you already have IIS7 installed you can add +the "CGI" role feature through "Control panel" > "Programs and +Features". =item Create a new website @@ -124,13 +126,19 @@ You can configure FastCGI extension using commandline utility appcmd.exe set config "CatalystSite" -section:system.webServer/handlers /+"[name='CatalystFastCGI',path='*',verb='GET,HEAD,POST',modules='FastCgiModule',scriptProcessor='d:\strawberry\perl\bin\perl.exe|d:\www\WebApp\script\webapp_fastcgi.pl -e',resourceType='Unspecified',requireAccess='Script']" /commit:apphost -Note: before launching the commands above do not forget to change site -name and paths to values relevant for your server setup. +Note: before launching the commands above, do not forget to change the +site name and paths to values relevant for your server setup. =back =back +=head3 Setup of your application + +Note that you B have the config setting C set to true +to work in IIS7 - if you do not have this then all sub paths in your application +(e.g. /foo/bar) will resolve to the root path, i.e. / + =head1 AUTHORS Catalyst Contributors, see Catalyst.pm