From: Andy Grundman Date: Thu, 23 Mar 2006 02:42:54 +0000 (+0000) Subject: Removed forced engine instructions from tutorial X-Git-Tag: 5.7099_04~665 X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits%2FCatalyst-Runtime.git;a=commitdiff_plain;h=9ecc267238aa4b8b7e09ef834c08f5a7b5351771;hp=4cfbdfdba42801fbce9de80c0e3ff74d6531da3a Removed forced engine instructions from tutorial --- diff --git a/lib/Catalyst/Manual/Tutorial.pod b/lib/Catalyst/Manual/Tutorial.pod index 1d620bf..b05112a 100644 --- a/lib/Catalyst/Manual/Tutorial.pod +++ b/lib/Catalyst/Manual/Tutorial.pod @@ -681,18 +681,11 @@ the new value in the database. Now that we have the basics together, we can try running our application on a "real" server instead of just using the test server that catalyst comes with. L is the module used to implement various types of -servers to run it on. The current popular ones are Apache and FastCGI. To -force the use of a particular engine we can use the -Engine flag to Catalyst: - - use Catalyst qw/-Engine=Apache/; - -or - - use Catalyst qw/-Engine=FastCGI/; +servers to run it on. The current popular ones are Apache and FastCGI. =head3 Apache -Apache also needs to be configured: we need to tell it to load your +Apache needs to be configured: we need to tell it to load your application. You can either use Catalyst for your entire website, or subsections. Use the Location directive to choose a path to run your application under: