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

Use of uninitialized value $val
by P Kishor 30 Sep '10

30 Sep '10

I have started getting the following in my Apache error logs Use of uninitialized value $values[0] in join or string at /usr/local/lib/perl5/site_perl/5.12.1/Dancer/Route.pm line 79. I can't recall doing anything special that has started causing this. Doesn't seem to affect the web site, but I would like the error to not occur. -- Puneet Kishor

1 0

How to debug Dancer?
by woosley. xu. 26 Sep '10

26 Sep '10

Hi all, I just begin to use Dancer to build some small sites. It is convenient for sure. But, my problem is, how can I debug a site when I met problems? I start with the code just a PL file, no packages, all the request and function in one file. If there is any Perl grammar errors, sure Perl can find them for me, but if there is any other run time errors, dancer just give me a Error 500, and there is nothing in the log file. Here is the log configuration in my code, I tried to use debug "Hey, I got here!", however, this line never shows up in the log file, maybe it never execute? I have no idea. set logger => 'file'; set log => 'core'; the common thing I have in the log is [10141] core @0.020718> [hit #1] response: 500 in /opt/csw/share/perl/site_perl/Dancer/Handler.pm l. 102 How can I get all the error information? Thanks -- Woosley.Xu

2 4

YAML, why?
by P Kishor 22 Sep '10

22 Sep '10

The following experience (another email thread); using the following in my config.yml charset: utf-8 engines: template_toolkit: ENCODING: utf8 I get the error Error while loading /Users/punkish/Sites/punkish/punkish.pl: YAML Error: Inconsistent indentation level, referer: http://punkish.local/ [Wed Sep 22 06:22:08 2010] [error] [client 127.0.0.1] Code: YAML_PARSE_ERR_INCONSISTENT_INDENTATION Which makes me think, why even bother with YAML? This whole respect for white space and indentation is one of the reasons that makes me detest Python, but now I am doing this in Perl. YAML is useful if I am doing some language agnostic data storage, but this is a tiny config file. It would be just as well being just a perl data structure. I would be able to have any kind of nested complexity in my config, and would never have to worry about YAML parsing errors. Would be nice if there were any option which would allow me to just use pure perl to set my config values, kinda like %CONFIG = { 'charset' => 'utf-8' 'engines' => 'template_toolkit' .. }; -- Puneet Kishor

5 8

croaks on utf-8
by P Kishor 22 Sep '10

22 Sep '10

everytime some fancy character is encountered, I get the following in Plack::Middleware::StackTrace::__ANON__ at /usr/local/lib/perl5/5.12.1/Carp.pm line 62 body must be bytes and should not contain wide characters (UTF-8 strings) How can I enable Dancer (latest) to cooperate with utf-8? -- Puneet Kishor

2 2

Preparing Dancer 1.2
by Alexis Sukrieh 19 Sep '10

19 Sep '10

Hi fellow dancers! We've met with Franck yesterday evening in order to speak about Dancer and for trying to make some decisions regarding our development and maintenance process. We decided the following: * Our priority is to release Dancer 1.2, which will be the next stable release on CPAN. * The code is frozen until Dancer 1.2 is released: the only commits/pull requests that are accepted until then are : - a commit that fixes bug - a commit that fixes a test script failure - a commit that fixes a documentation issue * Targets for Dancer 1.2 These are the key blocker points we identified for 1.2: - Dancer::Headers is rewritten to be based on HTTP::Headers all along the way (the current implementation is a weak point, identified by Franck) - Deployment under Apache with CGI/FCGI and mod_perl should go smoothly when following the documentation given in Dancer::Deployment (this is a common problem regarding the mailing list archives and we want to fix that). - The new website design is shipped (we received a *huge* proposal and every core developer agreed on the fact this design rocks _a lot_. Check this draft out: http://cl.ly/72278b35886dda8878b3 By the way, a big thank to everyone who submitted a redesign proposal, they were all looking great, but this one took our vote, because it's really unique-looking and ... cool :) === [ What you can do to help us ] === * Testing We really want Dancer 1.2 to be rock solid. We welcome very much reports about deployment issues, so feel free to contact us if you have any problem with 1.1811 * Documentation reviews Even if we did enhance a lot our documentation lately, typos and errors still occur, so feel free to review Dancer::Deployment, Dancer::Cookbook and Dancer::Tutorial. Pull requests are welcome for documentation fixes. * Spread the word Dancer is lucky enough to have lots of enthusisast users and we're very proud of that. If you like Dancer, spread the word :) blog, tweet, talk to your friends and coworkers. Show off some demo apps at work. This is good marketing and it's quite as important as the code itself. I'll try to write a mail to the list whenever we did some significant progress regarding the 1.2 release, so stay tuned! PS: no, there is no date scheduled yet for the release, don't ask ;) -- Alexis Sukrieh

2 1

New web site design [Was: Preparing Dancer 1.2]
by Flavio Poletti 17 Sep '10

17 Sep '10

Hi, just a feedback on the new web site design. The head part is very wide (the horizontal slider appeared in Safari, I had to enlarge the browser's window to include the whole page horizontally), but the main section below is quite slim the two tiny sub-windows with the Dancer example wrap the text inside. I would restrict the head part and enlarge the main one. Just my 2c, Flavio. On Fri, Sep 17, 2010 at 5:00 PM, Alexis Sukrieh <sukria(a)sukria.net> wrote: > Hi fellow dancers! > > We've met with Franck yesterday evening in order to speak about Dancer and > for trying to make some decisions regarding our development and maintenance > process. > > We decided the following: > > * Our priority is to release Dancer 1.2, which will be the next stable > release on CPAN. > > * The code is frozen until Dancer 1.2 is released: the only commits/pull > requests that are accepted until then are : > > - a commit that fixes bug > - a commit that fixes a test script failure > - a commit that fixes a documentation issue > > * Targets for Dancer 1.2 > > These are the key blocker points we identified for 1.2: > > - Dancer::Headers is rewritten to be based on HTTP::Headers all along > the way (the current implementation is a weak point, identified by > Franck) > > - Deployment under Apache with CGI/FCGI and mod_perl should go > smoothly when following the documentation given in > Dancer::Deployment (this is a common problem regarding the mailing > list archives and we want to fix that). > > - The new website design is shipped (we received a *huge* proposal > and every core developer agreed on the fact this design rocks > _a lot_. Check this draft out: http://cl.ly/72278b35886dda8878b3 > > By the way, a big thank to everyone who submitted a redesign > proposal, they were all looking great, but this one took our vote, > because it's really unique-looking and ... cool :) > > > === [ What you can do to help us ] === > > > * Testing > > We really want Dancer 1.2 to be rock solid. We welcome very much reports > about deployment issues, so feel free to contact us if you have any problem > with 1.1811 > > > * Documentation reviews > > Even if we did enhance a lot our documentation lately, typos and errors > still occur, so feel free to review Dancer::Deployment, Dancer::Cookbook and > Dancer::Tutorial. Pull requests are welcome for documentation fixes. > > > * Spread the word > > Dancer is lucky enough to have lots of enthusisast users and we're very > proud of that. If you like Dancer, spread the word :) blog, tweet, talk to > your friends and coworkers. Show off some demo apps at work. This is good > marketing and it's quite as important as the code itself. > > > I'll try to write a mail to the list whenever we did some significant > progress regarding the 1.2 release, so stay tuned! > > > PS: no, there is no date scheduled yet for the release, don't ask ;) > > -- > Alexis Sukrieh > _______________________________________________ > Dancer-users mailing list > Dancer-users(a)perldancer.org > http://www.backup-manager.org/cgi-bin/listinfo/dancer-users >

2 1

Dancer::Plugin:Database with multiple connections - request for testers
by David Precious 15 Sep '10

15 Sep '10

Hi all, I've just released a new version of Dancer::Plugin::Database incorporating an excellent new feature contributed by Igor Bujna - the ability to handle multiple connections. You can now define multiple connections in your config file, for example: plugins: Database: [...] connections: foo: driver: 'SQLite' database: 'foo.sqlite' bar: driver: 'SQLite' database: 'bar.sqlite' You can then pass the name of the connection you want to the database() keyword - for instance: my $dbh_foo = database('foo'); # or use it directly: my $sth = database('foo')->prepare('...'); Configuration details declared the existing way will be used if you don't supply a name to database(). I've just released this to CPAN as a developer release 0.08_01, or you can pull from the repo on Github. Assuming all seems OK, I plan to get it released as version 0.09 some time later this week. I also plan to write some good tests for it, but I'm not sure the best way to go about testing it to be honest - any thoughts would be appreciated. I could use DBD::Mock or Test::MockDBI to mock up the database interactions so I'm just testing the way the plugin works, but I'd ideally need to test it as it would be used from a Dancer app, which is the bit I'm not sure about. Cheers Dave P -- David Precious <davidp(a)preshweb.co.uk> http://blog.preshweb.co.uk/ www.preshweb.co.uk/twitter www.preshweb.co.uk/linkedin www.preshweb.co.uk/facebook www.preshweb.co.uk/identica www.lyricsbadger.co.uk "Programming is like sex. One mistake and you have to support it for the rest of your life". (Michael Sinz)

2 1

Session collision of multiple web sites with Plack::Handler::Apache2
by P Kishor 14 Sep '10

14 Sep '10

I had been experiencing strange problems until I inadvertently discovered, what I believe, is the cause. I have several Dancer-based web sites hosted with Plack::Handler::Apache2 and virtual hosts on the same server. Well, the config info of one web site is visible in and affects the other web sites. All my virtual hosts have a Location / section in their respective definitions like so NameVirtualHost *:80 <VirtualHost *:80> ServerName app1.org DocumentRoot "/Users/punkish/Sites/app1" <Directory "/Users/punkish/Sites/app1"> AllowOverride None Order allow,deny Allow from all </Directory> <Location /> SetHandler perl-script PerlHandler Plack::Handler::Apache2 PerlSetVar psgi_app /Users/punkish/Sites/app1/app1.pl </Location> </VirtualHost> <VirtualHost *:80> ServerName app2.org DocumentRoot "/Users/punkish/Sites/app2" <Directory "/Users/punkish/Sites/app2"> AllowOverride None Order allow,deny Allow from all </Directory> <Location /> SetHandler perl-script PerlHandler Plack::Handler::Apache2 PerlSetVar psgi_app /Users/punkish/Sites/app2/app2.pl </Location> </VirtualHost> However, when I look at the debug info (actually, I had an error in my code, which caused a runtime error, and the error messages were written to the browser... that is when I discovered this situation), I see this "collision." Basically, when I go to http://app2.org, I see the config info from app1. I believe this is because in Apache's memory, all the psgi_apps are being loaded once, and they are colliding. What can I do to avoid this? The obvious answer is to use CGI, but surely, I should be able to host multiple, different Dancer apps on the same Apache server, no? -- Puneet Kishor http://www.punkish.org Carbon Model http://carbonmodel.org Charter Member, Open Source Geospatial Foundation http://www.osgeo.org Science Commons Fellow, http://sciencecommons.org/about/whoweare/kishor Nelson Institute, UW-Madison http://www.nelson.wisc.edu ----------------------------------------------------------------------- Assertions are politics; backing up assertions with evidence is science =======================================================================

1 1

before_template help
by igor.bujna＠post.cz 13 Sep '10

13 Sep '10

Hello, i read documentation for before_template in http://search.cpan.org/~sukria/Dancer/lib/Dancer.pm#before_template It will be nice to put some help text like before_template sub { my $tokens = shift; $tokens->{'hello'} = sub { return "hello world\n"; }; }; for understanding use before_template. Thank you

1 1

Apache with Plack deployment woes seem to be back
by P Kishor 13 Sep '10

13 Sep '10

Per 1.1811 deployment docs, if running from Apache with Plack, the following should do the trick <Location /> SetHandler perl-script PerlHandler Plack::Handler::Apache2 PerlSetVar psgi_app /Sites/app/app.pl </Location> When I try to run with the above, I get the following error in my Apache logs [Sat Sep 11 20:37:56 2010] [error] [client 127.0.0.1] Error while loading /Users/punkish/Sites/app/app.pl: unable to load application app : Can't locate app.pm in @INC (@INC contains: lib /usr/local/apache2/bin/lib /usr/local/lib/perl5/site_perl/5.12.1/darwin-2level /usr/local/lib/perl5/site_perl/5.12.1 /usr/local/lib/perl5/5.12.1/darwin-2level /usr/local/lib/perl5/5.12.1 /usr/local/lib/perl5/site_perl . /usr/local/apache2) at (eval 57) line 2.\nBEGIN failed--compilation aborted at (eval 57) line 2.\n My app directory looks like so -rw-r--r-- 1 punkish punkish 635 Aug 25 00:23 Makefile.PL -rwxr-xr-x@ 1 punkish punkish 80 Sep 11 20:39 app.pl* -rw-r--r--@ 1 punkish punkish 682 Sep 11 21:01 config.yml drwxr-xr-x 4 punkish punkish 136 Aug 25 00:23 environments/ drwxr-xr-x 5 punkish punkish 170 Sep 11 20:57 lib/ drwxr-xr-x 3 punkish punkish 102 Aug 25 00:32 logs/ drwxr-xr-x 11 punkish punkish 374 Sep 7 13:38 public/ drwxr-xr-x 4 punkish punkish 136 Aug 25 00:23 t/ drwxr-xr-x 6 punkish punkish 204 Sep 11 21:04 views/ and my app.pl file looks like so #!/usr/local/bin/perl use Dancer; use lib ('lib'); load_app 'app'; dance; and my app/lib directory looks like so drwxr-xr-x 6 punkish punkish 204 Sep 11 21:30 app/ -rw-r--r--@ 1 punkish punkish 397 Sep 11 20:57 app.pm What am I doing wrong? -- Puneet Kishor http://www.punkish.org Carbon Model http://carbonmodel.org Charter Member, Open Source Geospatial Foundation http://www.osgeo.org Science Commons Fellow, http://sciencecommons.org/about/whoweare/kishor Nelson Institute, UW-Madison http://www.nelson.wisc.edu ----------------------------------------------------------------------- Assertions are politics; backing up assertions with evidence is science =======================================================================

3 4