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

Re: [dancer-users] Dancer2 - New App - compilation aborted
by Gert van Oss 20 Sep '13

20 Sep '13

Thanks for you reply, Guess CPAN is outdated then. You're link that was mentioned there did not work but git clone git@github.com:PerlDancer/Dancer2.git Does work. Though… still messing around with paths How to create a skeleton app with this cloned dancer (as opposed to the one that is somewhere on my Mac in /Users/gvo/perl5/perlbrew/perls/dancer_development/bin/perl/dancer2) If I just do something like: ./script/dancer2 -a TestApp My Mac starts complaining about. Can't locate Dancer2/Template/Simple.pm in @INC (@INC contains: /Library/Perl/5.12/ While if I say: `perl -v` it does mention perl v.5.18.1. These path issues never seem to work the way thought they would work. : ( Gert On 20 sep. 2013, at 10:37, Juan José 'Peco' San Martín <jsanmartin(a)gmail.com> wrote: > Hello. > > This is a known bug (Dancer 2.09) already solved at the repo (but not yet uploaded to CPAN) > > You could: > > Install Dancer2 from github: git clone git://github.com/perldancer/Dancer2.git > > Or > > Just try Dancer2.06: cpanm XSAWYER/Dancer2-0.06.tar.gz > > Hope this helps. > Peco > > > > > 2013/9/20 Gert van Oss <gertvanoss(a)me.com> > Starting to have closer look at using Dancer2 I found the following. > > I installed everything as documented (on OS-X with perl v.5.18.1). Then I do: > > dancer2 -a MyApp && cd MyApp > > Next > > perl bin/app.pl > > Can't locate MyApp.pm in @INC (you may need to install the MyApp module) (@INC contains: /Users/gvo/perl5/perlbrew/perls/dancer_development/lib/site_perl/5.18.1/darwin-2level /Users/gvo/perl5/perlbrew/perls/dancer_development/lib/site_perl/5.18.1 /Users/gvo/perl5/perlbrew/perls/dancer_development/lib/5.18.1/darwin-2level /Users/gvo/perl5/perlbrew/perls/dancer_development/lib/5.18.1 .) at bin/app.pl line 3. > BEGIN failed--compilation aborted at bin/app.pl line 3. > > All this did work for Dancer (number one). Can anybody explain me how to solve this. > > Best, > Gert > > _______________________________________________ > 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

1 0

Collision of multiple Dancer2 apps using Plack::Handler::Apache2
by Juan José 'Peco' San Martín 18 Sep '13

18 Sep '13

Hello. Although the general answer seems to be: "yes, with Dancer2 it's possible to run multiple applications on the same server<https://github.com/PerlDancer/Dancer/issues/521>", I'm not able to do it :-/ I'm looking for the way to run 2 apps in *Dancer2* using * Plack::Handler::Apache2* without any trick as "using a proxy to different web servers", or "join two apps in one", etc. Is it possible?. I thought Dancer2 had solved it (instead of Dancer1). With the following configuration, I can only run one application correctly. If I start both, I have a mess ... # App1 <Location /app1> SetHandler perl-script PerlHandler Plack::Handler::Apache2 PerlSetVar psgi_app path_to_app1/bin/app.pl </Location> # App2 <Location /app2> SetHandler perl-script PerlHandler Plack::Handler::Apache2 PerlSetVar psgi_app path_to_app2/bin/app.pl </Location> Thanks a lot. Peco

6 10

Question
by vinnie＠vinniesilva.com 17 Sep '13

17 Sep '13

Morning team, where does the Database connection goes? I mean, how do I tell my dancer application where to find the database? Regards Vinnie Silva vinnie(a)vinniesilva.com www.vinniesilva.com (403) 200-5667

2 1

Dancer::Test and params()
by Tom Hukins 17 Sep '13

17 Sep '13

Hi, I'm working with a Dancer 1 code base that uses Dancer::Test to test itself. One particular route does the following: post '/register' => sub { my $user = param( 'user, 'post' ); my $password = param( 'pass', 'post' ); }; And it has tests like this: my $response = dancer_response POST => 'register', { params => { user => 'me', pass => 'secret' } }; However, I notice that param() only takes one argument, the name of the parameter to fetch. Unlike params(), it cannot specify the parameter's source. I also notice that the documentation for Dancer::Test doesn't state what it does with "params" passed to it. I expect the author of the code I maintain intended to pass these in the HTTP body, whereas I notice it passes them in the query string. Currently, I can encode POST parameters myself and pass them to dancer_response() in the "body" argument, as "body" must contain a string. I plan to implement the following, but thought I would see if anyone objects before I do so: 1. Document that the "params" argument to dancer_response() always populates the query string, even for POST requests. 2. Allow the "body" argument to dancer_response() to take a hash reference as well as a string and make dancer_response() serialise the hash reference. 3. Have Dancer::param() warn if passed more than one argument to help people who mistakenly assume it takes the same arguments as params(). Do my plans seem reasonable? Have I missed a better approach? Thanks, Tom

1 1

get session info without route
by Hugues Max 10 Sep '13

10 Sep '13

Hello I use Dancer 1.3118 with YAML session in config. session: 'YAML' in config.yml in my file.pm I try to use my $PATHXLS = config->{'PATHXLS'}. session 'numclient' .'/'; if this ligne is in any route (get , post, any .. ) it's working for this route but if this line is at beginning of file, outside of route , and I want to use $PATHXLS, info of session 'numclient' is empty I tried to use hook 'before' my $PATHXLS; hook 'before' => sub { $PATHXLS = config->{'PATHXLS'}. session 'numclient' .'/'; }; debug $PATHXLS; but this is the same problem , $PATHXLS is defined but without session info do you have a idea to get a variable for all file with session info ? bye Hugues.

4 10

What about a "use Dancer :config"?
by Cymon 08 Sep '13

08 Sep '13

Hi all, I was a little puzzled when I saw the "Use Dancer :syntax" disappear in the 0.007 release. I thought that a less powerful Dancer inclusion was needed as the "Use Dancer" create an App in every package is used. Thinking about it I realized that probably it's a matter of "code discipline" (tell me if I'm wrong). The right way to do things is not importing "a part" of Dancer environment, but passing the $dsl object when needed, so I accepted that. Even so, I think that there's a case when a "light" dancer import is needed and it is when you need to use some configuration you have in the config.yml that should be the master configuration file for everything in your project (in my idea). So I was wondering if it could be useful to add a "Use Dancer :config" way to import Dancer just to make the config keyword accessible, without creating an App. What do you think about this? -- Simone "Cymon" Faré http://perlishscrewdriver.blogspot.com

3 4

Using Dancer2 as a website framework
by Greg Kempe 07 Sep '13

07 Sep '13

Hi, I'm hoping for the community's input on whether Dancer is an appropriate framework for our project. We're building a website that wraps functionality exposed by an existing Perl EPP library. Perl has great EPP support and we don't want to re-implement that library in another language. In the medium term, the website will need to offer a fairly rich user experience that calls out to other databases and services beyond this one library. We're exploring two options: 1. use Dancer to build the entire website 2. use Dancer to power a thin REST API around the library and use another framework (eg. in Python) to build the rich website experience. Our requirements include: * move quickly, use the right tool for the job (ie. favour re-using components over building everything from scratch) * modern website tooling, such as SASS for CSS, good HTML form support, model validation * well documented and mature software * relatively easy for other devs to work on the project later I'm deliberately trying to avoid a language flame war. Rather, I'm evaluating based on the size and maturity of the User Experience/UI section of the Perl community. Dancer seems well placed for API servers, but the web dev communities seem to be focused around Ruby, Python, Node etc. which is making me lean toward option (2) above. Is that a reasonable evaluation? What do you all think? Thanks, Greg

9 17

New Dancer 2 release: 0.09
by sawyer x 04 Sep '13

04 Sep '13

Hi everyone! We've just cut a new release of Dancer 2. I thought you might like to know about the recent changes done. Mickey Nasriachi continued his work on the core. This is the second release he has appeared in. This time he cleaned up the DSL and made more things immutable (a major target for us), and sped up route compilation, fixed some issues and so on. Do continue on your rampage! Russell Jenkins is determined to close as many open holes as we can find. He has fixed a "forward" problem, cleaned up some of the serializers' behavior and most importantly corrected inaccurate PSGI handling in one edge case that was really bugging me. Thank you, Russell! Ahmed Zawawi joined Dancer history by making his first contribution (congratulations!) by cleaning up a bit in the documentation that confused people and suggesting a proper way of handling reloading while developing. Another new comer in Dancer history is Alex Beamish who also cleaned up a bit of documentation. It's an often-overlooked aspect of projects but it's nothing short of crucial for beginners. And one more new comer is Andrew Solomon who had helped with documentation as well as being quite visible in Github, trying to help us sort out things, and fleshing out possible issues. Welcome Ahmed, Alex and Andrew! If you check the Changes file, you will probably see Alberto Simões and myself. Alberto fixed the autopages (along with the help of Russell) and a small fix in log levels with config files. The autopage fix was extremely important for me, and I'm personally thrilled to have a team that is so in-tuned with working on things that actually trouble people directly. I've been quite busy myself as well, but I managed to work on removing the Dancer ModuleLoader with Class::Load, with a hand from Alberto. This means loading is faster and more correct. I've removed the not-quite-implemented "load_app" keyword and the documented-but-non-existent "load" keyword. With Dancer 2 you just do "use App". It seems we have also successfully phased out the "devel" branch. I've been working on some bigger things in Dancer, but they will take time to ripen. I want to thank all the contributors for their help. You have made Dancer 2 that much better and we appreciate it. A special thanks goes to Alberto for the constant probing and poking to make sure PRs get attention, fixes are done, and releases are made. I also want to give a big shout out to Alexis Sukrieh (sukria), who helped out behind the scenes with throwing ideas around, discussing implementation, providing insight and support. You might not see him much, but he is alive and kicking! Also, he will be at the upcoming Portuguese Perl Workshop. If you're there and I'm not, give him a hug for me. :) Keep in touch! If you have any feedback, please do let us know: mailing list, Github, personal emails, it's all there for you to use. See you next release, Sawyer X, Dancer core team.

2 1

New Dancer incoming - Hannover.pm
by BURNERSK 04 Sep '13

04 Sep '13

Hi all. Dancer is cool so we of Hannover.pm decided to use Dancer for our Perl Mongers homepage. Build a very tiny Dancer CMS around it. Feel free to add it to http://www.perldancer.org/dancefloor :D http://hannover.pm/ -- Cheers, Sören BURNERSK Hannover.pm

5 4

Dancer 1 v1.3118 is on its way to CPAN
by Yanick Champoux 01 Sep '13

01 Sep '13

Good morning dancers, It is my pleasure to announce that I've just cried havoc and slipped out the Dancer of war. Release 1.3118 is on its way to CPAN, and it carries a fair amount of goodies (see below). As usual, a big thank you and a heap of props to everyone who reported bugs, submitted patches, offered advice, displayed patience and silently passed the bottle of rotgut when it was needed. You are the ones keeping the dance floor alive. Joy, DJ `/anick 1.3118 01.09.2013 [ ENHANCEMENTS ] * GH #946: new 'require_environment' setting. (Jesse van Herk) * GH #952: don't set defaults for Template subclasses for Dancer::Template::TemplateToolkit. (Rick Myers) * GH #945: add function 'template_or_serialize' to Dancer::Serializer::Mutable. (Yanick Champoux) [ BUG FIXES ] * GH #655: clarify logger error message. (Yanick Champoux, reported by Gabor Szabo) * GH #951: fix quoting of TemplateToolkit start_tag/stop_tag. (Rick Myers) * GH #940: carry over the session when we forward(). (Yanick Champoux, reported by sciurius) * GH #954: don't die on autoflush for older perls. (Yanick Champoux, reported by metateck and David Golden) * GH #950: Dancer::Test functions now populate REQUEST_URI. (Yanick Champoux, reported by Sören Kornetzki) [ DOCUMENTATION ] * GH #942: simpilify the Apache deployment docs for cgi/fcgi. (bug report by Scott Penrose) [ MISC ] * GH #949: fixes a few errors in the serializer testsuite. (Franck Cuny)

2 1