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

Dancer::SessionFactory::Memcached released
by David Golden 10 Apr '14

10 Apr '14

It's amazing how little code is needed with Moo and the role. Mostly, it just delegates everything. https://github.com/dagolden/dancer-sessionfactory-memcached/blob/master/lib… David -- David Golden <xdg(a)xdg.me> Take back your inbox! → http://www.bunchmail.com/ Twitter/IRC: @xdg

2 2

Can't do a hook-based db transaction per request
by Punter 30 Jun '13

30 Jun '13

And the request I can't do it is because of a bug of Dancer2, which I have filed here: https://github.com/PerlDancer/Dancer2/issues/292 What I want to do, is simply to send "BEGIN" to the database before the web request starts, and then at the end of the request, and depending on whether it ended in an error or it succeeded, send "ROLLBACK" or "COMMIT" respectively. But I can't do it because of the bug. Please fix soon, because it's absolutely necessary for my work. Thanks,

1 0

setting mime type
by Mr. Puneet Kishor 30 Jun '13

30 Jun '13

I am sending back to the browser html5 video code via JSON as shown below. The code then loads mp4 video, but I need to set the correct mime type for the video. How do I do that with Dancer? get '/p/:uri' => sub { return to_json { html => qq{ <video width="960" height="540" poster="path/to/$mov.jpg" controls> <source type="video/mp4" src="path/to/$mov.mp4" /> <source type="video/m4v" src="path/to/$mov.m4v" /> <source type="video/ogg" src="path/to/$mov.ogv" /> <source type="video/webm" src="path/to/$mov.webm" /> Sorry, your browser has no video playback capabilities </video> <br /> <b>$title</b> }; }; }; Note that the "path/to/.." is relative to the Dancer app, so the video is being served by Dancer. For a totally orthogonal reason I am unable to serve the static files from a different web server. Many thanks, -- Puneet Kishor

4 3

Dancer built-in server seems to choke
by Mr. Puneet Kishor 28 Jun '13

28 Jun '13

This is a weird one, and I have started noticing this only recently, so perhaps with one of the recent updates. Here are the logs (trimmed for sanity) 12:55:54-punkish~/Projects/punkish (master)$ bin/app.pl >> Dancer 1.3115 server 183 listening on http://0.0.0.0:3000 >> Dancer::Plugin::Ajax (1.00) == Entering the development dance floor ... [183] debug @0.003543> [hit #2]sending back first-page in /path/to/app/lib/punkish.pm l. 34 [183] debug @0.012338> [hit #4]sending back second-page in /path/to/app/lib/punkish.pm l. 34 [183] debug @0.003169> [hit #5]sending back second-page in /path/to/app/lib/punkish.pm l. 34 [183] debug @0.003327> [hit #8]sending back second-page in /path/to/app/lib/punkish.pm l. 34 [183] debug @0.003521> [hit #11]sending back first-page in /path/to/app/lib/punkish.pm l. 34 The app itself is rather simple # ajax request get '/p/:uri' => sub { debug "sending back $uri"; .. return to_json $result; }; # If the URI has no /p/ in it then it is a non-ajax call. # Send back an empty template and the name of the page # to be called via ajax # !get '/*?' get '/*?' => sub { .. return template 'index', $result, { layout => 'main' }; } If the user enters a full path in the browser, Dancer sends back the template with the name of the actual page to be loaded which is then called via with the /p/ in the path. If Dancer sees /p/ in the path then it sends back only the specific page's content. This is my home-grown version of a "single-page-app" that all the cool kids are making nowadays, except I am not yet ready to jump ship to Nodejs. The problem is, the first load happens fine. The ajax calls after that just hang. As you can see from the log above, the ajax call to http://localhost:3000/first-pagehappened fine, but after that, 3 consecutive requests to http://localhost:3000/second-page got hung up, and then suddenly, as if a plug had been removed, three of them were sent back. I also tried a direct `curlhttp://localhost:3000/p/second-page` and that too just hung. What is going on? Oh, and I have a corollary question -- is it possible to customize that debug message? For example, instead of the rather unhelpful (to me) [183] debug @0.003543> [hit #2]sending back first-page in /path/to/app/lib/punkish.pm l. 34 I would like to see something like Jun 26, 2013 13:18:23 - sending back first-page in /path/to/app/lib/punkish.pm l. 34 In fact, the actual `path/to/app` is really long in my case. I would like to just trim that. Many thanks, -- Puneet Kishor

1 0

Dancer built-in server seems to choke
by Puneet Kishor 27 Jun '13

27 Jun '13

This is a weird one, and I have started noticing this only recently, so perhaps with one of the recent updates. Here are the logs (trimmed for sanity) 12:55:54-punkish~/Projects/punkish (master)$ bin/app.pl >> Dancer 1.3115 server 183 listening on http://0.0.0.0:3000 >> Dancer::Plugin::Ajax (1.00) == Entering the development dance floor ... [183] debug @0.003543> [hit #2]sending back first-page in /path/to/app/lib/punkish.pm l. 34 [183] debug @0.012338> [hit #4]sending back second-page in /path/to/app/lib/punkish.pm l. 34 [183] debug @0.003169> [hit #5]sending back second-page in /path/to/app/lib/punkish.pm l. 34 [183] debug @0.003327> [hit #8]sending back second-page in /path/to/app/lib/punkish.pm l. 34 [183] debug @0.003521> [hit #11]sending back first-page in /path/to/app/lib/punkish.pm l. 34 The app itself is rather simple # ajax request get '/p/:uri' => sub { debug "sending back $uri"; .. return to_json $result; }; # If the URI has no /p/ in it then it is a non-ajax call. # Send back an empty template and the name of the page # to be called via ajax # !get '/*?' get '/*?' => sub { .. return template 'index', $result, { layout => 'main' }; } If the user enters a full path in the browser, Dancer sends back the template with the name of the actual page to be loaded which is then called via with the /p/ in the path. If Dancer sees /p/ in the path then it sends back only the specific page's content. This is my home-grown version of a "single-page-app" that all the cool kids are making nowadays, except I am not yet ready to jump ship to Nodejs. The problem is, the first load happens fine. The ajax calls after that just hang. As you can see from the log above, the ajax call to http://localhost:3000/first-page happened fine, but after that, 3 consecutive requests to http://localhost:3000/second-page got hung up, and then suddenly, as if a plug had been removed, three of them were sent back. I also tried a direct `curl http://localhost:3000/p/second-page` and that too just hung. What is going on? Oh, and I have a corollary question -- is it possible to customize that debug message? For example, instead of the rather unhelpful (to me) [183] debug @0.003543> [hit #2]sending back first-page in /path/to/app/lib/punkish.pm l. 34 I would like to see something like Jun 26, 2013 13:18:23 - sending back first-page in /path/to/app/lib/punkish.pm l. 34 In fact, the actual `path/to/app` is really long in my case. I would like to just trim that. Many thanks, -- Puneet Kishor

1 0

How are people logging with Dancer2
by David Golden 27 Jun '13

27 Jun '13

I'm looking at logging and notice that there don't appear to be any handlers other than the core ones. Then I look at Dancer2::Logger::File and see these issues: * log_path is documented but no code actually uses it * holds an open file-handle. No flush/reopen on a signal, so log rotation means restarting the whole app So what are people using Dancer2 actually doing for logging? Just Console grabbed by a supervisor daemon? David -- David Golden <xdg(a)xdg.me> Take back your inbox! → http://www.bunchmail.com/ Twitter/IRC: @xdg

2 2

Sessions in Dancer2::Test
by Jeff Boes 26 Jun '13

26 Jun '13

First, a documentation bug to report: http://search.cpan.org/~sukria/Dancer2-0.04/lib/Dancer2/Session/YAML.pm This page links to "Dancer2::Session" in the "See Also" section, but there's nothing at the link. Now to my question: I'm working on unit tests for a Dancer2 application. The application is a typical log-in, which is supposed to store some data in the session, so subsequent requests can make use of it. During the login page processing, I can see that the session is being affected. But during the next unit test, which is a follow-up request, my session is empty. I'm using the YAML engine for session control. Is there a way for each dancer_request call to share a session? -- Jeff Boes <>< jeff(a)endpoint.com 269-408-0811

1 0

Problem with dancer_response Dancer2::Test
by Jeff Boes 26 Jun '13

26 Jun '13

My test scripts are failing after a call like this: my $response = dancer_response POST => '/private/affiliate/login.html', { params => { ... }, }; What's happening is that the response comes back with $response->status == 200, as expected, but $response->content comes back as an uninterpolated layout file: ... <body> <% content %> <div id="footer"> Powered by <a href="http://perldancer.org/">Dancer</a> <% dancer_version %> </div> ... I've tried walking through this in the Perl debugger, but I keep losing my way. -- Jeff Boes <>< jeff(a)endpoint.com 269-408-0811

1 1

On the TODO list: perhaps make this more configurable (Dancer-Plugin-Auth-Extensible) (RFC)
by Henk van Oers 25 Jun '13

25 Jun '13

This works for me. No need for 'no_login_handler: 1' in config.yml diff -u Extensible.pm Extensible.pm.new --- Extensible.pm 2013-06-25 15:05:39.000000000 +0200 +++ Extensible.pm.new 2013-06-25 21:20:50.000000000 +0200 @@ -12,8 +12,10 @@ my $settings = plugin_setting; my $loginpage = $settings->{login_page} || '/login'; +my $userhomepage = $settings->{user_home_page} || '/'; my $logoutpage = $settings->{logout_page} || '/logout'; my $deniedpage = $settings->{denied_page} || '/login/denied'; +my $exitpage = $settings->{exit_page}; ##Dancer::Logger::warning(<<CHANGEWARNING); @@ -559,7 +561,7 @@ if ($success) { session logged_in_user => params->{username}; session logged_in_user_realm => $realm; - redirect params->{return_url} || '/'; + redirect params->{return_url} || $userhomepage; } else { vars->{login_failed}++; forward $loginpage, { login_failed => 1 }, { method => 'GET' }; @@ -571,6 +573,8 @@ session->destroy; if (params->{return_url}) { redirect params->{return_url}; + } elsif ($exitpage) { + redirect $exitpage; } else { # TODO: perhaps make this more configurable, perhaps by attempting to # render a template first. ------------------- Next on the TODO list: A new default '/login' route. -- Henk

1 0

Simple patch breaks tests (Dancer-Plugin-Auth-Extensible)
by Henk van Oers 25 Jun '13

25 Jun '13

What is wrong with the tests? https://travis-ci.org/bigpresh/Dancer-Plugin-Auth-Extensible/jobs/7750714 The patch works fine under stand-alone and apache. -- Henk

1 0