Philip Crow > Bigtop-0.38 > Bigtop::Backend::CGI::Gantry

Download:
Bigtop-0.38.tar.gz

Dependencies

Annotate this POD

CPAN RT

New  2
Open  1
View/Report Bugs
Source  

NAME ^

app.server - A generated server for the [% app_name %] app

SYNOPSIS ^

    usage: app.server [options] [port]

port defaults to 8080

DESCRIPTION ^

This is a Gantry::Server based stand alone server for the [% app_name +%] app. It was built to use the [% instance %] Gantry::Conf instance in the docs directory.

To override the database connection information in your conf file, see "Changing Databases without Changing Conf" below.

To change instances or master conf files, use these flags (they all require values):

--instance (or -i)

(Incompatible with --type)

The full name of your conf instance, defaults to [% instance %].

--type (or -t)

(Incompatible with --instance)

Use this if you use named config blocks in your Bigtop file. Use the name of the config block as the value for --type. This will build the corresponding instance name as [% instance %]_TYPE, where TYPE is the value of this flag.

If you don't neither --instance nor --type, the instance you get will be [% instance %].

--file (or -f)

The name of your master Gantry::Conf file, defaults to docs/app.gantry.conf.

Changing Databases without Changing Conf ^

You may use the following flags to control database connections. If you supply these flags, they will take precedence over your Gantry::Conf instance. All of them require values.

--dbd (or -d)

The name of your DBD module (like SQLite, Pg, or mysql). If you use dbname, this defaults to SQLite.

--dbname (or -n)

The name of your database.

--dbuser (or -u)

Your database user name.

--dbpass (or -p)

Your database password.

NAME ^

Bigtop::CGI::Backend::Gantry - CGI dispatch script generator for the Gantry framework

SYNOPSIS ^

If your bigtop file includes:

    config {
        CGI Gantry {
            # optional statements:
                # to get a stand alone server:
                    with_server 1;
                # to use FastCGI instead of regular CGI:
                    fast_cgi 1;
        }
    }

and there are controllers in your app section, this module will generate app.cgi when you type:

    bigtop app.bigtop CGI

or

    bigtop app.bigtop all

You can then directly point your httpd.conf directly to the generated app.cgi.

DESCRIPTION ^

This is a Bigtop backend which generates cgi dispatching scripts for Gantry supported apps.

KEYWORDS ^

This module does not register any keywords. See Bigtop::CGI for a list of allowed keywords (think app and controller level 'location' and controller level 'rel_location' statements).

METHODS ^

To keep podcoverage tests happy.

backend_block_keywords

Tells tentmaker that I understand these config section backend block keywords:

        no_gen
        fast_cgi
        with_server
        server_port
        flex_db
        gantry_conf
        template

        instance
        conffile

Note that instance and conffile are now deprecated in favor of setting gantry_conf to true, which draws the values from the Conf Gantry backend. You may still use them if you like, but that may change in the future.

what_do_you_make

Tells tentmaker what this module makes. Summary: app.server and app.cgi.

gen_CGI

Called by Bigtop::Parser to get me to do my thing.

output_cgi

What I call on the various AST packages to do my thing.

setup_template

Called by Bigtop::Parser so the user can substitute an alternate template for the hard coded one here.

AUTHOR ^

Phil Crow <crow.phil@gmail.com>

COPYRIGHT and LICENSE ^

Copyright (C) 2005 by Phil Crow

This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself, either Perl version 5.8.6 or, at your option, any later version of Perl 5 you may have available.

syntax highlighting: