- SEE ALSO
- AUTHOR EMERITUS
Maypole::Config - Maypole Configuration Class
This class stores all configuration data for your Maypole application.
This should be a string containing your application's name.
Optional. Is used in the factory templates.
This is the number of rows your application should display per page.
Contains a list of all tables, if supported by model.
This is where your application can find its templates.
This is the URI base that should be prepended to your application when Maypole makes URLs.
The name of the view class for your Maypole Application. Defaults to "Maypole::View::TT".
A hash of configuration options for the view class. Consult the documentation for your chosen view class for information on available configuration options.
This config variable contains a list of your view classes. This is set up by the model class, and should not be changed in the view or the config.
This is a list of the tables that are public to your Maypole application. Defaults to all the tables in the database.
The DSN to your database. Follows standard DBD syntax.
This is the loader object (n.b. an instance, not a class name). It's set up by the CDBI model to an instance of "Class::DBI::Loader" if it's not initialized before calling setup().
The name of the model class for your Maypole Application. Defaults to "Maypole::Model::CDBI".
This is a hash of the public tables. It is populated automatically by Maypole from the list in display_tables and should not be changed.
Password for database user.
Other options to the DBI connect call.
Username to log into the database with.
If your modules need to store additional configuration data for their own use or to make available to templates, add a line like this to your module:
Maypole::Config->mk_accessors(qw(variable or variables));
Care is needed to avoid conflicting variable names.
You may distribute this code under the same terms as Perl itself.