X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits%2FCatalyst-Manual.git;a=blobdiff_plain;f=lib%2FCatalyst%2FManual%2FTutorial%2F01_Intro.pod;h=534d1a681478bcdcb073054940f3dc4a9ac2b3d3;hp=b0079eea81b986f837394158dd805b9e960e45d7;hb=8c454636e665ea7326c212ed82376bc7a1e05937;hpb=014065cb1682cef16ac7fa0ca516884e81669e16 diff --git a/lib/Catalyst/Manual/Tutorial/01_Intro.pod b/lib/Catalyst/Manual/Tutorial/01_Intro.pod index b0079ee..534d1a6 100644 --- a/lib/Catalyst/Manual/Tutorial/01_Intro.pod +++ b/lib/Catalyst/Manual/Tutorial/01_Intro.pod @@ -83,16 +83,16 @@ following command (note: will probably be switching to git soon): This will download the most recent code for each chapter of the tutorial into the CatalystTutorial directory on your machine. -B +errors, or accidentally skipped part of the tutorial. B It should make little or no difference to Catalyst's operation, B that you can download and use to work through the full tutorial step by step. B to avoid issues that may crop up if you are working with a different configuration. We @@ -193,15 +193,12 @@ Virtual Machine. This document uses the term "host machine" to refer to the physical machine where you will run the virtualization software and boot up the VM. The terms "guest machine" or just "VM" refer to the virtual machine itself -- the thing where you actually do the tutorial -and that you boot up on the "host machine". +(and that you boot up on the "host machine"). -Also, to reduce download size, the Tutorial VM just includes a minimal -command-line environment. In general, it is expected that people will -boot up the Tutorial VM on their main desktop (the "host machine" using -the terminology above) and then use that main desktop machine to SSH and -web browse into the "guest VM" as they work through the tutorial. If -you wish to install X-Windows (or any other packages), just use the -C (or C) Debian commands. +B Throughout the tutorial, we will shows the UNIX shell prompt as +"C<$>". If you are using the Tutorial VM, the prompt will really be +"C" (where "C<~"> will change to show your +current directory), but we will keep it short and just use "C<$>". =over 4 @@ -211,14 +208,14 @@ C (or C) Debian commands. Download a Tutorial Virtual Machine image from L -B +B +B<(and everything else they do for the Perl community)!> =item 2 -Uncompress the image: +Uncompress the image on the "host machine": - tar zxvf CatalystTutorial.tgz + MAINCOMPUTER:~$ tar zxvf CatalystTutorial.tgz =item 3 @@ -228,13 +225,14 @@ L. =item 4 -Once you get a login prompt, enter the username B and a password -for C. You should now be at a prompt that looks like: +Once you get a login prompt, enter the username B and a +password for C. You should now be at a prompt that looks +like: - catalyst login: root + catalyst login: catalyst Password: catalyst ... - root@catalyst:~# + catalyst@catalyst:~$ =item 5 @@ -252,7 +250,7 @@ The image it design to automatically use a DHCP-assigned address. Try to ping this IP address from your "host machine" (main desktop): - MainComputer:~$ ping 192.168.0.12 + MAINCOMPUTER:~$ ping 192.168.0.12 PING 192.168.0.12 (192.168.0.12) 56(84) bytes of data. 64 bytes from 192.168.0.12: icmp_req=1 ttl=255 time=4.97 ms 64 bytes from 192.168.0.12: icmp_req=2 ttl=255 time=3.43 ms @@ -270,7 +268,7 @@ could be a few network-related issues you might need to sort out. See the section below L for additional information and troubleshooting advice. -L Remember this IP address... you will be using it throughout the +B Remember this IP address... you will be using it throughout the tutorial. @@ -279,13 +277,13 @@ tutorial. B, open an SSH client and connect to the IP address found in the previous step. You should get a login prompt (accept the SSH key if you get a warning message about that). Login -with the same username and password as we used in Step 4: B / +with the same username and password as we used in Step 4: B / B - catalyst login: root + catalyst login: catalyst Password: catalyst ... - root@catalyst:~# + catalyst@catalyst:~$ =item 7 @@ -295,7 +293,7 @@ Chapter 3 included with the Tutorial Virtual Machine and start the Catalyst Development Server: $ cd Final/Chapter03/MyApp - $ perl scripts/myapp_server + $ perl script/myapp_server.pl =item 8 @@ -317,26 +315,86 @@ back and carefully check each of the steps above. =item 9 -B The VI/VIM editor is already installed on the Tutorial -Virtual Machine. In order to reduce the size of the download, Emacs is -not pre-installed. Since people obviously have very strong opinions -about which editor is best, :-) Debian fortunately make it very easy to -install Emacs: +B Also, to reduce download size, the Tutorial VM just +includes a minimal command-line environment. You are free to use +Debian's very capable C package manager to install other packages. +You will first want to pull the apt cache files with C +(or C if you prefer apt-get). + +The VI/VIM editor is already installed on the Tutorial Virtual Machine. +In order to reduce the size of the download, Emacs is not pre-installed. +Since people obviously have very strong opinions about which editor is +best, :-) fortunately it's very easy to install Emacs: + + $ sudo aptitude update + $ sudo aptitude install emacs + +In general, it is expected that people will +boot up the Tutorial VM on their main desktop (the "host machine" using +the terminology above) and then use that main desktop machine to SSH and +web browse into the "guest VM" as they work through the tutorial. If +you wish to install X Windows (or any other packages), just use the +C (or C) Debian commands. + +For example, to install X Windows with Fluxbox (a lightweight +WindowManager -- it is great for things like this tutorial since it's +about 1/10th the size of other common X Windows environments), you can +do: + + $ sudo aptitude update + $ sudo aptitude install xorg fluxbox iceweasel + +And then start X Windows from the B with this command: + + $ startx + +Note that if you want to start Fluxbox from an SSH session, you can use +the C and select "anybody" from the +menu. Otherwise, you will need to be on the actual "VM console" to +start it. + +If you have a preference for the Gnome desktop environment, you can do: + + $ sudo aptitude update + $ sudo aptitude install gnome iceweasel + $ + $ # You can reboot or start with 'startx', we will just reboot here + $ reboot + + $ sudo aptitude install kde iceweasel + +For KDE, just substitute the package name "C" for "C" above. + +Note that C is basically used to install Firefox on Debian +boxes. You can start it under X Windows with either the C +command or the C command (or use the menus). You can get +more information on Iceweasel at L. + +Also, you might need to add more memory to your virtual machine if you +want to run X Windows (or other tools that might require additional +memory). Consult the documentation for you virtualization software +for instructions on how to do this (it's usually pretty simple). - $ aptitude install emacs =back You may note that the Tutorial Virtual Machine uses L so -that the Perl modules are run from ~/perl5 (in this case, /root/perl5) -vs. the usual location of your "system Perl". We recommend that you -also consider using this very handy module. It can greatly ease the -process of maintaining and testing different combinations or Perl -modules across development, staging, and production servers. (The -"relocatable Perl" feature can also be used to to run both the modules -B Perl itself from your home directory [or any other directory you -chose]). +that the Perl modules are run from ~/perl5 (in this case, +/home/catalyst/perl5) vs. the usual location of your "system Perl". We +recommend that you also consider using this very handy module. It can +greatly ease the process of maintaining and testing different +combinations or Perl modules across development, staging, and production +servers. (The "relocatable Perl" feature can also be used to to run +both the modules B Perl itself from your home directory [or any +other directory you chose]). + +B: Please provide feedback on how the Virtual Machine approach for +the tutorial works for you. If you have suggestions or comments, you +can reach the author through the email address at the bottom of this +page or via an RT ticket at +L. + =head2 Sorting Out Virtual Machine Network-Related Issues @@ -380,11 +438,16 @@ other machine (including the "host machine") into the VM. Some virtual machine host environments let you configure a "static NAT" or "port forwarding" to reach the guest OS, but others omit this functionality. +Note: NAT mode can work fine if you install X Windows and do the whole +tutorial locally on the actual VM vs. using SSH and a web browser from +your host machine. + "Local host only" mode let's the guest VM and the host machine talk on a "private subnet" that other devices in your network cannot reach. This can work as long as you don't need to go from the VM to the Internet (for example, to install other Debian packages). + Consult the documentation on your virtual machine host environment for help configuring the options above. Here are some links that might help: @@ -393,15 +456,15 @@ help: =item * -L +L =item * -L +L =item * -L +L =back @@ -478,13 +541,14 @@ C. Note that the development server defaults to port 3000 (you can change with with the "-p" option on the command line. -B Depending on the web browser you are using, you might need -to hit C or C to pull a fresh page when +B Depending on the web browser you are using, you might +need to hit C or C to pull a fresh page when testing your application at various points (see -L for a comprehensive -list of options for each browser). Also, the C<-k> keepalive option to -the development server can be necessary with some browsers (especially -Internet Explorer). +L for a +comprehensive list of options for each browser). + +Also, the C<-k> B to the development server can be +necessary with some browsers (B). =back @@ -510,10 +574,10 @@ L Kennedy Clark, C -Please report any errors, issues or suggestions to the author. The -most recent version of the Catalyst Tutorial can be found at -L. +Feel free to contact the author for any errors or suggestions, but the +best way to report issues is via the CPAN RT Bug system at +L. -Copyright 2006-2010, Kennedy Clark, under the +Copyright 2006-2011, Kennedy Clark, under the Creative Commons Attribution Share-Alike License Version 3.0 (L).