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

Dancer RBAC tutorial
by Puneet Kishor 20 Apr '12

20 Apr '12

From a little scouting around, Dancer::Plugin::RBAC seems to be the preferred way to go about setting up a protected/authenticated web app. I would appreciate it if someone can direct me to a tutorial showing how to implement DP::RBAC (or, any other recommended alternative). Many thanks, -- Puneet Kishor

1 0

Multiple "optional" components in URLs
by Ovid 19 Apr '12

19 Apr '12

Hi all, I had this in my Dancer code: get '/instance/?:id?' => sub { my $id = param('id'); ... }; That let's me do this: http://localhost:5000/instance # get a list of instances http://localhost:5000/instance/ # get a list of instances http://localhost:5000/instance/213 # get instance 213 However, after I typoed a URL, I discovered that it would also match: http://localhost:5000/instances # get instance 's' This is because of the generated regex: /^\/instance\/?([^\/]+)?$/ I've fixed this by switching to regex paths, but I would argue for the following to be the regex generated from my example above: /^\/instance(?:\/([^\/]+))?$/ In other words, if you have multiple "optional" components in a path, they are all required up to, but excluding, the last optional component found in the URL that is accessed. You could then safely visit /instance, /instance/, and /instance/42. This would allow the easy construction of things like this: /member/?:member_id?/?:tag_id? Allowing you to access: /member /member/ /member/3 /member/3/ /member/3/7 This would make it easy to write the sort of URLs that I often write. Speculation: at that point, if we have an optional component, we could *assume* that the preceding / must be optional (?), leading to a simple URL: /member/:member_id?/:tag_id? Once something optional is found, nothing after it may be mandatory (otherwise, if you had optional items collapsing out of the URL, it would be a semantic mess that's impossible to sort through). Thoughts? Cheers, Ovid -- Live and work overseas - http://www.overseas-exile.com/ Buy the book - http://www.oreilly.com/catalog/perlhks/ Tech blog - http://blogs.perl.org/users/ovid/ Twitter - http://twitter.com/OvidPerl/

1 0

Yelp-ish app with Dancer
by Puneet Kishor 15 Apr '12

15 Apr '12

I am thinking of reinventing the wheel, but before I dive in, am wondering if there is already a (preferably Dancer-based, or at least) Perl-based code base that I can build upon. The idea is simple... see something, rate it, recommend it (or not) with a little write-up, add a photo or two, tag it, and also, be able to "follow" other recommenders. Kinda like a mash-up of Yelp and Facebook. Many thanks for any suggestions. -- Puneet Kishor

4 4

Exception in before_template_render hook does not render error_template
by Alex C 14 Apr '12

14 Apr '12

I noticed this when trying to make a database call in the before_template_render hook (to conditionally set a token if a row exists). To reproduce: $ echo "my custom error message" > views/error.tt --------- package App; use Dancer ':syntax'; set show_errors => 0; set error_template => 'error.tt'; hook before_template_render => sub { die; }; get '/' => sub { template 'index.tt'; }; true; --------- It can be resolved by adding a simple check inside Dancer::Template::Abstract::apply_renderer() : --------- @@ -73,9 +73,13 @@ sub apply_renderer { ($tokens, undef) = _prepare_tokens_options($tokens); + my $is_error_template + = $view eq Dancer::Config::setting('error_template') ? 1 : 0; + $view = $self->view($view); - Dancer::Factory::Hook->execute_hooks('before_template_render', $tokens); + Dancer::Factory::Hook->execute_hooks('before_template_render', $tokens) + unless $is_error_template; --------- Is it worth making a PR for this? -- Alex

1 2

Plugin::Database failed on reconnect
by WK 12 Apr '12

12 Apr '12

Hi! My little application stand whole night and when on morning user made first request, app did not connect properly to Database. Error was like: DBD::mysql::db do failed: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '&amp;amp;amp;amp;amp;amp;amp;amp;#39;utf8&amp;amp;amp;amp;amp;amp;amp;am' at line 1 at /usr/local/share/perl/5.12.4/Dancer/Plugin/Database.pm line 198. /usr/local/share/perl/5.12.4/Dancer/Plugin/Database.pm around line 198 195 return; 196 } elsif (exists $settings->{on_connect_do}) { 197 for (@{ $settings->{on_connect_do} }) { 198 $dbh->do($_) or Dancer::Logger::error( 199 "Failed to perform on-connect command $_" 200 ); 201 } As i use also Plugin::EscapeHTML with automatic_escaping: 1, it seems that there is some problem with 2 of them together. At least there is made some weird escaping. Or? After restarting app, connenction to DB was alright. Main problem: how to avoid reconnecting failure? -- Wbr, Kõike hääd, Gunnar

3 5

UTC timestamp for logger_format
by Alex C 12 Apr '12

12 Apr '12

I noticed that Dancer gets its timestamps using localtime(). I prefer to have all my logs in UTC. Please can I suggest the following patch to Dancer::Logger::Abstract to provide an option for this? @@ -94,6 +94,7 @@ sub format_message { t => sub { Encode::decode(setting('charset') || 'utf8', POSIX::strftime( "%d/%b/%Y %H:%M:%S", localtime )) }, T => sub { POSIX::strftime( "%Y-%m-%d %H:%M:%S", localtime ) }, + U => sub { POSIX::strftime( "%Y-%m-%d %H:%M:%S", gmtime ) }, P => sub { $$ }, L => sub { $level }, D => sub { -- Alex

4 4

Config Setting "behind_proxy: true" gives incorrect proxied protocol
by Gurunandan Bhat 05 Apr '12

05 Apr '12

Hi, I am hosting a Dancer Web Application behind an Apache proxy using the recommended (in Dance::Deployment) configuration. The application can be accessed via a secure URL: https://some.domain.comand I have set 'behind_proxy: "true"' in my config.yml. However when I use [% request.uri_base %], I get http://some.domain.com and not https://some.domain.com which is what I am expecting. Is there a way to have request.uri_base return the correct proxied protocol (in this case https) rather than 'http'? Thank you - Gurunandan

3 5

Logging and "info"
by Ovid 28 Mar '12

28 Mar '12

Hi all, I noticed that when I'm trying to log information, I have several log levels (core() apparently reserved for the core, as one might expect): * debug * warning * error I have a case where I would like to log informational data that is neither a warning or error. However, I don't want to log it as debug because I still want this logged in production. I propose adding an "info" log level that has a log level of 4 and thus should always be logged if logging is enabled. It would behave like other log levels: info "All bid requests were denied for auction $auction_id"; Does this make sense or am I missing something obvious? Here are the log levels from Log::Log4perl (http://search.cpan.org/~mschilli/Log-Log4perl-1.36/lib/Log/Log4perl.pm#Log_…) $logger->trace("..."); # Log a trace message $logger->debug("..."); # Log a debug message $logger->info("..."); # Log a info message $logger->warn("..."); # Log a warn message $logger->error("..."); # Log a error message $logger->fatal("..."); # Log a fatal message Cheers, Ovid -- Live and work overseas - http://overseas-exile.blogspot.com/ Buy the book - http://www.oreilly.com/catalog/perlhks/ Tech blog - http://blogs.perl.org/users/ovid/ Twitter - http://twitter.com/OvidPerl/

8 15

Invalid content-type sended by dancer when error 500 happens
by Tomasz Konojacki 24 Mar '12

24 Mar '12

Hi! I'm using Dancer 1.3093 (latest in ActiveState PPM) under Windows. I have created application using "dancer -a test" command, and modified test/lib/test.pm so now it looks like this: --beginning of code-- # This is application generated by "dancer -a test", only test/lib/test.pm was modified package test; use Dancer ':syntax'; use Exception::Class ( foobar => { description => 'Arguments passed to function are invalid.' }, ); our $VERSION = '0.1'; get '/' => sub { <<EOF; <!doctype html> <html> <head><title>test</title></head> <body> <form action="/" method="post"> <input type="text" name="login"><br> <input type="password" name="password"><br> <input type="submit" name="submit"> </form> </body> EOF }; post '/' => sub { die 'error!'; }; true; ---end of code--- When I run app.pl with argument "--environment=production", connect to the site with browser, and click "submit", Dancer returns error 500 (as expected), but instead of "text/html" Content-Type, it has "application/x-www-form-urlencoded" MIME type. What am I doing wrong? Thanks, Tomasz

3 4

Plugin hooks and prefix
by Ovid 23 Mar '12

23 Mar '12

Hi all, If I do this: use Dancer ':syntax'; use Dancer::Plugin::Weborama::Authentication; prefix '/companyname' => sub { post '/bidder' => sub { ... }; }; I would very much like my Authentication plugin to register a 'before' hook which only fires if the /companynameprefix is set. What's the best way of doing this? Cheers, Ovid -- Live and work overseas - http://overseas-exile.blogspot.com/ Buy the book - http://www.oreilly.com/catalog/perlhks/ Tech blog - http://blogs.perl.org/users/ovid/ Twitter - http://twitter.com/OvidPerl/

3 3