X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=lib%2FCatalyst%2FManual%2FInstallation.pod;h=24900cb94b024ad987119514937c4c0fc796415b;hb=b354201608d428db344c63dd35de096a62a7a9d3;hp=9c4edfc0d0aa1365b4539c0ff7ff2498cdfffc20;hpb=da62e2982e9586973f977c6fc76ff2b87dd89927;p=catagits%2FCatalyst-Runtime.git diff --git a/lib/Catalyst/Manual/Installation.pod b/lib/Catalyst/Manual/Installation.pod index 9c4edfc..24900cb 100644 --- a/lib/Catalyst/Manual/Installation.pod +++ b/lib/Catalyst/Manual/Installation.pod @@ -1,4 +1,4 @@ -head1 NAME +=head1 NAME Catalyst::Manual::Installation - Catalyst Installation @@ -8,21 +8,34 @@ How to install Catalyst. =head1 INSTALLATION -On one hand, Catalyst gains immediate power and flexibility -through its use of CPAN (the Comprehensive Perl Archive -Network, an enormous global repository containing over 10,000 -free modules). On the other hand, Catalyst's reliance on CPAN -can complicate initial installations, especially in -shared-hosting environments where you, the user, do not have -easy control over what versions other modules are installed. - -It is worth stressing that the difficulties found in installing -Catalyst are caused not by anything intrinsic to Catalyst -itself, but rather by the interrelated dependencies of a large -number of required modules. - -Fortunately, there are a growing number of methods that can -dramatically ease this undertaking: +One of the frequent problems reported by new users of Catalyst is that +it can be extremely time-consuming and difficult to install. + +One of the great strengths of Perl as a programming language is its use +of CPAN, the Comprehensive Perl Archive Network, an enormous global +repository containing over 10,000 free modules. For almost any basic +task--and a very large number of non-basic ones--there is a module on +CPAN that will help you. Catalyst has taken advantage of this, and uses +a very large number of CPAN modules, rather than reinventing the wheel +over and over again. On the one hand, Catalyst gains power and +flexibility through this re-use of existing code. On the other hand, +Catalyst's reliance on CPAN can complicate initial installations, +especially in shared-hosting environments where you, the user, do not +have easy control over what versions of other modules are installed. + +It is worth stressing that the difficulties found in installing Catalyst +are caused not by anything intrinsic to Catalyst itself, but rather by +the interrelated dependencies of a large number of required modules. + +Fortunately, there are a growing number of methods that can dramatically +ease this undertaking. Note that for many of these, you will probably +need to install additional Catalyst-related modules (especially plugins) +to do the things you want. As of version 5.70, Catalyst has split into +two packages, L, which includes the core elements +necessary to deploy a Catalyst application, and L, +which includes the Helpers and other things necessary or useful for +developing Catalyst applications. In a purely deployment environment +you can omit L. =over 4 @@ -30,23 +43,35 @@ dramatically ease this undertaking: Matt Trout's C script -Available at -L, -C can be a quick and painless way to get Catalyst -up and running. Just download the script from the link above -and type C. This script automates the -process of installing Catalyst itself and its dependencies, -with bits of overriding so that the process does not require -user interaction. +Available at L, +C can be a quick and painless way to get Catalyst up and +running on your system. Just download the script from the link above +and type C. This script automates the process of +installing Catalyst itself and its dependencies, with bits of overriding +so that the process does not require user interaction. C +installs Catalyst and its dependencies using the L module, so that +modules are installed the same way you would probably install them +normally--it just makes it easier. This is a recommended solution for +installation. =item * Chris Laco's CatInABox -Download the tarball from +CatInABox is a complete version of Catalyst that is installed locally on +your system, so that you don't need to go through the effort of doing a +full install. Simply download the tarball from L and unpack it on your machine. Depending on your OS platform, either run C -or C. +or C to set your bin/PERLLIB paths. This tarball contains +everything needed to try out Catalyst including Catalyst itself, +Template Toolkit, several Authentication modules, StackTrace, and a few +other plugins. + +A special Win32 version is available upon request that contains many +more plugins and pre-compiled modules, including DBIx::Class, DBI, +SQLite, and Session support. If you are interested in this version, +please send e-mail to C. =item * @@ -57,6 +82,43 @@ of VMWare images where an entire Catalyst development environment has already been installed, complete with database engines and a full complement of Catalyst plugins. +=item * + +Frank Speiser's Amazon EC2 Catalyst SDK + +There are currently two flavors of publicly available Amazon Machine +Images (AMI) that contain all the dependencies you'd need to get a +Catalyst development environment,with all the trimmings, up and +running within minutes. + +Once you obtain an Amazon Elastic Cloud Computing account available +here: +L, +you can literally get a Catalyst development instance up and running +in less than 5 minutes. + +The current AMIs that are available are here in abbreviated form: + + IMAGE ami-bdbe5ad4 developer-tools/Debian-Etch_Catalyst_DBIC_TT.manifest.xml + IMAGE ami-9fbe5af6 developer-tools/Fedora8-Catalyst_DBIC_TT.manifest.xml + +You can run the instances according to the Amazon documentation, as follows: + + ec2-run-instances -k gsg-keypair + +Refer to the Amazon EC2 documentation from the "Amazon Web Services" +section of the L web site for further +assistance. + +You can currently choose between ready-made SDKs on Fedora8 and Debian +Etch. Both machine images include Catalyst, DBIx::Class, +Template::Toolkit, Moose, the mysql and postgresql databases, as well +as subversion source control. The Debian Etch machine instance also +includes svk and git. + +Just run the installation instructions contained in this manual and +go. + =back =head2 OTHER METHODS @@ -70,10 +132,11 @@ variety of other installation techniques: CPAN -The traditional way to install Catalyst is directly from CPAN using -C bundle: +The traditional way to install Catalyst is directly from CPAN using the +C bundle and C: - $ perl -MCPAN -e 'install Task::Catalyst' + $ perl -MCPAN -e 'install Task::Catalyst' + $ perl -MCPAN -e 'install Catalyst::Devel' Unless you have a particularly complete set of Perl modules already installed, be prepared for a large number of nested dependencies. @@ -92,8 +155,8 @@ C. FreeBSD FreeBSD users can get up and running quickly by typing C, or C if C is installed on your system. +/usr/ports/www/p5-Catalyst-Devel && make install>, or C if C is installed on your system. =item * @@ -101,7 +164,7 @@ Windows ActivePerl Windows users can take advantage of the PPM tool that comes with ActivePerl to jumpstart their Catalyst environment. Directions are -available at L. +available at L. =item * @@ -109,19 +172,17 @@ Subversion Repository Catalyst uses Subversion for version control. To checkout the latest: - $ svn co http://dev.catalyst.perl.org/repos/Catalyst/trunk/Catalyst/ + $ svn co http://dev.catalyst.perl.org/repos/Catalyst/trunk/Catalyst-Runtime/ =back -B Although all of the above methods can be used to -install a base Catalyst system, only the VMWare image is -likely to have all of the plugins and modules you need to use -Catalyst properly, and to complete the tutorial. When you -start the C