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

Is it necessary to "use Plugin" in every module where I want to use the plugin's new keywords?
by Punter 04 Mar '13

04 Mar '13

Couldn't we make it so, that if you include the plugin in config.yml, then you get its keywords everywhere where we just "use Dancer"? Please? Code would then be a lot cleaner and shorter.

4 3

Erroneous session-cookie setting behaviour in Dancer2
by Punter 04 Mar '13

04 Mar '13

I created my own D2::Session::* class. I set session to something, with: session greeting => 'hello'; Now whenever I do a page any view, I get a "this website wants to set a cookie" message It shouldn't be like that. If cookie values don't change, then they should only be set once.

5 17

Plackup + Starman reloading issues
by James Baer 03 Mar '13

03 Mar '13

Hi all, Not sure if I'm missing something but I recently wanted to try switching from Apache to Nginx + Starman to serve a Dancer app. I'm having an issue reloading Starman after I make changes to my code, in that my changes are not picked up after I send a SIGHUP to the Starman master. I'm starting my app like so: plackup -E development -s Starman --workers=1 -p 3000 -a bin/app.pl -D Then after I make some changes I send a kill -1 or -HUP to the Starman master work pid.My changes are then not being picked up by the new starman worker. So far the only way I have been able to reload my changes is to manually kill both master and all workers, then reissue the plackup command. I have also tried using the plackup --Reload option, with no luck either. I'm running Starman-0.3006. Am I doing something wrong? Is this a known issue? Thanks for any help.

1 0

How do I mount a Dancer2 app tree with Plack::Builder?
by Punter 02 Mar '13

02 Mar '13

I followed this tutorial http://advent.perldancer.org/2012/7 and built a very small but structured Dancer2 application. Now I would like to mount it as a PSGI application with Plack::Builder. What do I have to do? This here app.psgi configuration definitely doesn't work: https://metacpan.org/module/SUKRIA/Dancer2-0.02/lib/Dancer2/Deployment.pod#… (it was probably built for Dancer1) Thank you

2 3

Re: [dancer-users] How do I mount a Dancer2 app tree with Plack::Builder?
by Peter Corrigan 01 Mar '13

01 Mar '13

Thank you for the replies Rik and Curtis. Hope this is not noise for this list. So it works akin to CGI under Apache in that while the httpd server may be bound to multiple ports, our app will only get traffic from a specific port. Of course, unlike CGI our app is not invoked anew for each request. The localisation we get with Dancer2 extends to variables within the Dancer applications environment. The http port is set further down the stack and not reachable by the app. Peter On 1 March 2013 14:53, Curtis Jewell <perl(a)curtisjewell.name> wrote: > Specifically, you have two apps that are entry points into the same > codebase/external storage. > > I would ask how much you could extract out into code that does not rely > on Dancer at all (database queries, etc.), and then the two apps > themselves can be smaller, but call into common code. > > --Curtis > > On Fri, Mar 1, 2013, at 6:53, Rik Brown wrote: > > Sounds like you really have two apps there, not one :) > > > > Rik > > > > > > On 1 March 2013 10:06, Peter Corrigan <peter.corrigan(a)nuigalway.ie> > > wrote: > > > > > So can/will a single scoped Dancer2 app listen on multiple http ports > > > with specific routes per port e.g. /search on 80 and /admin on 9000? > > > Peter > > > > > > > On 1 March 2013 08:25, Alexis Sukrieh <sukria(a)gmail.com> wrote: > > > > Nice catch, will look into that. > > > > > > > > Thanks > > > > > > > > -- > > > > Alexis, on the road > > > > > > > > Le 1 mars 2013 à 04:58, Punter <punter(a)punter.gr> a écrit : > > > > > > > >> I followed this tutorial http://advent.perldancer.org/2012/7 and > built > > > a very small but structured Dancer2 application. > > > >> > > > >> Now I would like to mount it as a PSGI application with > Plack::Builder. > > > What do I have to do? > > > >> > > > >> This here app.psgi configuration definitely doesn't work: > > > > https://metacpan.org/module/SUKRIA/Dancer2-0.02/lib/Dancer2/Deployment.pod#… probably built for Dancer1) > > > >> > > > >> Thank you > > > >> _______________________________________________ > > > >> dancer-users mailing list > > > >> dancer-users(a)dancer.pm > > > >> http://lists.preshweb.co.uk/mailman/listinfo/dancer-users > > > >> > > > > _______________________________________________ > > > > dancer-users mailing list > > > > dancer-users(a)dancer.pm > > > > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users > > > _______________________________________________ > > > dancer-users mailing list > > > dancer-users(a)dancer.pm > > > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users > > > > > _______________________________________________ > > dancer-users mailing list > > dancer-users(a)dancer.pm > > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users > -- > Curtis Jewell > csjewell(a)cpan.org http://csjewell.dreamwidth.org/ > perl(a)csjewell.fastmail.us http://csjewell.comyr.org/perl/ > > "Your random numbers are not that random" -- perl-5.10.1.tar.gz/util.c > > Strawberry Perl for Windows betas: http://strawberryperl.com/beta/ > > _______________________________________________ > dancer-users mailing list > dancer-users(a)dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users >

1 0

Re: [dancer-users] How do I mount a Dancer2 app tree with Plack::Builder?
by Peter Corrigan 01 Mar '13

01 Mar '13

So can/will a single scoped Dancer2 app listen on multiple http ports with specific routes per port e.g. /search on 80 and /admin on 9000? Peter Peter Corrigan, Head of Organisational Development & Performance, James Hardiman Library, National University of Ireland, Galway. Tel +353-87-2798505 peter.corrigan(a)nuigalway.ie On 1 March 2013 08:25, Alexis Sukrieh <sukria(a)gmail.com> wrote: > Nice catch, will look into that. > > Thanks > > -- > Alexis, on the road > > Le 1 mars 2013 à 04:58, Punter <punter(a)punter.gr> a écrit : > >> I followed this tutorial http://advent.perldancer.org/2012/7 and built a very small but structured Dancer2 application. >> >> Now I would like to mount it as a PSGI application with Plack::Builder. What do I have to do? >> >> This here app.psgi configuration definitely doesn't work: https://metacpan.org/module/SUKRIA/Dancer2-0.02/lib/Dancer2/Deployment.pod#… (it was probably built for Dancer1) >> >> Thank you >> _______________________________________________ >> dancer-users mailing list >> dancer-users(a)dancer.pm >> http://lists.preshweb.co.uk/mailman/listinfo/dancer-users >> > _______________________________________________ > dancer-users mailing list > dancer-users(a)dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users

3 2

CGI must DIE! .... or Dancer::Plugin::FakeCGI
by igor.bujna＠post.cz 26 Feb '13

26 Feb '13

Hi, first i want thanks to Sawyer X about his good presentation on YAPC about CGI must DIE! I find only this video http://www.youtube.com/watch?v=tu6_3 fZbWYw. I have couple of project which use CGI.pm. I thinking about how can i simply rewrite this to any MVC framework. Couple of years ago, ther isn;t exist any usable MVC framework and every of us use CGI or other similar functions for creating HTML pages. How SawyerX said, CGI must die. Because working on big project writed on CGI, than one time you will have to much problem to keep consistence of programs. Before couple years ago i must writed one CRM project in Perl and try to find which frameworkt can use for this. I play with CGI::Application, Gantry, Jifty, Mojo, Catalyst. Winner of this was Catalyst, but next i finded newer project - Dancer :) and try to made this project atop Dancer. For me Dancer was and for now is winner as Perl web framework. Because is small, simpliest and made everything what i need. Catalyst is powerfull but bigger. Now when i thinking how move my CGI projects to Dancer i finded couple of solutions( Catalyst::Controller::CGIBin, HTTP::Request::AsCGI, CGI::PSGI, CGI:: Emulate::PSGI) but none of this make everything what i need. Than i make Dancer::Plugin:: FakeCGI. http://search.cpan.org/~koceasy/Dancer-Plugin-FakeCGI-0.60/lib/ Dancer/Plugin/FakeCGI.pm This plugin made emulation of Mod_PERL for now in version 1. I choose this, because any of us which use CGI.pm we had to use a mod_perl funcionalities to make better programs runned atop CGI.pm. You look on examples directories and run bin/app.pl from this. When you have bigger project writed atop CGI.pm than you have big problem to rewriting this to anythink else. Rewriting use yours time, which can you spend to extended funcionalities. It can look like this: Web--->INPUT-->CGI project do something--->HTML contentt I try to emulated mod_perl behavior in Dancer::Plugin::FakeCGI. First emulated input parametters under mod-Perl and second is capture everything what CGI project print to STDOUT. If i hade this than can be simple make any changes or funcionalities in this CGI. For this i use mocking and this package http://search.cpan.org/~sukria/Test-TinyMocker-0.03/lib/Test/ TinyMocker.pm(I send simply patch to Alexis Sukrieh to extend his package to method mocked, which can return original mocked method, but he dosn't answer on my email)(http://search.cpan.org/%7Esukria/) Now if i have this functionalities, than i have simplies change fincionalities in CGI project. I can mocked any function and if CGI project run this function than i return what i need, simply example is /test_6 under examples directories or this example: sub test_file { my ($cgi_bin, $cgi, $url, $is_perl) = @_; return 1 if ($cgi =~ /^\./); # skip serving this file https://email. seznam.cz/#compose/30576 return 1 if ($cgi =~ /test.pl/); # skip serving this file if ($cgi eq "index.pl") { # own serving for given file any $url => sub { redirect "/index.sh"; }; return 1; } return 0; # default serving file } fake_cgi_bin(\&test_file, ["*.pl", "*.sh"], 1); # Read every files *.sh or *.pl and try to serve automaticaly if method test _file() return 0; There is couple of problem when use this plugin: 1) in CGI can't be any infinity loop such us CGI::Push.pm or other, because i use capturing STDOUT and after CGI program exited than i server this captured informations-HTML pages to client 2) Problem with fork|system() function under HTTP::Server::Simple - This server make bad openening file descriptor of STDOUT on child pid and open STDOUT as STDERR of parent pid. Solution for this is use plackup 3) better solution for capturing STDOUT under system call when is set capture to memory. 4) Don't use dancer under mod_perl in apache. because I emulated mod_perl funcionalities. Solution for this is use Apache as proxy and serving connection to plackup server. 5) Serving file is about 20-50% slowest than under Mod_perl when use Registry.pm, because CGI::Compile behaviour is as PerlRun.pm. Now i worked on similar behavior as Registry.pm. 6) memory usage us bigger than on mod_perl - solution for this is buy more memory :D My reasons is this will be good for simple migration from CGI to Dancer. Now you can simply run any CGI project under Dancer and make simple refactoring of this code. Bye Igor

1 0

Re: [dancer-users] Configuring Plack::Middleware::Expires
by Gurunandan Bhat 19 Feb '13

19 Feb '13

Sorry - I found my error - the second parameter in the options list must be 'content_type' not 'content-type' Thanks On Mon, Feb 18, 2013 at 7:28 PM, Gurunandan Bhat <bhat.gurunandan(a)gmail.com>wrote: > Hi, > > I am trying to configure Plack::Middleware::Expires and Deflater to add an > expires header and gzip with the following in my config.yml: > > plack_middlewares: > - > - Expires > - content-type > - > - image/gif > - image/jpeg > - expires > - access plus 1 day > - > - Deflater > > I find that while the Deflater middleware works correctly, the Expires > does not. Is there an error in my YAML syntax? I tried to parse the YAML > separately and I seem to get the correct options that Expires expects. > > Would appreciate your help, > > Thank you. > > >

1 0

Dancer 1 and Dancer 2, what we're going to do
by Alexis Sukrieh 18 Feb '13

18 Feb '13

http://www.sukria.net/fr/archives/2013/02/18/dancer-1-and-dancer-2-what-wer… Fellow Perl hackers, you who like to “dance“, read the following carefully for I have some interesting news for you. You probably know that we’ve frozen Dancer 1 development some time ago, when we decided to focus all the energy on Dancer 2. That was done with an idea in mind: get the most possible out of the D2 prototype. We had also the idea that D2 will at some point be able to replace D1. Entirely. It was a mistake. Actually a mistake that will lead to something that I believe is rather very good for the Dancer community, let me explain. Dancer 2 is a success on many fields: it’s entirely written with Moo, so it has a complete OO layer. The core encapsulates each app in a proper instance, ensuring no more app collisions will occur. All the non-deprecated keywords of the DSL provided by Dancer 1 are supported in Dancer 2. Some components are even better in D2 (look at the awesome session handling for instance) and the Moo layer behind the scene allows many great things for the future. Plugins can be migrated quite easily to support D1 and D2 at the same time. But there is one thing that won’t be possible: support engines in D1 and in D2 transparently. The reason is rather technical: in D1, an engine (logger, template, session) is a class that should be extended (in pure Perl 5 code). In D2, it’s a role that should be composed. Of course, the design is more rigid, and many things need to be changed for an engine to work under D2. The question was: should we spend energy on trying to support both? Should we provide a wrapper to allow easy migration? The consensus is no. We’ll do something else. There is out there a lot of real-life D1 applications. Most of them use engines that won’t work transparently under D2. Also the app-scoping can break things with some applications, if the app is decoupled in many packages. For that reason, I’m going to release Dancer 2 in its own namespace, and that will bring a lot of energy in both projects: Dancer 1 is at the same time unfrozen, development can continue there (as long as the features added are not something that would lead to a new Dancer 2!) Dancer 2 is released on CPAN and its ecosystem can rise Dancer 1 users are happy Dancer 2 users are happy Migrating an app becomes something under control. So, be prepared to see Dancer2 on CPAN pretty soon :) And by the way, we’ll choose a Dancer 1 maintainer, because I won’t have the time to handle both projects. Stay tuned! Cheers, Alexis.

3 5

Configuring Plack::Middleware::Expires
by Gurunandan Bhat 18 Feb '13

18 Feb '13

Hi, I am trying to configure Plack::Middleware::Expires and Deflater to add an expires header and gzip with the following in my config.yml: plack_middlewares: - - Expires - content-type - - image/gif - image/jpeg - expires - access plus 1 day - - Deflater I find that while the Deflater middleware works correctly, the Expires does not. Is there an error in my YAML syntax? I tried to parse the YAML separately and I seem to get the correct options that Expires expects. Would appreciate your help, Thank you.

1 0