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

Dancer2 panels for Plack::Debugger
by Peter Mottram 26 Apr '16

26 Apr '16

As I slowly drag myself away from Dancer1 towards Dancer2 I've found myself missing my much-loved Dancer::Debug panels and so have started working on a set of panels using Plack::Debugger. Before I get lost down too many rabbit holes I thought I'd share my current plan with the wider community to see how others might want to see things and to ask for thoughts on where I might already be going wrong. My approach for collecting D2 data (tokens, routes, etc) is by creating Dancer2::Plugin::Debugger which can then use hooks, etc and stash collected data via Cache::Mmap (probably serialsed using JSON) to be picked up by Plack::Debugger panels in 'after' callbacks. The plugin must be specifically enabled in config so importing is effectively a noop if config is not enabled. On the Dancer2 plugin side any collector class would be created under the Dancer2::Plugin::Debugger::Panel namespace with a corresponding class created under Plack::Debugger::Panel::Dancer2 so for example Dancer2::Plugin::Debugger::Panel::TemplateTokens would have a corresponding Plack::Debugger::Panel::Dancer2::TemplateTokens. I'm also planning to have Dancer2::Debugger which is a Dancer2 app which sets up the Plack::Debugger side of things to make setup in the psgi file as simple as possible keeping configuration shared between the two parts in D2 config files. The current plan allows for new panels to be released as individual distros which provide the plugin panel and the debugger panel classes. So before I wade in too deep does anyone have any suggestions, issues, ...? Cheers SysPete

2 2

2016 Perl::Dancer Conference - Announcement
by Sam Batschelet 13 Apr '16

13 Apr '16

Fellow Dancers, Each year we bring together an international band of Perl loving misfits for a few days of hacking and community fun. The Perl::Dancer conference is a unique opportunity to leave the terminal and get hands on with #dancer. Take a training course, learn new and exciting ways people are using Dancer. Network with fellow developers and possibly even land your dream job. We are very excited to announce that this year’s conference will once again be held in the beautiful city of Vienna, Austria on September 21st - 22nd. In addition we are planning a full day of training Tuesday, September 20th. The conference is currently taking submissions on training topics, we would love to hear your ideas. In order for the conference's success, WE NEED YOUR HELP! Have you wanted to become more involved with the Dancer community, but didn’t know how? This is your chance, become a part of Team PDC today! We have a wide range of tasks available for any skill set, perfect for using up those extra cycles. Tasks include, helping program the conference website, assistance with scheduling, submitting and reviewing talks, writing marketing material for spreading the word, organizing equipment, brainstorming on activities and more. Everyone who helps out this year will get a super cool limited edition "Team Dancer” t-shirt and sticker to show off your support. How do you get involved? Simply send us an email at 2016(a)perl.dance or chime in on #dancer. We look forward to hearing from you! Warm Regards, Sam Batschelet (hexfusion) Perl::Dancer conference Share, collaborate and dream https://www.perl.dance | 2016(a)perl.dance https://www.facebook.com/Perl-Dancer-Conference-670529456366338/

1 0

[RFC] Rewritten documentation
by Sawyer X 08 Apr '16

08 Apr '16

Hey fellow hackers! TL;DR; I rewrote the documentation and would be happy for comments. Following is an explanation. If you're short on time, here's the PR link: https://github.com/PerlDancer/Dancer2/pull/1069 It might be easier to view only the docs themselves, available here: https://github.com/PerlDancer/Dancer2/blob/docs/from-scratch/lib/Dancer2.pm… Long version: Documentation is hard. You probably know this. It's difficult to convey both how something works and how to use it. When working on a framework, we often find ourselves explaining where it fits in and how, and what is the problem the framework solves. In our context this might explain the HTTP protocol, how to implement a web service, or how to deploy an existing application or merge your new application within existing code. A while ago, following conversations on the topic, I decided to take a stab at rewriting the entire documentation. My goals were simpe (and daring): * Explain what Dancer2 does * Explain how Dancer2 is composed * Explain how to set it up, configure it, and use it * Cover all the important keywords I had made the following assumptions: * I focus on best practices * I do not cover at length what I don't think should be done (call it "bad practices") * I provide follow-up links (or at least try) where I prefer not to go into detail * I do not explain how HTTP works or how web applications work I would be grateful for any review of this work you can provide before we merge it as the new official documentation. Here are some leading questions to help you think through this: * Is this documentation too long? * Is this documentation not enough? * Does it explain things the documentation usually does not? * Do you think you understand more of how Dancer2 works now? * Does this clarify parts that were unclear before? * Any big pieces missing? You can reply on the list or directly to me. * The link to the Pull Request: https://github.com/PerlDancer/Dancer2/pull/1069 * The link to the documentation directly: https://github.com/PerlDancer/Dancer2/blob/docs/from-scratch/lib/Dancer2.pm… Thank you ever so much. :) Sawyer.

2 5

ajax route error
by Zahir Lalani 05 Apr '16

05 Apr '16

Hi All We are experiencing loss of CSS style under certain circumstances and have to completely restart starman to cure. We traced this to the ajax processing and found this issues logged: https://github.com/PerlDancer/Dancer2-Plugin-Ajax/issues/1 Has anyone seen this issue before? Zahir Lalani Head of Development & Architecture [cid:96F784CA-E917-4CC1-A9A9-96CBDA2AF2BC] 2 Tabernacle Street, London, EC2A 4LU m: +44 (0)7956 455168 t: +44 (0)203 142 3619 e: zahirlalani(a)oliver-marketing.com<mailto:zahirlalani@oliver-marketing.com> w: www.oliver-marketing.com<http://www.oliver-marketing.com/>

2 2

Dancer on Pulsar
by Zahir Lalani 05 Apr '16

05 Apr '16

I still do some work for an engineering company that builds studio equipment for broadcast. The majority of development has been on custom OS's or raw hardware. They have now bought a MicroZed board (http://microzed.org/) which runs WindRiver Pulsar Linux. I was asked to test it out for a number of requirements, one of which was to create an API/Web interface to control their equipment. Of course "web app" meant I had to try and see if Dancer would work. It absolutely did and worked pretty well considering the limited resources of the board. Zahir Lalani Head of Development & Architecture [cid:96F784CA-E917-4CC1-A9A9-96CBDA2AF2BC] 2 Tabernacle Street, London, EC2A 4LU m: +44 (0)7956 455168 t: +44 (0)203 142 3619 e: zahirlalani(a)oliver-marketing.com<mailto:zahirlalani@oliver-marketing.com> w: www.oliver-marketing.com<http://www.oliver-marketing.com/>

1 0

Dancer2 session file not being created.
by vijayvithal jahagirdar 04 Apr '16

04 Apr '16

0down votefavorite <http://stackoverflow.com/questions/36377451/dancer2-session-not-written-to-…> In my Dancer2 app I find that the session information is not stored in between file request. I am using YAML as my session store format. e.g. I have defined a test route to set a variable in the session and dump the settings and session variable in the template using Data Dumper in the template. get '/test/:key/:value' => sub { my $key =params->{key}; my $value =params ->{value}; session($key=>$value); template 'test';}; The result of Data Dumper is $VAR1 = {'engines' => {'template' => {'template_toolkit' => {'start_tag' => '<%','end_tag' => '%>'}},'session' => {'YAML' => {'cookie_name' => 'domain.session','is_secure' => '1','is_http_only' => '1','session_dir' => '/tmp/dancer-sessions/'}}}, And session var is $VAR1 = {'a' => 1}; At this point I expect my /tmp directory to contain a session folder but I see the following starman@ubuntu:~/www/app$ ls -al /tmp total 776 drwxrwxrwt 2 root root 4096 Apr 2 14:39 . drwxr-xr-x 21 root root 4096 Apr 2 07:31 ..-rw-r--r-- 1 starman starman 776737 Apr 2 14:31 starman.err-rw-r--r-- 1 starman starman 0 Apr 2 07:31 starman.out-rw-r--r-- 1 starman starman 4 Apr 2 14:31 starman.pid I am unable to figure out why the session file is not getting created. Any pointers on my mistake will be helpful My test.tt is as follows <%USE Dumper%><h1> Dumping the settings variable </h1> <%Dumper.dump_html(settings)%> <h1> Dumping the session variable </h1><%Dumper.dump_html(session)%> The live url for this route is Live URL <http://edaindia.com/test/var/bar> Note: I am launching 2 separate domain using a common app.psgi file whose content is as follows use Plack::Builder; use Dancer2 ':syntax'; use lib '/home/starman/www/dyumnin/lib'; use lib '/home/starman/www/edaindia/lib'; use dyumnin; use edaindia; builder { mount 'http://edaindia.com/' => edaindia->to_app; mount 'http://dyumnin.com/' => dyumnin->to_app; }; -- https://www.facebook.com/vijayvithal.jahagirdar https://twitter.com/jahagirdar_vs http://democracies-janitor.blogspot.in/

2 1