Quick Navigator

Search Site

Unix VPS
A - Starter
B - Basic
C - Preferred
D - Commercial
MPS - Dedicated
Previous VPSs
* Sign Up! *

Contact Us
Online Help
Domain Status
Man Pages

Virtual Servers

Topology Map

Server Agreement
Year 2038

USA Flag



Man Pages
CatalystX::AppBuilder(3) User Contributed Perl Documentation CatalystX::AppBuilder(3)

CatalystX::AppBuilder - Build Your Application Instance Programatically

    # In
    my $builder = CatalystX::AppBuilder->new(
        appname => 'MyApp',
        plugins => [ ... ],

WARNING: YMMV regarding this module.

This module gives you a programatic interface to configuring Catalyst applications.

The main motivation to write this module is: to write reusable Catalyst appllications. For instance, if you build your MyApp::Base and you wanted to create a new application afterwards that is mostly like MyApp::Base, but slightly tweaked. Perhaps you want to add or remove a plugin or two. Perhaps you want to tweak just a single parameter.

Traditionally, your option then was to use and create another scaffold, and copy/paste the necessary bits, and tweak what you need.

After testing several approaches, it proved that the current Catalyst architecture (which is Moose based, but does not allow us to use Moose-ish initialization, since the Catalyst app instance does not materialize until dispatch time) did not allow the type of inheritance behavior we wanted, so we decided to create a builder module around Catalyst to overcome this. Therefore, if/when these obstacles (to us) are gone, this module may simply dissappear from CPAN. You've been warned.

This module is NOT a "just-execute-this-command-and-you-get-catalyst-running" module. For the simple applications, please just follow what the Catalyst manual gives you.

However, if you really wanted to, you can define a simple Catalyst app like so:

    # in
    use strict;
    use CatalystX::AppBuilder;
    my $builder = CatalystX::AppBuilder->new(
        debug  => 1, # if you want
        appname => "MyApp",
        plugins => [ qw(
            # and others...
        ) ],
        config  => { ... }


The originally intended approach to using this module is to create a subclass of CatalystX::AppBuilder and configure it to your own needs, and then keep reusing it.

To build your own MyApp::Builder, you just need to subclass it:

    package MyApp::Builder;
    use Moose;

    extends 'CatalystX::AppBuilder';

Then you will be able to give it defaults to the various configuration parameters:

    override _build_config => sub {
        my $config = super(); # Get what CatalystX::AppBuilder gives you
        $config->{ SomeComponent } = { ... };
        return $config;

    override _build_plugins => sub {
        my $plugins = super(); # Get what CatalystX::AppBuilder gives you

        push @$plugins, qw(

        return $plugins;

Then you can simply do this instead of giving parameters to CatalystX::AppBuilder every time:

    # in
    use MyApp::Builder;

Once you created your own MyApp::Builder, you can keep inheriting it to create custom Builders which in turn create more custom Catalyst applications:

    package MyAnotherApp::Builder;
    use Moose;

    extends 'MyApp::Builder';

    override _build_superclasses => sub {
        return [ 'MyApp' ]

    ... do your tweaking ...

    # in
    use MyAnotherApp::Builder;


Voila, you just reused every inch of Catalyst app that you created via inheritance!

Components like Catalyst::View::TT, which in turn uses Template Toolkit inside, allows you to include multiple directories to look for the template files.

This can be used to recycle the templates that you used in a base application.

CatalystX::AppBuilder gives you a couple of tools to easily include paths that are associated with all of the Catalyst applications that are inherited. For example, if you have MyApp::Base and MyApp::Extended, and MyApp::Extended is built using MyApp::Extended::Builder, you can do something like this:

    package MyApp::Extended::Builder;
    use Moose;

    extends 'CatalystX::AppBuilder'; 

    override _build_superclasses => sub {
        return [ 'MyApp::Base' ]

    override _build_config => sub {
        my $self = shift;
        my $config = super();

        $config->{'View::TT'}->{INCLUDE_PATH} = 
            [ $self->inherited_path_to('root') ];
        # Above is equivalent to 
        #    [ MyApp::Extended->path_to('root'), MyApp::Base->path_to('root') ]

So now you can refer to some template, and it will first look under the first app, then the base app, thus allowing you to reuse the templates.

The module name of the Catalyst application. Required.

The metaclass object of the Catalyst application. Users cannot set this.

Boolean flag to enable debug output in the application

The version string to use (probably meaningless...)

The list of superclasses of the Catalyst application.

The config hash to give to the Catalyst application.

The list of plugins to give to the Catalyst application.

Bootstraps the Catalyst app.

Calls path_to() on all Catalyst applications in the inheritance tree.

Calls path_to() on the curent Catalyst application.

Documentation. Samples. Tests.

Daisuke Maki "<>"

This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.


2016-02-26 perl v5.32.1

Search for    or go to Top of page |  Section 3 |  Main Index

Powered by GSP Visit the GSP FreeBSD Man Page Interface.
Output converted with ManDoc.