1. Introduction
    1. About Agavi
    2. MVC in Agavi
    3. Overview of Agavi
    4. Overview of Application Execution Flow
    5. A Word About Actions
    6. Application filesystem layout
    7. Overview of application configuration
  2. Setting Up The Initial Application
    1. Installing Agavi
    2. Creating an Agavi Project
    3. Finishing The Setup
    4. Finishing The Basic Setup
    5. Installing a New Copy of Your Application
  3. Adding First Code
    1. Creating A New module
    2. Creating A New Action
    3. Tying Things Together — An Introduction To Routing
    4. Fixing The Bloggie Routing
    5. Accessing Request Parameters and Validation Basics
    6. Handling Validation Errors
  4. Putting The M in MVC
    1. Creating A New Model
    2. Adapting The Actions and Views
    3. Custom Validators
  5. Polishing It Up
    1. Layers and Layouts
    2. Applying Our Layout
    3. What Are Slots?
    4. Adding The Post's Title To The URL
    5. Routing Callbacks
    6. Using Callbacks for the Title in URLs
  6. Connecting to a database
    1. The Database Manager
  7. Handling Output Variants
    1. Output Types
    2. Exception Templates
    3. Generating an RSS Feed
  8. Form Processing
    1. Adding a Post
    2. Editing a Post
    3. The Form Population Filter (FPF)
  9. Creating a User Authentication System
  10. Adding To The Master Template

Finishing The Basic Setup

Now would be a good time to perform some setup tasks that might seem a bit unnecessary at the moment but will save you a lot of time and hassle further down the road.

Getting Away From Pear

While using the pear install is just perfect for the basic project setup and first steps, it is recommended to move away from using the pear install and bundle the agavi lib for further development. This enables your fellow developers to check out your application without having a full agavi install and gives you full control over which agavi version you need for your application. This will come in handy the moment someone upgrades the installed agavi version on the server or you need to install two applications on the same server that require different agavi versions.

The first step is to bundle agavi with your application by placing a copy in libs/agavi. You can either have a full export there, use a tarball or just have an external point to the appropriate revision in the agavi svn repository.

Then create a copy of the agavi bin directory in dev/bin. Again you can use an export or use an external, but best use the same method as you used to bundle agavi to ensure consistency. Whatever method you choose, make sure you only check in a template of the agavi build script as the path setup must be done manually in some cases.

For the tutorial we'll be using the 1.0.0 release tarball. Just download it from www.agavi.org/download and extract it. Copy the contents of the src directory to bloggie/libs/agavi. Copy the contents of the bin directory to bloggie/dev/bin. Copy all the licence files to bloggie/. Add all those files to version control. Now copy the agavi build script in dev/bin to it's real name. On windows copy agavi.bat-dist to agavi.bat, on linux and other unix derivates copy agavi-dist to agavi. Adapt the path to the agavi directory in the script and make it executable if nessesary. Add the script to your VCS ignore list. We'll be using the bundled version from now on.

Tip: While you can bundle agavi as a svn:external as lot's of people do, we recommend that you use a full export at least for deployment. While we do our very best to ensure constant availability, it would be a pity to have your application deployment interrupted because our sysadmins choose to reboot the subversion server, taking it offline just in the right moment to have you in big trouble.
Remember: When bundling agavi with your application you have to take care to obey it's license. The license is LGPL, so using and bundling is just perfectly fine, even in closed source applications - you just need to bundle the licence file somewhere.