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

Flexible credentials with Dancer::Plugin::Database
by Lutz Gehlen 06 May '14

06 May '14

Hello all, I would like to use Dancer::Plugin::Database to access a postgresql database from my dancer application. The docu suggests to configure the connection like this: plugins: Database: driver: 'mysql' database: 'test' host: 'localhost' port: 3306 username: 'myusername' password: 'mypassword' connection_check_threshold: 10 dbi_params: RaiseError: 1 AutoCommit: 1 on_connect_do: ["SET NAMES 'utf8'", "SET CHARACTER SET 'utf8'" ] log_queries: 1 handle_class: 'My::Super::Sexy::Database::Handle' However, I would like to store the login details, namely username and password, in a different file that I can exclude from version control by gitignore for security reasons as well as to enable my co-developers to use different credentials on their system. Is there a good way to achieve this? Thanks for your help, Lutz

4 7

Doc bug: params() return value
by Warren Young 05 May '14

05 May '14

This page claims params() returns a hashref, always: https://metacpan.org/pod/Dancer::Request#params Not true. It only does so in scalar context. Thus: myfunction(params); will pass myfunction a hash which gets flattened to an array, not a hashref. The fix is myfunction(scalar params); Also, this link from that section: https://metacpan.org/pod/Dancer::Request#params-source is missing the "-source" bit at the end. (The latter link does document this behavior of params(), but that didn't stop me from banging my head against a wall for an hour or two while I still believed what the first page said.)

3 4

Major Dancer 2 release: 0.140000
by sawyer x 01 May '14

01 May '14

Hey everyone! I just released a new version of Dancer 2. It's a major one. I'd like to share a bit about it. *Semver:* First of all, you probably noticed a completely different release version. Previous ones were 0.12, 0.13, which is why it would make sense for this one to be 0.14. In fact, it is! We've decided to use a convention called Semver[1]. It allows us to indicate to you, the users and developers, what changes we've done. *Changelog:* Additionally, if you check the Changes file, you will see a few more interesting gems. We only have features in this release, there are four changes which were introduced by the same three people (Stefan Hornburg, Mickey Nasriachi, and myself - Sawyer X). *Hackathon:* The reason for many of these changes were a Dancer 2 core hackathon that was conducted at Booking.com's HQ with the aforementioned three core devs last Thursday, a day before the Dutch Perl Workshop. We have worked hard on cleaning up several things that bugged us for a while. Allow me to fill you in on those: *Deliverables:** Replace Config role with better ConfigReader role. * Move App-related attributes (engines) to App instead of config role. Dancer2::Core::Role::Config has been a sore point for a long while. It was pushing attributes to unrelated classes, contained triggers which caused us several attempts to untangle, and was something we wanted to clean up. The new ConfigReader just reads a configuration, allows local and global triggers, and the necessary attributes went into the appropriate class. Yay! * Untangle Runner-Server (removing Server entirely). Dancer2 had a setup of Server handlers (under the ::Server class name), one for PSGI app handling, and the other for a standalone server. The idea was: you call "dance()" (or "start()") and Dancer will either return a PSGI coderef (which goes to Plack) or start a local development web server. Thus we had ::Server::PSGI and ::Server::Standalone. While this makes total sense, it doesn't make any sense at all. First of all, the standalone server is, in fact, a PSGI server. The PSGI server handler (::Server::PSGI) was not a server, but a coderef. Secondly, the standalone server would still need the PSGI coderef. Confused? Good. Now you understand why we wanted to remove it. What we did was keep the Runner class, have it hold a "server" attribute, which will be lazily evaluated to a PSGI development standalone server. If you will need a standalone server run, it will build it, and call it with a PSGI coderef. There is now no ::Server handler classes. That entire layer has been removed. * Replace HTTP::Server::Simple::PSGI with HTTP::Server::PSGI. Since Plack comes with HTTP::Server::PSGI, we could remove a dependency, while replacing it with a much better module. It is more maintained, doesn't require (monkey-)patching (which we introduced in HTTP::Server::Simple::PSGI) and already does all we need. There is now also no ability to daemonize the development server within Dancer2 since 1. Plack already allows it via command line, and 2. you should not be running the development server in the background. If you do, please consider changing it. *Non-hackathon changes:* Cookie building improvements and using Plack::Middleware::Head to serve the head (instead of an ugly around() method), both by Russell Jenkins, and supporting deserializing from DELETE methods as well, done by Russell, Yanick Champoux, and Sawyer. *Thanks:* Major thanks goes to all people mentioned in the changelog in this release: Mickey Nasriachi, Stefan Hornburg, Russell Jenkins, Yanick Champoux, and Sawyer X. Another major thanks goes to our fantastic community. Thank you for the feedback, support, and help! Please try out this new version and update us on any issue you may find! [1] Semantic Versioning: semver.org.

3 6

Problems Directly printing to Apache2::RequestRec buffer with dancer
by Brian Brandes 01 May '14

01 May '14

I'm retrofitting Dancer onto an existing perl application of mine. However, some of the code, for large report generations, will directly print to the web buffer. This is resulting in nothing come back in my response. E.g, with this route handler: get '/buffertest' => sub { my $r = request->input_handle; $r->print("hello world"); # ref $r == Apache2::RequestRec return; }; And then I make a request to it... ==== Begin Request Dump ==== GET http://localhost/buffertest Content-Type: application/json === End Request Dump ==== ... , the response won't come back: ==== Begin Response Dump ==== HTTP/1.1 200 OK Connection: close Date: Wed, 30 Apr 2014 16:37:19 GMT Server: Apache Vary: Accept-Encoding,User-Agent Content-Length: 0 Content-Type: text/html; charset=utf-8 Client-Date: Wed, 30 Apr 2014 16:37:20 GMT Client-Peer: 10.5.15.5:80 Client-Response-Num: 1 P3P: CP="CAO PSA OUR" === End Response Dump ==== IF however, I do something like enable autoflushing ($|=1) then I will get "hello world" back, but that feels like a very brutal hack. Is there an equivalent way to flush response in Dancer?

2 1

Dancer2::Session::DBIC
by Stefan Hornburg (Racke) 30 Apr '14

30 Apr '14

Besides a bunch of improvements to Dancer2 core we did on a small hackathon in Amsterdam there is now a Dancer2 version of my DBIC session engine: https://metacpan.org/pod/Dancer2::Session::DBIC Please check it out and test it, it will be also part of my Dancer/DBIC presentation on the Dutch Perl Workshop tomorrow. Regards Racke -- Perl and Dancer Development Visit our Open Source conference on E-commerce: http://www.ecommerce-innovation.com/

2 1

Deploy on Windows 2008 R2
by Jean-Marc Choulet 30 Apr '14

30 Apr '14

Hello, What is the best method to deploy a Dancer application on Windows 2008 ? Before, I deployed all my apps on Linux with no problems, but now, I must install some apps on Windows. Thanks, Jean-Marc.

2 1

Stepping away from Dancer
by David Golden 30 Apr '14

30 Apr '14

Due to an employment change, I no longer work with Dancer with any regularity. I have a number of Dancer plugins -- and many of the D2 ones are in various states of breakage due to the D2 API churn. As those who know my other Perl community work can imagine, I have a severe "round tuit" shortage and I don't expect to maintain my Dancer plugins or fix the broken ones. I've marked them all as "HANDOFF" on PAUSE and welcome anyone who volunteers to take some or all of them over. Regards, David

4 8

Message corrupt error during post
by Joel Roth 26 Apr '14

26 Apr '14

Hi Dancers, During development, I've put a file with the username/email/password on the site (generally bad practice, I know), and have a button for sending a password reminder. When the user posts a form with an "email" field to the /reminder route (see below) it results in the following error, which is issued *after* the mail is sent out: The page 'http://localhost:3000/reminder' couldn't be loaded. Message Corrupt I would expect a redirect to '/reminder-has-been-sent' Do you have any suggestions? Kind regards, Joel -- post '/reminder' => sub { my $email = params->{email}; my $result = find_passwd($email); session user => undef; session failed_login => undef; if ($result) { send_out_mail($result->{email}, $result->{body}); # sent! redirect '/reminder-has-been-sent'; # no redirect } else { redirect '/email-not-found'; } }; There is a "before" clause. before sub { if (!session('user') and request->path_info !~ m{(login|bye|reminder|reminder-has-been-sent|email-not-found)$}) { # Pass the original path requested along to the handler: session requested_path => request->path_info; redirect('/login'); } elsif ( ! authorized( session('user'), request->path_info) and request->path_info ne '/forbidden'){ # Pass the original path requested along to the handler: session requested_path => request->path_info; redirect('/forbidden'); } }; sub find_passwd { my $user_or_email = shift; # we expect to be in Dancer app directory my @entries = read_file('pass'); my $body; my ($name, $email, $username, $password); map { chomp } @entries; foreach my $entry( @entries ){ ($name, $email, $username, $password) = split /\s*:\s*/, $entry; next if $user_or_email ne $username and $user_or_email ne $email; say "-->$name"; $body = mail_body($name, $username, $password); last } return({ email => $email, name => $name, password => $password, body => $body }) if $body; } sub mail_body { my ($name, $username, $password) = @_; my ($first) = $name =~ /(.+?)\s*\S*$/; #say $first; <<FORM; Dear $first, This automated mail contains your login credentials for http://example.com Your username is $username Your password is $password FORM } sub send_out_mail { my( $email, $body) = @_; my $sender = 'joelz(a)pobox.com'; Email::Stuffer->from($sender) ->to($email) ->subject("Reminder") ->text_body($body) ->send; } 1 -- Joel Roth

4 4

Dancer::Plugin::Database Hangs Randomly on check_connection
by James Baer 22 Apr '14

22 Apr '14

Hello - I'm having an issue with Dancer::Plugin::Database that has been hard to reproduce and track down. I have a new app that I just moved to its production environment. It connects to a database that is in a remote data center over a vpn tunnel. Everything functions normally as expected 98% of the time, however occasionally I will hit a worker thread (deployed via Starman) that just hangs trying to get a database handle. It hangs in the _check_connection subroutine until it reaches some timeout. Then will reconnect just fine with a new connection. I'm using plugin version 1.82 and I have traced it down to this line in the plugin: if ($dbh->{Active} && (my $result = $dbh->ping)) { Right at this if statement is where it hangs, i assume while calling the ping function. It seems there is some confusion as to whether the dbh is still active, it then calls ping which hangs for a number of minutes (not sure how many exactly yet, b/t 3-5). This renders this worker thread unresponsive until it times out. It will eventuall fall into the else block and just return false, which then a new connection is established just fine. I have successfully deployed a number of apps using this same plugin with no problems this only difference here is the physical location so there maybe something network related, just not sure where. I have dug into DBI, etc and the ping functions works fine on all my test scripts. Again, this only happens once in a while so I cannot reproduce on command, which makes it difficult to debug. Here is the output of my debug statements, showing the one thread that hangs: [27037] debug @0.005053> [hit #4]Database connection_check_threshold [30] in /usr/local/share/perl5/Dancer/Plugin/Database.pm l. 69 [27037] debug @0.005189> [hit #4]Database handle last check [1398093938] in /usr/local/share/perl5/Dancer/Plugin/Database.pm l. 70 [27037] debug @0.005345> [hit #4]Database calling check_connection in /usr/local/share/perl5/Dancer/Plugin/Database.pm l. 83 [27037] debug @0.005481> [hit #4]Database.pm in check_connection before if active and ping in /usr/local/share/perl5/Dancer/Plugin/Database.pm l. 265 ... other threads working ... [27037] debug @962.134467> [hit #4]Database in check_connectiion false return in /usr/local/share/perl5/Dancer/Plugin/Database.pm l. 285 [27037] debug @962.134667> [hit #4]Database connection went away, reconnecting in /usr/local/share/perl5/Dancer/Plugin/Database.pm l. 90 [27037] debug @962.134894> [hit #4]Database calling get_connection in /usr/local/share/perl5/Dancer/Plugin/Database.pm l. 97 [27037] debug @962.135059> [hit #4]Adding mysql_enable_utf8 to DBI connection params to enable UTF-8 support in /usr/local/share/perl5/Dance Any help or suggestions on where to look next is appreciated. Thank you.

3 4

Useless use of private variable in void context
by Hugues 22 Apr '14

22 Apr '14

Hello in my Dancer App , I've got his construction my $Stock; $Stock->{$NumP} = ( $Num => { Code => $parc->{Code}, NumP => $parc->{NumP}, NumS => $parc->{NumS}, NumC => $parc->{NumC} } ); I've got allways this warning Useless use of private variable in void context at dossier.pm line 271. I check all values before affect $Stock->{$NumP} App works well , how I can remove this warning ?

3 3