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

production.yml & development.yml
by Wanjuan Yang 04 Jul '16

04 Jul '16

Hi, There are 2 environment config file in the dancer web framework. Where to set which environment file( development.ml or production.yml) is used? Many thanks, Wendy

3 9

DancerCon 2016 Sponsorship
by Sam Batschelet 02 Jul '16

02 Jul '16

Greetings Dancer Enthusiast, We are closing in fast on the 2016 Perl Dancer Conference (DancerCon) held this year in Vienna, Austria September 20 - 22. Sponsoring DancerCon is an opportunity to present your company or association to an international audience of Perl, Dancer and DBIx:Class related developers and business owners. We have a great cast of speakers ( https://www.perl.dance/speakers ) from the #dancer community this year including core developers Sawyer X, Stefan Hornburg (racke), Mickey Nasriachi (mickey), Jason Crome (chromosome) and Peter Mottram (SysPete). 2016 has already been a very exciting year for Dancer. This May, Dancer2 0.200000 brought us the long awaited updates to the Dancer2 plugin architecture. A lot of the momentum for this release was the result of last years conference and the continued hard work of many. If your company uses Dancer or is considering it in the future please take a moment and look over our sponsorship page for ideas. Alternatively contact us directly at 2016(a)perl.dance and we can come up with a custom package for you. Thank You, Sam Batschelet 2016 Perl Dancer Conference http://perl.dance | 2016(a)perl.dance Powered By Dancer2!

3 3

Dancer2 0.200000 is finally out!
by Sawyer X 02 Jun '16

02 Jun '16

The long awaited new version of Dancer2 <https://metacpan.org/pod/Dancer2> is finally on its way to CPAN mirror near you! Why did it take so long, what's changed, and why the big bump in version? In short: A new plugin system, reworked from scratch, that is still (mostly) backwards compatible. *The plugin system* One of the sore points left in Dancer2 is its plugin architecture. The idea was to have an easy, comfortable plugin system (similar to Dancer 1) but much smarter. Unfortunately while the idea was there, and some of the code was there, the goals were not fully achieved, due to tuit shortage. This led to various problems with plugins, most notably, using plugins within other plugins. This was beyond frustrating for several plugin developers. The current system was simply insufficient. We decided to finally tackle this. I have an entire story about that, but I'll leave it for another time. The new plugin system provides each plugin with its own instance, full Moo <https://metacpan.org/pod/Moo> classes (use attributes, roles, other plugins, whatever you want), full access to the internal objects (which, as a plugin developer, you might as well use), and cleanly decouples it from the user namespace. Despite it being object oriented, we still carefully try and handle the old keyword-based interface that the previous plugin system used. In places where it was not possible, we contacted the module authors, and provided pull requests to implement the new parts. We even collected statistics on which modules are supported, whether we submitted a PR, whether it was merged, and whether a new release was made. You can see this here <https://github.com/PerlDancer/Dancer2/issues/1078>. The compatibility layer was incredibly involved and tasking and took several good developers, and myself, to get it done. Damien Krotkine (dams) even came back from semi-retirement just to help remove AUTOLOAD usage. He was missed. :) Peter Mottram has worked tirelessly to get everything running as smooth as possible. He tracked everything, debugged, tested, submitted PRs, contacted and worked with authors, and basically did the work of about 20 people at once. *New core plugin* A beautiful gem that was a result of the second Dancer Conference ( DancerConf <http://perl.dance/>), Dancer2::Plugin::SendAs <https://metacpan.org/pod/Dancer2::Plugin::SendAs> is now in core! Most people do not know about it. It allows you to override the serializer (or the lack thereof) per response. Well, that's not really true. The truth is that we introduced a stronger version of it with more features! *New keywords* The original keyword spec for Dancer <https://metacpan.org/pod/Dancer> and Dancer2 <https://metacpan.org/pod/Dancer2> included header and push_header. This is only for response, not request. We now introduced variations explicitly for request and response, namely request_header and response_header (and more). *Megasplat fix* We fixed a problem with Megasplat, reported by Miyagawa-san. *Plack support* We support new Plack <https://metacpan.org/pod/Plack> versions, a breakage that we marked as a mandatory high-priority issue. *A bit faster* We've internally moved to Type::Tiny <https://metacpan.org/pod/Type::Tiny> which will automatically load Type::Tiny::XS <https://metacpan.org/pod/Type::Tiny::XS>, making your program faster. We also moved from Class::Load <https://metacpan.org/pod/Class::Load> to Module::Runtime <https://metacpan.org/pod/Module::Refresh> to both reduce dependencies and speed up the framework. There had been quite a few more improvements and we would like to thank everyone who helped make this release such a great one. You can view all the changes in the Changes <https://metacpan.org/changes/distribution/Dancer2> log. *Onwards* Now that we got the new plugin architecture out of the way, we can start concentrating on additional improvements and interesting changes. We will introduce a completely reworked documentation, named routes (or route aliases), and maybe a rainbow-colored pony which sneezes sunshine. With much love, The Dancer Core Team.

10 10

Mig Dancer 1 to 2: set confdir does not work?
by Jochen Schnuerle 25 May '16

25 May '16

Hello, I have created a webportal for my server installation and configuration functions with Dancer1. Now I want to add ldap user support and I think this is the opportunity to migrate to Dancer2. First I created a webapp with dancer2 gen -a "fsi" -p /opt/test/ After that I move the environment and config yml files to the etc dir and delete the environments dir. I want a clean root dir and so I move the rest of the files to the new doc dir. [root@fsisrv6 fsi]# pwd /opt/test/fsi [root@fsisrv6 fsi]# tree . ??? bin ? ??? app.psgi ??? doc ? ??? cpanfile ? ??? Makefile.PL ? ??? MANIFEST ? ??? MANIFEST.SKIP ??? etc ? ??? config.yml ? ??? development.yml ? ??? production.yml ??? lib ? ??? fsi.pm ??? public ? ??? 404.html ? ??? 500.html ? ??? css ? ? ??? error.css ? ? ??? style.css ? ??? dispatch.cgi ? ??? dispatch.fcgi ? ??? favicon.ico ? ??? images ? ? ??? perldancer-bg.jpg ? ? ??? perldancer.jpg ? ??? javascripts ? ??? jquery.js ??? t ? ??? 001_base.t ? ??? 002_index_route.t ??? views ??? index.tt ??? layouts ??? main.tt From my Dancer1 project, I copy the three set lines to the fsi.pm file: - - --- -- --- -- - ---- package fsi; use Dancer2; set confdir => "/opt/test/fsi/etc"; set envdir => "/opt/test/fsi/etc"; set environment => 'development'; our $VERSION = '0.1'; get '/' => sub { template 'index'; }; true; - - --- -- --- -- - ---- If I now start the portal with plackup -s Starman --workers=10 -a /opt/test/fsi/bin/app.psgi -p 3000 I see in the "Your application's environment" section: Location: /opt/test/fsi Template engine: <% settings.template %> Logger: <% settings.logger %> Environment: <% settings.environment %> So I think Dancer2 cannot find the config.yml file. I read that I must create a .dancer file in the etc dir: [root@fsisrv6 etc]# ls -lisa insgesamt 20 5376363 4 drwxr-xr-x 2 root root 4096 19. Mai 07:52 . 5376297 4 drwxr-xr-x 9 root root 4096 19. Mai 07:51 .. 5376359 4 -rw-r--r-- 1 root root 1414 19. Mai 07:52 config.yml 5376327 0 -rw-r--r-- 1 root root 0 19. Mai 07:49 .dancer 5376361 4 -rw-r--r-- 1 root root 727 19. Mai 07:49 development.yml 5376352 4 -rw-r--r-- 1 root root 302 19. Mai 07:49 production.yml But that does not work. What am I doing wrong? Who can help, please? Thank you & Regards Jochen PS: env infos: - CentOS 6 and 7 - Dancer2 0.166001

3 6

Mig Dancer 1 to 2: session YAML - id not in file
by Jochen Schnuerle 24 May '16

24 May '16

Hello, I use session engine YAML for my webapp ... in Dancer1 the session file contains: ------------------------------------------------------------------ --- !!perl/hash:Dancer::Session::YAML id: 168717572663644210774823307966216571 last: 2016.05.13-21:13:37 logged_in: 1 logintime: 2016.05.13-14:03:57 role: Master user: fsi ------------------------------------------------------------------ In Dancer2 the content of the session file is: ------------------------------------------------------------------ --- last: 2016.05.24-10:09:09 logged_in: 1 logintime: 2016.05.24-08:52:31 role: Master user: fsi ------------------------------------------------------------------ I missed the id: line - but I do not know how the id come in the file. On the website for SessionFactory.pm (http://search.cpan.org/~xsawyerx/Dancer2-0.165000/lib/Dancer2/Core/Role/Ses…) I have read, that there is a method generate_id. But I do not know how to use it or how I can use the retrieve method to get the id to write into the YAML session file. Will someone please explain? Thank you / Regards Jochen

2 1

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