Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

dancer::plugins(3pm) [debian man page]

Dancer::Plugins(3pm)					User Contributed Perl Documentation				      Dancer::Plugins(3pm)

Dancer::Plugins - interesting plugins to add to Dancer's capabilities DESCRIPTION
Dancer aims to keep the core as small as possible, but there are a growing number of useful plugins to add helpful features. This document provides a quick summary of some recommended plugins. PLUGINS
Dancer::Plugin::Database Provides easy database access via DBI, reading the DB connection details from your app's config file, and taking care of ensuring the connection is still valid and reconnecting if not (useful in persistent environments). Just calling the "database" keyword gives you a connected and working database handle. It also provides some helpful keywords to make inserting/updating data as simple as it should be. Dancer::Plugin::DBIC Provides easy acces to DBIx::Class database virtualization. Dancer::Plugin::Auth::RBAC Dancer Authentication, Security and Role-Based Access Control Framework. Dancer::Plugin::Email Provides easy email-sending powered by Email::Send - simply call the "email" keyword. Email sending settings can be taken from your app's config. Dancer::Plugin::SMS Send SMS text messages to mobile phones from your Dancer app, using any service supported by SMS::Send. Dancer::Plugin::Ajax Provides easy way to add Ajax route handlers. Dancer::Plugin::REST Makes writing RESTful web services easy. Dancer::Plugin::SiteMap Automatically provides site maps (as a HTML page, or as an XML sitemap ready for Google) based on the routes your app defines. Dancer::Plugin::Validation Easy data validation powered by Oogly. Dancer::Plugin::Params::Normalization Provides different ways of normalizing parameter names Dancer::Plugin::SimpleCRUD Provides easy CRUD (create, read, update, delete) facilities, automatically creating routes to display, add, edit and delete data from a database table. Dancer::Plugin::WebSocket Supports building apps using Web Sockets for bi-directional, full-duplex communications over a long-lived socket connection. Dancer::Plugin::Memcached Cache page responses or individual items of data with memcached for performance. Dancer::Plugin::MobileDevice Quickly determine whether the client is a mobile browser, in order to offer a simplified layout, or otherwise customise features. Dancer::Plugin::NYTProf Provides dead-simple profiling of your app using Devel::NYTProf - enables profiling for each request individually, serves up a list of profiling runs, and generates & sends the HTML reports produced by "nytprofhtml". Dancer::Plugin::Bcrypt Provides simple effective password hashing and validation using Bcrypt. Dancer::Plugin::Cache::CHI Provides caching for generated pages and/or arbitrary data. Uses CHI, so is backend-agnostic - caching can be done in memory, to files, using Memcache, in a database, or any other method for which there is a CHI::Driver module. Dancer::Plugin::Thumbnail Easy thumbnail generation using GD. Dancer::Plugin::Captcha::SecurityImage Easy CAPTCHA image generation and validation, using GD. Dancer::Plugin::Facebook Easily work with Facebook's Graph API from your Perl Dancer app. Uses Facebook::Graph. Dancer::Plugin::Redis Easy Redis database connections, based upon Dancer::Plugin::Database. Dancer::Plugin::XML::RSS Easy XML RSS creation and consumption. More plugins are appearing on CPAN all the time - just search for "Dancer::Plugin" to see what may have been released since this document was last updated! perl v5.14.2 2011-11-30 Dancer::Plugins(3pm)

Check Out this Related Man Page

Dancer::Plugin::DBIC(3pm)				User Contributed Perl Documentation				 Dancer::Plugin::DBIC(3pm)

Dancer::Plugin::DBIC - DBIx::Class interface for Dancer applications VERSION
version 0.1506 SYNOPSIS
use Dancer; use Dancer::Plugin::DBIC 'schema'; get '/users/:id' => sub { my $user = schema->resultset('User')->find(param 'id'); template user_profile => { user => $user }; }; dance; DESCRIPTION
This plugin makes it very easy to create Dancer applications that interface with databases. It automatically exports the keyword "schema" which returns a DBIx::Class::Schema object. You just need to configure your database connection information. For performance, schema objects are cached in memory and are lazy loaded the first time they are accessed. CONFIGURATION
Configuration can be done in your Dancer config file. This is a minimal example. It defines one database named "default": plugins: DBIC: default: dsn: dbi:SQLite:dbname=some.db In this example, there are 2 databases configured named "default" and "foo": plugins: DBIC: default: dsn: dbi:SQLite:dbname=some.db schema_class: My::Schema foo: dsn: dbi:mysql:foo schema_class: Foo::Schema user: bob pass: secret options: RaiseError: 1 PrintError: 1 Each database configured must have a dsn option. The dsn option should be the DBI driver connection string. All other options are optional. If you only have one schema configured, or one of them is named "default", you can call "schema" without an argument to get the only or "default" schema, respectively. If a schema_class option is not provided, then DBIx::Class::Schema::Loader will be used to dynamically load the schema based on the dsn value. This is for convenience only and should not be used in production. See "SCHEMA GENERATION" below for caveats. The schema_class option, should be a proper Perl package name that Dancer::Plugin::DBIC will use as a DBIx::Class::Schema class. Optionally, a database configuation may have user, pass, and options parameters as described in the documentation for "connect()" in DBI. You may also declare your connection information in the following format (which may look more familiar to DBIC users): plugins: DBIC: default: connect_info: - dbi:mysql:foo - bob - secret - RaiseError: 1 PrintError: 1 USAGE
This plugin provides just the keyword "schema" which returns a DBIx::Class::Schema object ready for you to use. If you have configured only one database, then you can call "schema" with no arguments: my $user = schema->resultset('User')->find('bob'); If you have configured multiple databases, you can still call "schema" with no arguments if there is a database named "default" in the configuration. Otherwise, you must provide "schema()" with the name of the database: my $user = schema('foo')->resultset('User')->find('bob'); SCHEMA GENERATION
There are two approaches for generating schema classes. You may generate your own DBIx::Class classes by hand and set the corresponding "schema_class" setting in your configuration as shown above. This is the recommended approach for performance and stability. It is also possible to have schema classes automatically generated via introspection (powered by DBIx::Class::Schema::Loader) if you omit the "schema_class" configuration setting. However, this is highly discouraged for production environments. The "v7" naming scheme will be used for naming the auto generated classes. See "naming" in DBIx::Class::Schema::Loader::Base for more information about naming. For generating your own schema classes, you can use the dbicdump command line tool provided by DBIx::Class::Schema::Loader to help you. For example, if your app were named Foo, then you could run the following from the root of your project directory: dbicdump -o dump_directory=./lib Foo::Schema dbi:SQLite:/path/to/foo.db For that example, your "schema_class" setting would be "Foo::Schema". AUTHORS
o Al Newkirk <> o Naveed Massjouni <> o Alexis Sukrieh <> o Franck Cuny <> o David Precious <> COPYRIGHT AND LICENSE
This software is copyright (c) 2010 by awncorp. This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself. perl v5.14.2 2012-04-13 Dancer::Plugin::DBIC(3pm)
Man Page

Featured Tech Videos