GSP
Quick Navigator

Search Site

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

Support
Contact Us
Online Help
Handbooks
Domain Status
Man Pages

FAQ
Virtual Servers
Pricing
Billing
Technical

Network
Facilities
Connectivity
Topology Map

Miscellaneous
Server Agreement
Year 2038
Credits
 

USA Flag

 

 

Man Pages


Manual Reference Pages  -  DANCER::PLUGIN (3)

.ds Aq ’

NAME

Dancer::Plugin - helper for writing Dancer plugins

CONTENTS

VERSION

version 1.3138

SYNOPSIS



  package Dancer::Plugin::LinkBlocker;
  use Dancer :syntax;
  use Dancer::Plugin;

  register block_links_from => sub {
    my $conf = plugin_setting();
    my $re = join (|, @{$conf->{hosts}});
    before sub {
        if (request->referer && request->referer =~ /$re/) {
            status 403 || $conf->{http_code};
        }
    };
  };

  register_plugin;
  1;



And in your application:



    package My::Webapp;
   
    use Dancer :syntax;
    use Dancer::Plugin::LinkBlocker;

    block_links_from; # this is exported by the plugin



DESCRIPTION

Create plugins for Dancer

PLUGINS

You can extend Dancer by writing your own Plugin.

A plugin is a module that exports a bunch of symbols to the current namespace (the caller will see all the symbols defined via register).

Note that you have to use the plugin wherever you want to use its symbols. For instance, if you have Webapp::App1 and Webapp::App2, both loaded from your main application, they both need to use FooPlugin if they want to use the symbols exported by FooPlugin.

    METHODS

<B>registerB> Lets you define a keyword that will be exported by the plugin.



    register my_symbol_to_export => sub {
        # ... some code
    };



<B>register_pluginB> A Dancer plugin must end with this statement. This lets the plugin register all the symbols define with register as exported symbols (via the Exporter module).

A Dancer plugin inherits from Dancer::Plugin and Exporter transparently.

<B>register_hookB> Allows a plugin to declare a list of supported hooks. Any hook declared like so can be executed by the plugin with execute_hooks.



    register_hook foo;
    register_hook foo, bar, baz;



<B>execute_hooksB> Allows a plugin to execute the hooks attached at the given position



    execute_hooks some_hook;



The hook must have been registered by the plugin first, with register_hook.

<B>plugin_settingB> Configuration for plugin should be structured like this in the config.yml of the application:



  plugins:
    plugin_name:
      key: value



If plugin_setting is called inside a plugin, the appropriate configuration will be returned. The plugin_name should be the name of the package, or, if the plugin name is under the <B>Dancer::Plugin::B> namespace (which is recommended), the remaining part of the plugin name.

Enclose the remaining part in quotes if it contains ::, e.g. for <B>Dancer::Plugin::Foo::BarB>, use:



  plugins:
    "Foo::Bar":
      key: value



<B>plugin_argsB> To easy migration and interoperability between Dancer 1 and Dancer 2 you can use this method to obtain the arguments or parameters passed to a plugin-defined keyword. Although not relevant for Dancer 1 only, or Dancer 2 only, plugins, it is useful for universal plugins.



  register foo => sub {
     my ($self, @args) = plugin_args(@_);
     ...
  }



Note that Dancer 1 will return undef as the object reference.

AUTHORS

This module has been written by Alexis Sukrieh and others.

LICENSE

This module is free software and is published under the same terms as Perl itself.

AUTHOR

Dancer Core Developers

COPYRIGHT AND LICENSE

This software is copyright (c) 2010 by Alexis Sukrieh.

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

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


perl v5.20.3 DANCER::PLUGIN (3) 2015-06-12

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