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

Can I write own config in config.yml?
by chenlin rao 11 Dec '12

11 Dec '12

I try to write my own elasticsearch config in config.yml: ElasticSearch: servers: "10.10.10.33:9200" transport: "httplite" max_requests: 10000 trace_calls: 0 no_refresh: 0 But after I got the right `config->{ElasticSearch}` in my lib/DancerApp/A.pm, I got `config->{ElasticSearch}` in my lib/DancerApp/B.pm returns only one line as 'trace_calls:0'. I try to got config->{appdir} at multi sub and got right result everywhere. Why??

3 2

Re: [dancer-users] dancer-users Digest, Vol 34, Issue 3
by chenlin rao 10 Dec '12

10 Dec '12

config.yml: > ElasticSearch: > servers: "10.10.10.33:9200" > transport: "httplite" > max_requests: 10000 > trace_calls: 0 > no_refresh: 0 lib/App.pm: >use lib "$Bin/../lib"; >use App::A; >use App::B; lib/App/A.pm: >use Dancer ':syntax'; >use ElasticSearch; >my $elsearch = ElasticSearch->new( config->{ElasticSearch} ); >prefix '/a'; >get '/config' => sub { return Dumper $elsearch }; lib/App/B.pm: >use Dancer ':syntax'; >use ElasticSearch; >my $elsearch = ElasticSearch->new( config->{ElasticSearch} ); >prefix '/b'; >get '/config' => sub { return Dumper $elsearch }; Then `get http://localhost:3000/a/config` show that servers: " 10.10.10.33:9200" but `get http://localhost:3000/b/config` show that servers: "127.0.0.1:9200" which is the default setting of ElasticSearch module. 2012/12/10 <dancer-users-request(a)dancer.pm> > Send dancer-users mailing list submissions to > dancer-users(a)dancer.pm > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users > or, via email, send a message with subject or body 'help' to > dancer-users-request(a)dancer.pm > > You can reach the person managing the list at > dancer-users-owner(a)dancer.pm > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of dancer-users digest..." > > > Today's Topics: > > 1. Can I write own config in config.yml? (chenlin rao) > 2. Re: Can I write own config in config.yml? (David Precious) > 3. Re: Can I write own config in config.yml? (David Precious) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 10 Dec 2012 16:56:46 +0800 > From: chenlin rao <rao.chenlin(a)gmail.com> > Subject: [dancer-users] Can I write own config in config.yml? > To: dancer-users(a)perldancer.org > Message-ID: > <CABwsoohczVCJwVxZcFUqPaS2KdxsK8-rE-V0= > TeJEmDEPr4r5w(a)mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > I try to write my own elasticsearch config in config.yml: > > ElasticSearch: > servers: "10.10.10.33:9200" > transport: "httplite" > max_requests: 10000 > trace_calls: 0 > no_refresh: 0 > > But after I got the right `config->{ElasticSearch}` in my > lib/DancerApp/A.pm, I got `config->{ElasticSearch}` in my > lib/DancerApp/B.pm returns only one line as 'trace_calls:0'. > > I try to got config->{appdir} at multi sub and got right result everywhere. > > Why?? >

2 2

Test, please ignore (testing old list address forwarding)
by David Precious 05 Dec '12

05 Dec '12

Just checking that mails to the old list address arrive via the new list as they should. -- David Precious ("bigpresh") <davidp(a)preshweb.co.uk> http://www.preshweb.co.uk/ www.preshweb.co.uk/twitter www.preshweb.co.uk/linkedin www.preshweb.co.uk/facebook www.preshweb.co.uk/cpan www.preshweb.co.uk/github

1 0

Advent Calendar : Request for volunteers
by Alexis Sukrieh 05 Dec '12

05 Dec '12

Hello fellow Dancers! As you may know, we're running for the third consecutive year the Perl Dancer Advent Calendar: http://advent.perldancer.org/ It's being very well received (almost 300% traffic growth compared to last year) and each day we reach more than 500 unique visitors. It's a very good opportunity for us to showcase Dancer. That's great but there is a problem Houston! We don't have enough contributions! I'm requesting your help: if you want to contribute to the effort, you're more than welcome! Contributions are pretty easy to do: Fork and clone the repo at https://github.com/PerlDancer/advent-calendar And add your article in the pending directory then send a pull request. We'll do the rest. Your article doesn't need to be long, many things are possible: a Plugin you're using and how, a use case of Dancer at work, at home, what you like in Dancer, why did you use Dancer... Thanks a lot!

2 2

Re: [dancer-users] [Dancer-users] Dancer2 best practices
by Alexis Sukrieh 05 Dec '12

05 Dec '12

Actually, regarding the scaffolding of an app, it's exactly the same. Take a look at the Advent Calendar app, it's Dancer2! Nothing new here, 100% the same as Dancer 1 except that you can use any config file format instead of being forced to YAML. The only change you have to do is about TT's defaut markers (they are [% and %] in D2) and also, the config hierarchy for engines which is now: engines: $type: $name: ... Whereas with D1 there was no "$type" level. Appart from that, everything works just like the same. 2012/11/29 Maurice Mengel <mauricemengel(a)gmail.com> > Somebody point me to an article or two that might make sense, please. > Thanks! > > On Thu, Nov 29, 2012 at 1:15 PM, sawyer x <xsawyerx(a)gmail.com> wrote: > >> that, yes! >> > > > _______________________________________________ > Dancer-users mailing list > Dancer-users(a)perldancer.org > http://www.backup-manager.org/cgi-bin/listinfo/dancer-users > >

1 0

What do you think of Dancer? ( & Advent calendar posts needed!)
by David Precious 05 Dec '12

05 Dec '12

Hi all, We still have spots left for more posts on the Dancer advent calendar, so if anyone fancies contributing a post, don't be shy, let us know! Also, I'm thinking a good idea for a post might be a set of testimonial-type paragraphs from Dancer users, explaining what they use Dancer for, what they like about Dancer, and what they'd like to see in the future etc. So, if you use Dancer, and have a moment to spare to provide us a quote, please mail me with, say, 1-5 paragraphs - as above, good things to include would be what you use Dancer for, what you like about Dancer, what you'd like to see in future from Dancer etc. (These may also be used on the testimonials page on the site, which could do with an update.) Also, if you have a Dancer-powered site which isn't yet featured on the dancefloor page ( www.dancer.pm/dancefloor ) and you'd like it to be, please let me know! Cheers all Dave P -- David Precious ("bigpresh") <davidp(a)preshweb.co.uk> http://www.preshweb.co.uk/ www.preshweb.co.uk/twitter www.preshweb.co.uk/linkedin www.preshweb.co.uk/facebook www.preshweb.co.uk/cpan www.preshweb.co.uk/github

1 0

Problem with Dancer::Test, forward and session
by Marco Pessotto 03 Dec '12

03 Dec '12

Hello all! I think, but not sure, I've hit a bug in Dancer::Test. This is the minimal example: #### cut here ##### package DancerMelmothBug; use Dancer ':syntax'; post '/login' => sub { if (params->{username} and params->{password}) { session 'auth' => 1; } }; get '/login' => sub { return "login screen"; }; post '/works' => sub { return redirect '/login' unless session->{auth}; warn "works!"; return "it works"; }; post '/first' => sub { return redirect '/login' unless session->{auth}; warn "forwarding\n"; forward '/second'; }; post '/second' => sub { return redirect '/login' unless session->{auth}; warn "done\n"; return "OK"; }; 1; ###### cut here ########## This is the test script ##### cut here ##### use Test::More tests => 2; use DancerMelmothBug; use Dancer::Test; use Data::Dumper; use HTTP::Headers; my $login_creds = { username => "tester", password => "provaprova", }; my $loggingin = dancer_response (POST => '/login', { params => $login_creds }); my $sessionkey = $loggingin->header('Set-Cookie'); if ($sessionkey =~ m/(dancer\.session=.*?;)/) { $sessionkey = $1; print "Got the session key $sessionkey\n"; } my $loggedinheader = HTTP::Headers->new( cookie => $sessionkey ); my $response; $response = dancer_response(POST => "/works", { params => {}, headers => $loggedinheader, }); ok($response->content); $response = dancer_response(POST => "/first", { params => {}, headers => $loggedinheader, }); ok($response->content); ##### cut here #### Running the test yields: perl test.t 1..2 Got the session key dancer.session=4079393373042855076725642369476525; works! at DancerMelmothBug.pm line 17. ok 1 forwarding not ok 2 # Failed test at test.t line 42. # Looks like you failed 1 test of 2. So, it looks like it fails to get the session after the forwarding. It also seems that the bug is present only in the testing environment, because the running app is reacting properly. Best wishes and thanks in advance. -- Marco

1 0