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

Handling file uploads
by Stefan Oberwahrenbrock 25 Mar '11

25 Mar '11

Hello! I have some trouble handling file uploads with my first dancer app. Maybe someone can point me in the right direction: To get hold of an uploaded file sent via PUT, I have set up this route handler: put '/upload/:file' => sub { my $upload = upload( params->{file} ); debug "My Log 1: " . params->{file}; debug "My Log 2: " . ref($upload); }; To test the handler, I feed it with some data sent by "curl": curl --upload-file /srv/mydata.tar.gz http://localhost:3000/upload/ As far as I understand the documentation, $upload should hold a reference to an object of typ Dancer::Request::Upload now. Thus, methods like "filename", "basename", "tempname" etc. should be accessible. The logfile looks quite good - at the beginning: [3432] debug @0.003234> [hit #1] trying to match `/upload/mydata.tar.gz' against /^\/upload\/([^\/]+)$/ in /usr/local/share/perl/5.10.0/Dancer/Route.pm l. 73 [3432] debug @0.003493> [hit #1] My Log 1: mydata.tar.gz in lib/mywebapp.pm l. 26 But the next line indicates, that $upload is not what I expect it to be: [3432] debug @0.003550> [hit #1] My Log 2: in lib/mywebapp.pm l. 27 In addition to that, calling one of methods mentioned above (e. g. "$upload->filename()" ), produces a runtime error: Can't call method filename on an undefined value at... Probably I have not understood the upload() subroutine correctly - any hint is welcome! Thanks, Stefan -- GMX DSL Doppel-Flat ab 19,99 €/mtl.! Jetzt auch mit gratis Notebook-Flat! http://portal.gmx.net/de/go/dsl

2 2

Plat_Forms 2011 programming contest
by Lars Dɪᴇᴄᴋᴏᴡ 迪拉斯 30 Nov '10

30 Nov '10

Crossposted: catalyst(a)lists.scsys.co.uk, dancer-users(a)perldancer.org, mojolicious(a)googlegroups.com, http://perl-community.de/bat/poard/thread/15495 Hello Perl web programmers, the organisers of the [Plat_Forms contest](http://plat-forms.org/) have published the call for application. See the [announcement overview] (http://plat-forms.org/platforms-announcement#overview) for why this contest is very important for the community as a whole. Perl's esteem is at stake. ☺ Up to 4 teams comprised of 3 members each are needed to represent our favourite programming language. Like in the preceding contest in 2007, the Perl teams are likely self-organised and not company- backed. To facilitate that, I have set up [a page on the official Perl 5 wiki] (https://www.socialtext.net/perl5/index.cgi?events_2011_plat_forms) Action required: 1. Communicate as you see fit and form more teams. 2. Post summaries to the wiki page to keep everyone updated. 3. Fill in the [application form](http://plat- forms.org/sites/default/files/Plat_Forms-applicationform.pdf) and snail-mail it to the organisers.

2 2

Re: [Dancer-users] Newbie questions: filter fail
by Joel Roth 26 Nov '10

26 Nov '10

On Wed, Nov 24, 2010 at 10:01:56PM +0200, sawyer x wrote: > On Tue, Nov 23, 2010 at 3:49 PM, Joel Roth <joelz(a)pobox.com> wrote: > > > > > I didn't know a new Dancer was out. > > I just installed it... fixes the filter error > > > > > Glad to hear it! > > > > > > > Any suggestions would be welcome. :-) > > > > > There is a known issue that is already fixed in the source (but not released > to CPAN yet) of a race condition in engine triggers. This affects > Dancer::Session::Cookie, for example. > > This might be what you're experiencing. > > I would really appreciate it if you could try and install the latest source > (from Github) and see if it resolves your problem. > > If not, I sure would like to dwelve into it and fix it. I would also like to experiment with this, however I have a more pressing deployment question. Dancer::Deployment says: your Dancer app can be run as a simple cgi-script out-of-the-box. No additional web-server configuration needed. Your web server should recognize .cgi files and be able to serve Perl scripts. The Perl module Plack::Runner is required. Later: This option is a no-brainer... I think this description is misleading. Blosxom, which I have previously used is not a no-brainer, either, but at least it is a single cgi script. To get to the point of deploying a simple Dancer app, I did the following: 1. Bootstrap local::lib and configure environment variables 2. Install cpanminus # easier than configuring cpan client 3. Install all of Dancer Then to execute the dancer app I needed to: 4. Use an intermediate shell script (dispatch.cgi) to set the environment variables 5. End the script by exec'ing the dancer app (chi2.cgi) Now things are looking close. Dancer starts as usual, listening on port 3000, if I run the dispatch.cgi script while logged in. However when I trigger the app through a link: http://domain.com/dispatch.cgi There is no page returned. The error log reports that dancer is still trying to be a web server. [Thu Nov 25 16:35:56 2010] [error] [client 76.201.170.33] >> Dancer server 15454 listening on http://0.0.0.0:3000 I have Plack::Runner installed. I have not attempted any mod_rewrite magic yet. Can you suggest how I might coax Dancer to return a web page right away with whatever input it has? Thanks :) Joel > Sawyer. -- Joel Roth -- Joel Roth

1 1

Open Source Dancer based applications?
by Gabor Szabo 25 Nov '10

25 Nov '10

When learning a framework it can be very useful to see how other people have implemented their things. It would be nice to see the source code of a bunch of open source Dancer based web sites. It would be nice if they were linked from the Dancefloor of http://perldancer.org/ So are you building such an application? Please share the URL and the repository. regards Gabor

1 0

Fwd: [FOSDEM] Ruby talks?
by Gabor Szabo 25 Nov '10

25 Nov '10

Apparently there is someone who wants to run highlight Sinatra at FOSDEM. I think it would be nice if either the talk was titled "Sinatra, Dancer and other frameworks" or if there was a separate Dancer talk in the same track. Better coordinate with the person who suggested the talk originally. regards Gabor ---------- Forwarded message ---------- From: Francesco Vollero <razorinc(a)gmail.com> Date: Wed, Nov 17, 2010 at 9:47 PM Subject: [FOSDEM] Ruby talks? To: fosdem(a)lists.fosdem.org Hi List, i'm interested to produce a talk about Sinatra and simil microframeworks, but if i understand well, it's not for devroom, where i should send it to see if can be approved or not? Kind regards, Francesco Vollero _______________________________________________ FOSDEM mailing list FOSDEM(a)lists.fosdem.org http://lists.fosdem.org/mailman/listinfo/fosdem

2 3

Newbie questions: filter fail
by Joel Roth 24 Nov '10

24 Nov '10

Hi, I'm totally new to Dancer... but long enough to read all of the docs I could find and browse the list archives for this subject. Looks like just what I want. My first attempt to handle authorization was using a filter. However adding any filter code at all caused my app to fail. For example, the simplified test case below, followed by Dancer's diagnostic output. Thanks for any pointers! package danceapp; use Dancer ':syntax'; use Dancer::Error; our $VERSION = '0.1'; before sub { 1 }; get '/*' => sub { my ($match) = splat; my $content; my $textfile = "$match.txt"; my $fullpath = "$textfile"; if (-r $fullpath ){ template 'training.tt', {content => 'bar', topic => $match, }, {layout => undef }; } else { my $error = Dancer::Error->new( code => 404, message => "No such file: $match", ); Dancer::Response::set($error->render); } }; true; The full error text follows: filter error runtime error An error occured while executing the filter at position : Can't use st +ring ("") as a subroutine ref while "strict refs" in use at (eval 80) + line 11. Stack main in ./danceapp.pl l. 5 Dancer in /home/jroth/perl5/lib/perl5/Dancer.pm l. 105 Dancer in /home/jroth/perl5/lib/perl5/Dancer.pm l. 228 Dancer::Handler::Standalone in /home/jroth/perl5/lib/perl5/Dancer/Hand +ler/Standalone.pm l. 58 Dancer::Handler::Standalone in /home/jroth/perl5/lib/perl5/Dancer/Hand +ler/Standalone.pm l. 54 HTTP::Server::Simple in /usr/share/perl5/HTTP/Server/Simple.pm l. 296 HTTP::Server::Simple in /usr/share/perl5/HTTP/Server/Simple.pm l. 332 HTTP::Server::Simple in /usr/share/perl5/HTTP/Server/Simple.pm l. 427 HTTP::Server::Simple::PSGI in /usr/share/perl5/HTTP/Server/Simple/PSGI +.pm l. 103 HTTP::Server::Simple::PSGI in /usr/share/perl5/HTTP/Server/Simple/PSGI +.pm l. 103 Dancer::Handler::Standalone in /home/jroth/perl5/lib/perl5/Dancer/Hand +ler/Standalone.pm l. 39 Dancer::Handler in /home/jroth/perl5/lib/perl5/Dancer/Handler.pm l. 64 Dancer::Handler in /home/jroth/perl5/lib/perl5/Dancer/Handler.pm l. 65 Dancer::Renderer in /home/jroth/perl5/lib/perl5/Dancer/Renderer.pm l. +24 Dancer::Renderer in /home/jroth/perl5/lib/perl5/Dancer/Renderer.pm l. +98 Dancer::Route::Registry in (eval 80) l. 17 Dancer::Error in /home/jroth/perl5/lib/perl5/Dancer/Error.pm l. 23 Dancer::Error in /home/jroth/perl5/lib/perl5/Dancer/Error.pm l. 208 Settings { engines => {}, import_warnings => 1, mime_types => {}, appname => 'danceapp', views => '/oldroot/home/jroth/build/chi2app/views', layout => 'main', session => 'YAML', public => '/oldroot/home/jroth/build/chi2app/public', confdir => '/oldroot/home/jroth/build/chi2app', show_errors => '1', session_dir => '/oldroot/home/jroth/build/chi2app/sessions', server => '0.0.0.0', log => 'debug', daemon => 0, logger => 'file', warnings => '1', template => 'simple', access_log => 1, appdir => '/oldroot/home/jroth/build/chi2app', charset => '', port => '3000', environment => 'development', content_type => 'text/html', apphandler => 'Standalone', auto_reload => '1' } Session { id => '977589889414368076057528273425511622' } Environment $VAR1 = { SCRIPT_NAME => '', SERVER_NAME => '0.0.0.0', 'psgi.multiprocess' => 0, HTTP_ACCEPT_ENCODING => 'gzip,deflate', PATH_INFO => '/hello', HTTP_CONNECTION => 'keep-alive', CONTENT_LENGTH => undef, REQUEST_METHOD => 'GET', HTTP_ACCEPT => 'text/html,application/xhtml+xml,application/xml;q=0 +.9,*/*;q=0.8', 'psgi.multithread' => 0, HTTP_ACCEPT_CHARSET => 'ISO-8859-1,utf-8;q=0.7,*;q=0.7', QUERY_STRING => '', HTTP_USER_AGENT => 'Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1. +9.1.13) Gecko/20100916 Iceweasel/3.5.13 (like Firefox/3.5.13)', SERVER_PORT => '3000', HTTP_COOKIE => 'dancer.session=977589889414368076057528273425511622 +', HTTP_ACCEPT_LANGUAGE => 'en-us,en;q=0.5', REMOTE_ADDR => '127.0.0.1', CONTENT_TYPE => undef, HTTP_KEEP_ALIVE => '300', SERVER_PROTOCOL => 'HTTP/1.1', 'psgi.streaming' => 1, 'psgi.errors' => *::STDERR, REQUEST_URI => '/hello', 'psgi.version' => [ 1, 1 ], 'psgi.nonblocking' => 0, 'psgix.io' => bless( \*Symbol::GEN2, 'FileHandle' ), 'psgi.url_scheme' => 'http', 'psgi.run_once' => 0, HTTP_HOST => '127.0.0.1:3000', 'psgi.input' => do{my $o} }; $VAR1->{'psgi.input'} = $VAR1->{'psgix.io'}; -- Joel Roth -- Joel Roth

2 3

Dancer 1.2000, finally out
by sawyer x 24 Nov '10

24 Nov '10

*I tried to jot down my memories of the first time I used Dancer. A few images come to mind: - Searching CPAN for "web framework" for a small website for which Catalyst seemed like a complete overkill. - Giving excuses why every web framework wasn't good enough to use (at least for a small-scale project). - Finding Dancer and complaining that I can't configure it for CGI and almost immediately seeing an article by the original author nonetheless - Alexis - on how to configure it. - The fun and enjoyment of developing so rapidly, so easily - Working on my first Dancer feature just because I felt like doing it It is impossible to fit so many memories and thoughts in a few paragraphs, and believe me, I've tried. :) Dancer has always been my favorite project to work on. It's simple, it's light, it's fun and the community is warm and welcoming.* It is with great pride that I present you *Dancer 1.2000, the first major stable community release*. While it is true that most releases of Dancer are communal, but none as much so as the 1.2000 release. This release features the work of a large number of community members, some helped with some docs, some helped with a bug (or two, or three), some helped with reporting issues and helping understand them, surfacing them and making them apparent. Some were just there for support and very much appreciated. This release of Dancer touts the following aspects: - Improved Unicode (specifically UTF-8) support: you now have standardized, clean, well-founded support for UTF-8 applications. This includes support in the code, in the templates and all around. This wasn't easy but we needed it and you deserved it! - Improved documentation: a lot of it was missing and some had to be improved. While the documentation is still not perfect, we have improved it greatly by documenting many components in the Dancer framework and clarified existing documentation. This should help you grasp Dancer better and help young endeavors in any core hacking expedition. :) - Stabilization: We've always wanted users to be able to trust Dancer to be solid and stable and not give them any problems; we've put countless hours into fixing bugs and odd behaviors to ensure that, now more than ever, Dancer is a solid foundation you can depend upon. - Prettier scaffolded app: we've learned yet another lesson from Sinatra and provided a much nicer default design. This assures you'll be able to set up a clean and beautiful website quicker than before without having to worry about a default design. It even uses jQuery - either from CDN or locally. - Improved security: we've also wanted to help you make sure your application is more secure, so now it makes sure not to expose serialization errors. - Better deployment: we've improved the scaffolded dispatchers, especially in regard to PSGI. We intend to provide 1.2000 with small improvements that have to do with stability, documentations and other small improvements which do not break functionality. This release would not have been possible without the help of the following people and is dedicated to them (in no particular order): Alexis Sukrieh, Sawyer X, Franck Cuny, David Precious, Philippe Bruhat, Damien Krotkine, Yanick Champoux, Boris Shomodjvarac, Adam J. Foxson, Naveed Massjouni, Naveen Manivannan, Sebastian de Castelberg, Dave Doyle, Al Newkirk, Stefan Oberwahrenbrock, Puneet Kishor, Gabor Szabo, Roman Galeev, datamuc, Rafał Pocztarski, crujones, snearch, Maurice, Anton Ukolov, Igor Bujna, Nick Langridge, Mike Schroeder, Ivan, Mark Allen and everyone in the community I've missed. Thank you. Soon we will be showcasing Dancer using daily articles on our Advent Calendar. You're still more than invited to help write and/or proofread articles. Dance away, Sawyer.

2 2

Re: [Dancer-users] dancer behind web proxy
by Naveen Manivannan 22 Nov '10

22 Nov '10

I do recall editing this script a while ago to use cpan list (http://cpansearch.perl.org/src/SUKRIA/?C=N;O=D) instead since CHANGES file is way too large. Update your version of Dancer. That being said, including a way to opt out of a version_check or detect a proxy would be nice.

2 1

dancer behind web proxy
by Stefan Oberwahrenbrock 22 Nov '10

22 Nov '10

Hello! Making my first moves on the "development dance floor" I stumbled over an issue I'd like to mention: When I ran "dancer -a mywebapp" to start my first application on a linux machine, the shell/command seemed to freeze. Quite confused I realized after some tries, that the helper script ("/usr/local/bin/dancer") finally finished sucessfully - but only after round about 3 minutes of apparently doing nothing! What happend? Using "strace" I found out, that the helper script tries to establish an internet connection. I traced it down to the subroutine "version_check". Obviously this subroutine checks whether the locally installed version of "Dancer" is up to date. To achieve this, an HTTP-request to "http://search.cpan.org/dist/Dancer/CHANGES" is made. Basically this is a good idea, but in my case it also was the cause for the unexpected bevahiour/delay: The linux machine I was using is located behind a corporate web proxy - direct internet access is not possible. That proxy was configured properly in the linux system (environment variable "http_proxy") and on applicaton level (e. g. CPAN access). Unfortunately the helper script does not seem to utilise proxy settings and gets caught by some default timeout mechanisms. From my point of view it would be nice, if the helper script was able to cope with proxies - at least it would be nice, if the script printed out some message about the attempted internet access. Could be a valuable hint for proxy-plagued novice like me ;-) Greetings, Stefan Oberwahrenbrock

2 4

Dancer meeting #3
by Alexis Sukrieh 22 Nov '10

22 Nov '10

Hi there, Just a reminder for the people near Paris this week: we meet at "The Blue Buoï café", this wednesday (24th of Nov.) in order to speak about Dancer around a couple of beers. Our priority is to organize the upcoming advent calendar, stop by if you can join us! PS: By the way, you did notice we've released Dancer 1.2, didn't you? -- Alexis Sukrieh

2 1