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

Perl Dancer Conference 2015 - Call for Papers
by Stefan Hornburg (Racke) 17 Jul '15

17 Jul '15

The Call for Papers for the Perl Dancer Conference 2015 in Vienna is now open! We are accepting presentations in a wide range of topics, for example Dancer, Modern Perl, DBIx::Class, Perl "products" and security. Of course, we are open for any idea and submission. The submission deadline is August 31th, midnight CET. Talks are reviewed and possibly accepted as we receive them. Please use the online form at http://www.perl.dance/talks/submit for submitting your presentation. If you are not going to present at the conference, please spread the word. Regards Racke -- Perl and Dancer Development Visit our Perl::Dancer conference 2015. More information on http://www.perl.dance.

1 0

Adding dancer2 to an existing web site.
by Tom Browder 16 Jul '15

16 Jul '15

I have a web site with primarily static content and a few Perl CGI scripts. 1. Can I start integrating dancer2 a bit at a time without a wholesale site rewrite? 2. What is recommended as the best way to deploy dancer2 under Apache 2.4? Thanks. Best regards, -Tom

4 6

Dancer and forking
by Andrew Beverley 10 Jul '15

10 Jul '15

Dear all, Is there anything that I should be aware of if using fork() in a dancer application? I have some cache update code which can take a while to run, so I'd rather do it in the background. I've therefore done something like this: post '/data' => sub { my $template = ...; fork and return $template; update_cache; exit; } The actual code is in a module, but you get the idea. Thanks, Andy

3 7

Dancer2 v0.161000 on its way to CPAN
by Sawyer X 08 Jul '15

08 Jul '15

Hi everyone, A new version of Dancer2 is on its way to CPAN as we speak. It has a lot of exciting changes that I want to share with you. First of all, it's significantly faster, since the request object is now fully based on Plack::Request. I'm very proud of that. There are still additional spots we want to improve (I'm looking at you, parameters!) and we have room for further optimizations (in fact there's a branch waiting for merging that optimizes it even further), but it's at a much better standing as of this release. Security has improved thanks to work by Andy Beverley (thanks!) and Russell Jenkins (G'day!). Thanks goes to long-time community member, Pedro Melo! The build and install time for Dancer2 has now been substantially improved. We removed unnecessary dependencies (prompted by David Golden!) and no longer require memory cycle tests (unless you have it installed) or Module::Build, since we already support MakeMaker. We now handle a long-standing issue of sending non-hash data. JSON (and other serializers) allow you to serialize arrays or strings but parameters don't work that way. Until now that would crash (and get caught by Dancer, of course, but still annoying), whereas now it silently ignores them for the parameters, but still makes them available via "request->data". An additional "VERSION" method fix, thanks to Miyagawa for reporting! The old dispatcher which goes into effect when you call the "dance" method (although we recommend "to_app" instead) had a small bug fix provided. Changelog with ticket numbers is included below. A big thanks to everyone involved with this release and this lovely community. >From the Dancer core dev team with love, Sawyer. 0.161000 2015-07-08 14:57:16+02:00 Europe/Amsterdam [ BUG FIXES ] * GH #915, #930: Check existence of optional extension headers when behind proxy. (Andy Beverley, Pedro Melo, Russell Jenkins) * GH #926, #940: Set session directory default to $apprdir/session. (Russell Jenkins) * GH #936, #939: Use the error_template configuration on a 404. (Russell Jenkins) * GH #844, #937: Non-hash serialized params do not cause a crash. (Sawyer X) * GH #943: Pass @_ to UNIVERSAL's VERSION so it validates version number. (Sawyer X) * GH #934: Cleanup internals in the old Dispatcher. (Russell Jenkins) [ DOCUMENTATION ] * Sanitize Changes * GH #938: Fix POD link to params keyword. (Ludovic Tolhurst-Cleaver) * GH #935: Provide more details and considerations when using behind_proxy. (Andy Beverley) [ ENHANCEMENT ] * GH #933: use note in tests to produce cleaner non-verbose output (Vernon) * Remove unnecessary dependencies: build chain should be smaller. (Sawyer X) * No need for Module::Build. (Sawyer X) * GH #911: Dancer2 request object is now a subclass of Plack::Request. It's also much faster now. (Sawyer X)

1 0

Re: [dancer-users] Sad news regarding James Aitken (LoonyPandora),
by Richard James 30 Jun '15

30 Jun '15

Just found out the sad news that James is no longer with us.Got a reply to his email with the bad from one of his brothers in Manchester.We saw a lot of him socially around 2008/9 before he left Manchester for London and liked him a great deal. Could anyone please tell me what happened, where his funeral took place, did his estranged family find out in time and is there a grave to visit and pay our last respects? Sorry to drag up sad memories but don't want to hassle his family as they are still understandably very upset.Thanks,Richard.

3 2

plugin_setting function
by Kadir Beyazlı 30 Jun '15

30 Jun '15

Hi All, I am studying plugins so I am reading manual from cpan (thanks to sawyer) and testing all codes at my pc. I did not get any result by calling function plugin_setting() my code to test calling plugin (test.pl) and plugin code (MyTest.pm) is written below: -------------------------------------------------------------------------------------------------- #test.pl use Dancer2; use lib "../lib/"; use Dancer2::Plugin::MyTest; get '/mytest' => sub { mytest('I am Testing') }; dance(); ---------------------------------------------------------------------------------------------------- #MyTest.pm package Dancer2::Plugin::MyTest; use Dancer2::Plugin; register mytest => sub { my ($dsl, @args) = plugin_args(@_); my $conf = plugin_setting(); use Data::Dumper; return Dumper($conf); }; register_plugin for_versions => [ 2 ] ; 1; ----------------------------------------------------------------------------------------------------------------------------------- I added following code to config.yml ----------------------------------------------------------------------------------------------------------------------------------- #config.yml plugins: "Dancer2::Plugin::MyTest": key: value ----------------------------------------------------------------------------------------------------------------------------------- Output of my code which is also output of function plugin_setting() is empty as follow: $VAR1 = {}; I changed config.yml as follow but output is empty again ----------------------------------------------------------------------------------------------------------------------------------- #config.yml plugins: "MyTest: key: value ----------------------------------------------------------------------------------------------------------------------------------- How should I customize config.yml file to be able to see output and what is aim of function plugin_setting()? Kadir Beyazlı GSM : +90 535 821 50 00

2 3

Dancer1 v1.3139 (TRIAL) on its way to CPAN
by Yanick Champoux 25 Jun '15

25 Jun '15

Hi all, A new trial version of Dancer1 is on its way to CPAN. For this release, we're reverting two patches that proved to cause problems: the loading of configuration via a hash, and the caching of the session for the request lifecycle. (the changelog with the ticket numbers is included below) If nothing catch fire within 7 days, the release will be promoted to non-trial. As usual, a big thank to everybody who was involved in this release. Y'all rock. :-) Joy, `/anick 1.3139 2015-06-25 [ BUG FIXES ] - Reverted caching of session, as it can cause problem when the user is using 'session->destroy' (GH#1120). - Reverted loading config from hash. (GH#1121) [ STATISTICS ] - code churn: 9 files changed, 55 insertions(+), 249 deletions(-)

1 0

PR 1113 (Dancer 1.3137) spams log files in unhelpful places
by Sam Kington 22 Jun '15

22 Jun '15

Hi, Delurking, because the latest version of Dancer is causing our unit tests at $WORK to start creating empty log files inside the current working directory. This is easily-reproducible: e.g. > sam@chimera64:tmp$ cat spamlogfile.pl > #!/usr/bin/env perl > > use Dancer qw(halt); > sam@chimera64:tmp$ rm -fr logs; perl spamlogfile.pl > sam@chimera64:tmp$ ls -lah logs/ > total 40K > drwxr-xr-x 2 sam sam 4.0K Jun 22 17:01 . > drwxrwxrwt 10 root root 36K Jun 22 17:01 .. > -rw-r--r-- 1 sam sam 0 Jun 22 17:01 development.log A workaround is to say use Dancer qw(:syntax), but there are two problems with that: (1) this is a change in behaviour that wasn’t documented as such, and it requires all auxiliary non-server Dancer code to be changed; and (2) passing :syntax imports all sorts of Dancer symbols that can potentially clash with a parent class. I’ve spent the afternoon debugging point 2. Our end-to-end tests run under Test::Dancer, and we have a separate class that tests individual method calls as if they were Dancer requests (including setting the status code in case of errors). It previously said use Dancer () and explicitly called Dancer::status - and under Dancer 1.3138, running unit tests using this class would generate spurious empty log files. I patched that to say use Dancer qw(:syntax) - and now the code fails because the parent class implements methods true, false and redirect, which the method call class never gets to call because it’s had Dancer’s symbols stuck in its own package instead. So this now needs to say use Dancer qw(:syntax !true !false !redirect), and in practice I needed to write an automated test script that checked that all of a parent class’s methods were explicitly not imported from Dancer, because if I change anything upstream I need to change the import statement in the child classes. The problem appears to have been introduced in https://github.com/PerlDancer/Dancer/commit/e9e4e087528c2734dd6e9c922105eac… The actual problem is further down in Dancer::Config - line 227 in 1.3138 - where the settings are read. $SETTINGS at this point contains default values, and part of setting confdir involves creating a logs subdirectory. Previously the code wouldn’t get this far. Presumably a workaround would be to not create a log directory immediately, but then if you were running a real Dancer server you’d want to know as soon as possible that your log directory wasn’t writable, so that’s not going to be acceptable to many people. Alternatively, any code that says e.g. use Dancer qw(halt status) should be seen as clearly not wanting to actually start a Dancer server or anything like that. That sounds like a scary change to make, though. Or you could defer parsing of the Dancer config until something actually happens. That’s also vague and terrifying. Or just revert that particular commit / PR. I don’t fully understand why it does what it does, though. If there’s a way of cleanly telling apart (1) a hash of settings that was explicitly passed to Dancer from (2) the default settings that, chances are, you didn’t intend to use, that would be the best solution to my mind. Sam -- Website: http://www.illuminated.co.uk/

2 2

Re: [dancer-users] X-Sendfile
by Zahir Lalani 22 Jun '15

22 Jun '15

Sorry my bad - silly typo! From: Zahir Lalani Sent: 22 June 2015 17:10 To: Perl Dancer users mailing list Subject: X-Sendfile Hi All I have my image gallery working using send_file. But I am now trying to use X_Sendfile in apache to deal with image delivery. The code for send_file is replaced with: # use x-send header('Content-Type' => $mime); header("X-Sendfile: $file"); but I get the following error: Illegal field name 'X-Sendfile: /mnt/assets/1/56/8f/568f1a76-9e17-4027-8556-ed19155708c3/800.jpg' at (eval 384) line 17. The x-send module is enabled - not sure if this is a dancer issue or an apache one? Thx Zahir Lalani Head of Development & Architecture [cid:96F784CA-E917-4CC1-A9A9-96CBDA2AF2BC] 2 Tabernacle Street, London, EC2A 4LU m: +44 (0)7956 455168 e: zahirlalani(a)oliver-marketing.com<mailto:zahirlalani@oliver-marketing.com> w: www.oliver-marketing.com<http://www.oliver-marketing.com/>

1 0

X-Sendfile
by Zahir Lalani 22 Jun '15

22 Jun '15

Hi All I have my image gallery working using send_file. But I am now trying to use X_Sendfile in apache to deal with image delivery. The code for send_file is replaced with: # use x-send header('Content-Type' => $mime); header("X-Sendfile: $file"); but I get the following error: Illegal field name 'X-Sendfile: /mnt/assets/1/56/8f/568f1a76-9e17-4027-8556-ed19155708c3/800.jpg' at (eval 384) line 17. The x-send module is enabled - not sure if this is a dancer issue or an apache one? Thx Zahir Lalani Head of Development & Architecture [cid:96F784CA-E917-4CC1-A9A9-96CBDA2AF2BC] 2 Tabernacle Street, London, EC2A 4LU m: +44 (0)7956 455168 e: zahirlalani(a)oliver-marketing.com<mailto:zahirlalani@oliver-marketing.com> w: www.oliver-marketing.com<http://www.oliver-marketing.com/>

1 0