view release on metacpan or  search on metacpan

lib/Bigtop/Docs/TentRef.pod  view on Meta::CPAN

Defaults to the Perl 5.8.6 license text generated by h2xs.  Use this
to be meaner.  Some might even make it 'All rights reserved.'

=item Modules Used

These will be used in the base module for the app (but remember that they
will be ignored after your initial bigtop build).

=back

=head1 App Config

This is where you configure your app.  Here is the table you need to fill
with your info:

=for html <img src='http://www.usegantry.org/images/tenttut/appconfig.png' alt='App Config' />

    http://www.usegantry.org/images/tenttut/appconfig.png

There is a row for each config parameter.  Each row has four columns:

=over 4

=item Keyword

The name of the parameter.

=item Value

The value to use for it.

=item Skip Accessor?

If your framework already knows about the keyword, it probably provides
a built-in accessor for it.  For instance, Gantry already provides accessors
for dbconn, dbuser, dbpass, root, template_wrapper, and several others.
If your frameword provides the accessor, you should check the 'Skip Accessor?'
box, so bigtop does not make a duplicate accessor for the keyword in your
app's base module.

=item Delete Buttons

If you don't need one of the config params, simple click this button to
remove it.

=back

Under the current config parameters is a 'New Config Statement' button
and an input box to type the name of a new parameter.  For instance, you
might want to add dbpass for the database password which corresponds
to your dbuser.

This concludes our exhaustive tour of tentmaker.  I hope you are more
excited than exhausted.

'Consult Building and Starting' in C<Bigtop::Docs::TentTut> for instructions
on how to build your app once you have saved the above.

=head1 Further Reading

See C<Bigtop::Docs::Cookbook> for small problems and answers,
C<Bigtop::Docs::Tutorial> for a more complete example, with discussion,
C<Bigtop::Docs::AutoKeywords> for a list of valid keywords and their meanings,
and C<Bigtop::Docs::Sytnax> for more details.  The above backend information
is repeated in shorter form in C<Bigtop::Docs::AutoBackends>, but that
document is more up to date.  If you need to write your
own backends, see C<Bigtop::Docs::Modules>.

All of the doc modules are described briefly in C<Bigtop::Docs::TOC>.

=head1 Author

Phil Crow

=cut