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

dancer2's prototype is there, feedback needed
by sukria 05 Oct '12

05 Oct '12

Hi there, I am very glad and proud to announce here that I've came up with a prototype of dancer2 that pleases me enough to be advertised. -*- https://github.com/sukria/dancer2 -*- dancer2 is a complete rewrite of Dancer aiming at providing the same awesomeness with the following major changes: - no more globals in the core - 100% object-oriented backend (based on Moo) - better scoping for sub-applications - better design (no more encapsulation violations, Law of Demeter, ...) The prototype I've pushed to GitHub currently covers ~80% of the DSL of Dancer. It's able to run simple applications (it can run the PerlDancer.org website for instance). Of course, with your real-life applications, it will break in many places in this current shape, and this is where you can help. I'd like to have as many reports as possible regarding upgrades tests. You can test very easily your app with dancer2: $ git clone http://github.com/sukria/dancer2.git $ cd YOUR_APP $ perl -I../dancer2/lib bin/app.pl Also, important to know: most of the plugins may not be working well. Thanks a lot ;)

14 29

Dancer deployment bugs with Plack::Handler::Apache2
by Assaf Gordon 12 Nov '11

12 Nov '11

Hello, I've deployed two Dancer applications on one apache server using "Plack::Handler::Apache2" (one is the "SimpleCrud" test page mentioned yesterday), and I'm experiencing very strange bugs: It seems the two applications are conflicting, when routes or templates from one application are used by the other. That is, the deployment in Apache is as follows: ========= <Location /labmembers/gordon/simple_crud> SetHandler perl-script PerlHandler Plack::Handler::Apache2 PerlSetVar psgi_app /home/gordon/projects/simple_crud_sortable/bin/app.pl </Location> <VirtualHost *:80> ServerName xxxxx.cshl.edu ServerAlias xxxxx DocumentRoot /var/www/data/xxxxx/ <Location "/"> Order Deny,Allow Deny from all Allow from cshl.edu SetHandler perl-script PerlHandler Plack::Handler::Apache2 PerlSetVar psgi_app /var/www/data/xxxxx/dancer/bin/app.pl </Location> </VirtualHost> ========= And when I browse to the virtual server ( http://xxxxx.cshl.edu ), I most of the times get the correct page, but sometimes I get this error: === '/home/gordon/projects/simple_crud_sortable/views/about/index.tt' is not a regular file at /usr/lib/perl5/site_perl/5.8.8/Dancer.pm line 161 === That is: visiting the new application somehow tries to fetch a template from the "simple_crud" application (probably because a wrong route from "simple_crud" was used). I know it sound strange (or unbelievable?), but it has happened several times (not always, though, so it's hard to pin-point). Additionally, several static files (css/images) sometimes returns HTTP-404 - which I guess is also related to routes mix-up. Also, viewing the "/var/log/httpd/error_log" file, I can see dancer debug messages trying to match rountes from my other application even if I visit "http://cancan.cshl.edu/labmembers/gordon/simple_crud/genes". Has any one encountered such behavior ? Or is no one deploying production application using "Plack::Handler::Apache2" ? Thanks, -gordon

3 3

messed up routes
by Mr. Puneet Kishor 12 Nov '11

12 Nov '11

as much as I love Dancer, and I really truly do... as I said when I first used Dancer, it is a breath of fresh air in the world of Perl, Dancer has become really, really unreliable for me. The biggest problem that I face with it is the unreliable way I seem to get routes and layouts delivered to the browser. In my last email to this forum, I noted that I would get different layout than was expected. Today I decided to do a little experimentation. My routes are like so get '/video/:page_name/:movie' => sub { .. debug "using layout main_video"; layout 'main_video'; template 'video_mov', \%template_opts; }; get '/present/:page_name' => sub { .. debug "using layout main_presentation"; layout 'main_presentation'; template 'presentation_slides', \%template_opts; }; get '/*?' => sub { .. debug "using layout main"; template 'index', \%template_opts; } In my layouts I have also embedded debug strings like so    Yet, when I go to a page that should be using the layout main, my log file says [88056] debug @0.001454> [hit #14]using layout main in .. yet, I can see using "View source" in the browser  This is random, and it makes absolutely no sense. I would love to see this resolved, because, partly, I really, really love using Dancer. And, partly, I am sure there is nothing out there that is as easy and pleasurable to use. I shudder at the thought of going back to CGI::App, but I also can't let this unreliability continue. Suggestions? I am serving about 10 or 12 different apps using Starman proxied behind Apache2, if that is any help. -- Puneet Kishor

7 16

Dancer::MIME return value
by thecrux＠gmail.com 02 Nov '11

02 Nov '11

Hi. I had noticed that Dancer/MIME.pm (and also Dancer/Core/MIME.pm in Dancer2) return 42 https://github.com/sukria/Dancer/blob/devel/lib/Dancer/MIME.pm#L67 This is wrong, because generate warning $ perl -wce '42' Useless use of a constant (42) in void context at -e line 1. -e syntax OK Also, with `use warnings FATAL => 'all'` (default for Moo) returned error $ perl -c -Ilib lib/Dancer/Core/MIME.pm ; echo $? Useless use of a constant (42) in void context at lib/Dancer/Core/MIME.pm line 77. 255 -- Vladimir Lettiev aka crux ✉ theCrux(a)gmail.com

4 6

trouble with routes... related to ./public handling?
by Joel Roth 31 Oct '11

31 Oct '11

Hi Dancers (and choreographers) My Dancer is v1.3071. I have content in a ./public directory, and in a ./pages directory. The ./pages includes a nested directory structure that mirrors ./public with a page for each directory. For example: ./public/audio/foo/bar.mp3 ./public/audio/baz.mp3 ./pages/audio.txt # lists items under .../audio/ ./pages/audio/foo.txt # lists items under .../audio/foo/ [1] http://mydomain.com/audio [2] http://mydomain.com/audio/foo URL [1] is converted to the file path ./pages/audio.txt, which is rendered from Markdown to HTML and returned. I expect URL [2] to similarly return a rendered form of ./pages/audio/foo.txt, but what I receive is 404. FWIW, the entire app is small enough to append below, however in the interests of politeness, I'm posting this link: http://pastebin.com/kWrUsZZM My log files are not helpful, as I don't seem to be getting any output into them, despite what I believe to be correct configuration. Zero-length log files *do* get created when the app runs. The apache log reported missing Module::Reload errors that I resolved by setting auto_reload: 0 in config.yml. Thanks for any ideas. Joel -- Joel Roth

2 1

Dancer::Session::CHI on github
by Richard Huxton 28 Oct '11

28 Oct '11

https://github.com/richardhuxton/perl-dancer-session-chi Don't be frightened by the low version number - there's only a dozen lines of code or so. I'll try and find the time to sort out a CPAN upload too. -- Richard Huxton Archonet Ltd

3 5

Devel::Cover won't cover route handlers?
by Michael Alan Dorman 27 Oct '11

27 Oct '11

Hey, all, So I've got a new application I've been working on, and I decided to do a quick coverage check...and found that Devel::Cover seems to ignore all route handlers. You can see this yourself if you wish: dancer -a TestApp cd TestApp perl Makefile.PL cover -test Look at the coverage report, and there's nothing marked for the / route, even though it has been run. Needless to say, this is a little disappointing, if only because I realized that my 100% green report wasn't necessarily true. ;) Any ideas on how to resolve this issue? Mike.

2 3

app works fine but testing fails
by WK 25 Oct '11

25 Oct '11

Terr! I made a little sample app to check out SimpleCRUD plugin, it works fine but when trying to run standard tests bundled with Dancer tests fail like this: $ perl -Ilib t/001_base.t 1..1 Use of uninitialized value in concatenation (.) or string at /home/wanradt/perl5/lib/perl5/Dancer/Plugin/Database.pm line 103. Use of uninitialized value in string eq at /home/wanradt/perl5/lib/perl5/Dancer/Plugin/Database.pm line 112. not ok 1 - use keel; # Failed test 'use keel;' # at t/001_base.t line 5. # Tried to use 'keel'. # Error: Can't connect to data source 'dbi:' because I can't work out what driver to use (it doesn't seem to contain a 'dbi:driver:' prefix and the DBI_DRIVER env var is not set) at /home/wanradt/perl5/lib/perl5/Dancer/Plugin/Database.pm line 147 # Compilation failed in require at (eval 4) line 2. # BEGIN failed--compilation aborted at (eval 4) line 2. # Looks like you failed 1 test of 1. What is problem here? Why test can't see app configuration and use it for DB connection? -- Wbr, Kõike hääd, Gunnar

1 0

running a route from another route within Dancer
by Puneet Kishor 25 Oct '11

25 Oct '11

Is something like the following possible (see the line marked />+/)? Or, even advisable? get '/foo.:format' => sub { my $a = param 'a'; my $b = param 'b'; my $res = query_db($a, $b); return to_json $res; } get '/bar.:format' => sub { my $a = param 'a'; my $b = param 'b'; >>>>>> my $res_foo = <somehow call /foo.json?a=$a&b=$b>; my $res = do_something($res_foo); return to_json $res; } -- Puneet Kishor

3 4

Dancer2 - feature change request
by Richard Huxton 24 Oct '11

24 Oct '11

Since dancer2 is on the way, I thought I'd be cheeky and suggest a slight change in functionality (rather than wait until dancer3). Does anyone (particularly core devs of course) have any strong opinions on the following? At the moment, the logging levels are exposed directly (debug, warning, error). All the major logging modules seem to expose a single object (Log::Log4perl, Log::Dispatch, Log::Any etc). Doing similar would make logging more consistent across dancer and my non-web modules. To be explicit, I'm suggesting this: debug("current id = $id") would become: log->debug("current id = $id") It's a purely cosmetic change at one level, but it does: 1. Reduce namespace pollution 2. Allow for alternative log-levels I actually think the printf-style functionality of Log::Any is worth stealing too. It lets you do things like: log->debugf("user %d has fields %s", $user_id, $user_hashref) With $user_hashref being automatically piped through Data::Dumper -- Richard Huxton Archonet Ltd

7 12