December 2013 - dancer-users - lists.preshweb.co.uk

Advent Calendar
by Dave Cross 12 Dec '13

12 Dec '13

The advent calendar seems to be stuck on 2nd December - http://advent.perldancer.org/2013. Did you run out of articles already? Or is something not pushing the articles live correctly? Cheers, Dave...

5 6

Using Dancer::Plugin::Auth::Extensible with Dancer::Plugin::REST
by Jacques Lareau 11 Dec '13

11 Dec '13

I already use the Dancer::Plugin::Auth::Extensible (which is very nice, thanks!) to protect my routes. I would like to be able to protect the routes generated with the resources keyword. I tried something like: resource user => get => sub { }, delete => require_role Admin => sub { }, ... Won't work. D:P:Auth::Extensible seems to call the coderef passed to it. I guess I would need the coderef returned? Any hint? Thanks! -- Jacques Lareau

2 2

Re: [dancer-users] Namespace for load_app modules
by Damien Krotkine 09 Dec '13

09 Dec '13

And I'll make the tactical mistake of jumping into this thread after a long day :) and say that I agree with Sawyer and Yanick. I'd like to add this: Let's say you publish Dancer::App::MyGreatApp for other people to use. Some of them will use it as is, like without touching it, but others (most of them ?) will want to tweak it, change some stuff, expand on it, etc. And it will be much easier if it's a plugin. If you know POE, I think I could compare what you're trying to publish as a POE component. That would be translated in a Dancer::Plugin. Now, if your code can't fit in a plugin, then first, we'd like to see the code, and second, if it's really out of the Plugin's league, then we could think of something else. Like Dancer::Component. But I honestly doubt it can't fit into a Plugin dams. On Sun, Dec 8, 2013, at 08:42 AM, Yanick Champoux wrote: > >> Why can't this be a plugin, by the way? > > I'll make the tactical mistake of jumping into this thread before my > first coffee, and say that I agree with Sawyer: I think that those > modules could very well find their home in the ::Plugin namespace. > > Typically, plugins do add keywords, but they don't have to: they can > also extend the functionality of the application itself. > > Henk, do you already have some of your code on GitHub? If it is, it > would probably be easier to use one of them as an example of that I mean. > > Joy, > `/anick > > _______________________________________________ > dancer-users mailing list > dancer-users(a)dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users

2 1

Namespace for load_app modules
by Henk van Oers 08 Dec '13

08 Dec '13

I am a user of https://metacpan.org/pod/Dancer#load_app <q> load_app 'Forum', prefix => '/forum', settings => {foo => 'bar'}; </q> I reuse controler modules in different deployment modules. Some controler modules are useful CPAN modules. They do not extend the DSL, so, are not Dancer::Plugin's. Can I use the namespace Dancer::App for those modules? -- Henk

5 15

Trying to use Dancer2::Plugin::REST, what did I do wrong?
by Pierre M 07 Dec '13

07 Dec '13

Hi, here is what I'm trying to do: package mbf; use Dancer2; use Dancer2::Plugin::REST; prepare_serializer_for_format; get '/page.:format' => sub { [ 'some key' => 'value', 'something'=> 'else', ] }; true; And when I go to http://localhost:5000/page.json<http://localhost:5000/markets.json>I get ARRAY(0x23b3880) in the browser. The data was not serialized. What did I do wrong? As an alternative I've done something that works: package mbf; use Dancer2; use Dancer2::Serializer::JSON; get '/page.json' => sub { to_json([ 'some key' => 'value', 'something'=> 'else', ]); }; true; And in the browser I get what I expect: ["some key","value","something","else"] I would like to use use Dancer2::Plugin::REST though, to leave the choice of format to whoever will use the API. I noticed a detail in the module's documentation. The two examples given are: get '/user/:id.:format' => sub { and get qr{^/user/(?<id>\d+)\.(?<format>\w+)} => sub { The first example is similar to my case, but not the second one. And the documentation says: "Regexp routes will use the file-extension from captures->{'format'} to determine the serialization format." Which seems to indicate that only the second use case in the documentation would work. I tried it. It didn't work for me either. I must be doing something wrong. Any idea? --- Pierre Masci

3 7

Running a bot as a REST webservice
by Pierre M 07 Dec '13

07 Dec '13

Hi, I'm making a bot. I'm trying to integrate it into a Dancer2 app, in order to make a REST API for it, and later be able to interact with it from the browser. It logs in to an external webservice, like this: $bot->login($username, $password); This stores some credentilals in the bot, which uses them for other requests. And then it does some other stuff: $->do_stuff; The bot exists and can make these very basic operations from a script. To create the REST API with Dancer2, I made something in those lines: my $bot = MyBot->new; post '/login.json' => sub { my ($username, $password) = (params->{username}, params->{password}); $bot->login($username, $password); # Store credentials in the bot }; This works perfectly. And then post '/do_stuff.json' => sub { $bot->do_stuff; } This doesn't work: when I call '/login.json', followed by '/do_stuff.json', the second request fails because the credentials are not present: it seems to not be interacting with the same $bot object than the login request. It works if add $bot->login( ... ) at the beginning of the '/do_stuff.json' subroutine, but I don't want to login at each new request. What is a clean solution for this use case? * 30 minutes later * I have found Dancer2::Plugin::Adapter<https://metacpan.org/pod/Dancer2::Plugin::Adapter>and the "singleton" scope, which seems to be what I need. But it won't install. I will send a RT ticket. Any idea for an alternative solution?

2 5

Re: [dancer-users] Apache environment in FCGI app
by Keith Lawson 06 Dec '13

06 Dec '13

I didn't get any responses here or on IRC so I'm posting the solution I went with to get it archived. >>>> Keith Lawson 11/29/13 10:22 AM >>> >Hello, > > I'm working on my first Dancer application and want to deploy it in our standard server environment here. > > For authentication/authz we have custom mod_perl auth handlers that set Apache environment variables with user ID, group membership etc. >I'm trying to write an implementation of Dancer::Plugin::Auth::Extensible::Provider that does auth/authz by reading those environment variables however %ENV isn't populated in my Dancer app. Looking at the source of public/dispatch.fcgi I noticed the following: > ># For some reason Apache SetEnv directives dont propagate ># correctly to the dispatchers, so forcing PSGI and env here ># is safer. > set apphandler => 'PSGI'; > set environment => 'production'; > > Can anyone tell me if it's possible to get %ENV through to my Dancer app or perhaps a different approach for auth/authz that uses $ENV{REMOTE_USER} and our custom Apache environment variables? > I never did get FCGI to work so I tried regular CGI, here's my apache config for my app: SetEnv DANCER_ENVIRONMENT "development" <Directory "/var/dancerdev/filesafe"> AllowOverride None Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch Order allow,deny Allow from all AddHandler cgi-script .cgi </Directory> ScriptAlias /filesafe /var/dancerdev/filesafe/public/dispatch.cgi This works but I had to comment out where %ENV keys were explicitly set in dispatch.cgi so that the Apache conf directives for dev/prod environment worked properly: --- dispatch.cgi.dist 2013-12-05 09:21:35.917592251 -0500 +++ dispatch.cgi 2013-12-05 09:20:06.912736198 -0500 @@ -6,8 +6,8 @@ # For some reason Apache SetEnv directives dont propagate # correctly to the dispatchers, so forcing PSGI and env here # is safer. -set apphandler => 'PSGI'; -set environment => 'production'; +# set apphandler => 'PSGI'; +# set environment => 'production'; my $psgi = path($RealBin, '..', 'bin', 'app.pl'); die "Unable to read startup script: $psgi" unless -r $psgi; My first crack at doing Dancer auth/authz was to write a provider for Dancer::Plugin::Auth::Extensible with subs that rely on %ENV like this: sub authenticate_user { my ($self, $username, $password) = @_; return $ENV{REMOTE_USER}; } However I couldn't figure out why $ENV{REMOTE_USER} wasn't getting to the plugin so I gave up. I just ended up protecting portions of my new app with a <Location> stanza using our Apache2::AuthCookie auth handlers: <Location /filesafe/priv> order allow,deny allow from all AuthType Site::LDAPCookieHandler2 AuthName dancerdev PerlAuthenHandler Site::LDAPCookieHandler2->authenticate PerlAuthzHandler Site::LDAPCookieHandler2->authorize require valid-user satisfy all </Location> Then in my dancer app I protect portions like this: get '/priv/hello' => sub { die unless $ENV{REMOTE_USER}; return "Hi there ".$ENV{REMOTE_USER}; }; This won't solve authorization for me but I won't have a need for this in this app. > Thanks, > Keith. > > > -------------------------------------------------------------------------------- This information is directed in confidence solely to the person named above and may contain confidential and/or privileged material. This information may not otherwise be distributed, copied or disclosed. If you have received this e-mail in error, please notify the sender immediately via a return e-mail and destroy original message. Thank you for your cooperation.

2 2

Dancer2 and Storable session
by Tzacos 06 Dec '13

06 Dec '13

Hi, i'm writing an application for a security appliance. Thus, i don't want session to be store on the browser side with cookie, but on the server. I'm searching fr a session engine that can store session data on the server and encrypted. Is there any? regards

2 1

Plack::App::MCCS for minification, precompression, deflation and caching ?
by Pierre M 06 Dec '13

06 Dec '13

Does anyone use this module <https://metacpan.org/pod/Plack::App::MCCS> ? Apparently it would feature improved minification, precompression, deflation and caching (read "Wait, aren't there existing plack middlewares for that?" in the doc). The description sounds great, why is it not mentioned anywhere in the perl/dancer world? Shall I use it?

2 1

Plugin nesting in Dancer2
by Marco Pessotto 06 Dec '13

06 Dec '13

Hello all! I have a question about the plugin nesting in Dancer2. I'd like to know if using a plugin (notably the Dancer2::Plugin::Database) inside another plugin is doable or deprecated or hacky or unsupported or just can't work. This used to work with Dancer1, but now it's unclear if and how it should work, as we don't do "use Dancer qw/:syntax/" anymore. The app at runtime seems to work, I get the expected output of the dumped D2::P::D object, but in a Dancer2 qw/:script/ it fails with a "deep recursion" error. use Dancer2 ":script"; use Dancer2::Plugin::Test; print to_dumper(hello); perl -I lib t/script.t 1..1 DEPRECATED: Dancer2::Plugin::Test calls 'dsl' instead of '$dsl->dsl'. at /home/melmoth/perl5/perlbrew/perls/perl-5.16.3/lib/site_perl/5.16.3/Dancer2/Plugin/Database.pm line 57. DEPRECATED: Dancer2::Plugin::Test calls 'dsl' instead of '$dsl->dsl'. at /tmp/MyApp/lib/Dancer2/Plugin/Test.pm line 6. DEPRECATED: Dancer2::Plugin::Test calls 'dsl' instead of '$dsl->dsl'. at /tmp/MyApp/lib/Dancer2/Plugin/Test.pm line 6. DEPRECATED: Dancer2::Plugin::Test calls 'dsl' instead of '$dsl->dsl'. at /tmp/MyApp/lib/Dancer2/Plugin/Test.pm line 6. DEPRECATED: Dancer2::Plugin::Test calls 'dsl' instead of '$dsl->dsl'. at /tmp/MyApp/lib/Dancer2/Plugin/Test.pm line 6. DEPRECATED: Dancer2::Plugin::Test calls 'dsl' instead of '$dsl->dsl'. at /tmp/MyApp/lib/Dancer2/Plugin/Test.pm line 6. Deep recursion on anonymous subroutine at /home/melmoth/perl5/perlbrew/perls/perl-5.16.3/lib/site_perl/5.16.3/Dancer2/Core/Role/DSL.pm line 72. # Looks like your test exited with 255 before it could output anything. The test app is the following (also packed in the tarball attached with the tests). conf: ### cut #### plugins: Database: driver: SQLite database: 'foo.sqlite' ### cut #### app: ### cut #### package MyApp; use strict; use warnings; use Dancer2; use Dancer2::Plugin::Test; our $VERSION = '0.1'; get '/' => sub { my $dbh = hello; return to_dumper($dbh); }; true; ### cut #### plugin: ### cut #### package Dancer2::Plugin::Test; use strict; use warnings; use Dancer2::Plugin; use Dancer2::Plugin::Database; register hello => sub { my $dsl = shift; return database; }; register_plugin; 1; ### cut #### Thanks in advance Best wishes -- Marco

2 2