From jean-marie.bourbon at armaturetech.com Mon Sep 1 17:45:00 2014 From: jean-marie.bourbon at armaturetech.com (jean-marie.bourbon at armaturetech.com) Date: Mon, 1 Sep 2014 16:45:00 +0000 Subject: [dancer-users] Question about Perl Dancer Framework Message-ID: On 09/01/2014 03:56 AM, jean-marie.bourbon at armaturetech.com wrote: > Hi guys! > > I recently tried to build my own web application using Dancer but I'm a basic perl developer and I have any interrogations about this framework. > > I've first tried to build a login page based on your "navbar_login" example. > Once logged in I try to call another page named "test" but it seems to not work (I don't know how to call my page and how Dancer work exactly .. to be honest :-( . ) > : > I have a login.pm module, main.tt (in views/layout/) index.tt and test.tt in views. > Im my login.pm I have declared my routes as following: > > get '/index' => sub { template 'index' }; > > get '/' => sub { template 'login' }; > > get 'test' => sub { > template 'test'; > }; > > So, once logged in I try (and fail) to call my page like this: > > > elsif($password eq "12345") { > #print "ok"; > #return ''; > #return template 'examples/photo_carousel';# 'index'; > #my @animals = qw/dogs cats camels mooses vogons/; > return template 'test' => { > show => "launching test.tt", > }; > #session $username => params->{$username}; > #redirect params ->{'index'}; > > #show_ > } > > Fail also with redirect parameter .. But why and how to call my test page ? > I don't understand why it doesn't work, can you explain me please ? > > Thanks a lot ! > From asb.cpan at gmail.com Tue Sep 2 20:53:50 2014 From: asb.cpan at gmail.com (Alex Becker) Date: Tue, 2 Sep 2014 21:53:50 +0200 Subject: [dancer-users] Upload form tutorial Message-ID: Dear all, is there a tutorial how to create a Perl upload form with Dancer? Something basic and simple like this but without CGI? -> http://www.perlmeme.org/tutorials/cgi_upload.html Because, when I was a real noob, I learned Perl from scripts like these. And I still enjoy learning new things this way. Regards, Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcarey at ucar.edu Tue Sep 2 21:10:31 2014 From: mcarey at ucar.edu (Maxwell Carey) Date: Tue, 2 Sep 2014 14:10:31 -0600 Subject: [dancer-users] Upload form tutorial In-Reply-To: References: Message-ID: Not quite a tutorial, but the docs for Dancer::Request::Upload contain a good, simple example: # somewhere in your view:
# and then in your application handler: post '/upload' => sub { my $file = request->upload('filename'); $file->copy_to($upload_dir); # or whatever you need }; On Tue, Sep 2, 2014 at 1:53 PM, Alex Becker wrote: > Dear all, > > is there a tutorial how to create a Perl upload form with Dancer? > Something basic and simple like this but without CGI? -> > http://www.perlmeme.org/tutorials/cgi_upload.html > Because, when I was a real noob, I learned Perl from scripts like these. > And I still enjoy learning new things this way. > > Regards, > Alex > > _______________________________________________ > dancer-users mailing list > dancer-users at dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mail at knutov.com Tue Sep 2 21:25:22 2014 From: mail at knutov.com (Nick Knutov) Date: Wed, 03 Sep 2014 02:25:22 +0600 Subject: [dancer-users] Upload form tutorial In-Reply-To: References: Message-ID: <540627B2.5040300@knutov.com> More interesting is how to upload with jquery upload plugin and Dancer - http://blueimp.github.io/jQuery-File-Upload/ 03.09.2014 2:10, Maxwell Carey ?????: > Not quite a tutorial, but the docs for Dancer::Request::Upload > contain a > good, simple example: > [...] > > On Tue, Sep 2, 2014 at 1:53 PM, Alex Becker > wrote: > > Dear all, > > is there a tutorial how to create a Perl upload form with Dancer? > Something basic and simple like this but without CGI? -> > http://www.perlmeme.org/tutorials/cgi_upload.html > Because, when I was a real noob, I learned Perl from scripts like > these. And I still enjoy learning new things this way. > [...] -- Best Regards, Nick Knutov http://knutov.com ICQ: 272873706 Voice: +7-904-84-23-130 From asb.cpan at gmail.com Tue Sep 2 22:13:05 2014 From: asb.cpan at gmail.com (Alex) Date: Tue, 2 Sep 2014 23:13:05 +0200 Subject: [dancer-users] Upload form tutorial In-Reply-To: <540627B2.5040300@knutov.com> References: <540627B2.5040300@knutov.com> Message-ID: This is possible with Dancer? > Am 02.09.2014 um 22:25 schrieb Nick Knutov : > > > More interesting is how to upload with jquery upload plugin and Dancer - > http://blueimp.github.io/jQuery-File-Upload/ > > > 03.09.2014 2:10, Maxwell Carey ?????: >> Not quite a tutorial, but the docs for Dancer::Request::Upload >> contain a >> good, simple example: >> [...] >> >> On Tue, Sep 2, 2014 at 1:53 PM, Alex Becker > > wrote: >> >> Dear all, >> >> is there a tutorial how to create a Perl upload form with Dancer? >> Something basic and simple like this but without CGI? -> >> http://www.perlmeme.org/tutorials/cgi_upload.html >> Because, when I was a real noob, I learned Perl from scripts like >> these. And I still enjoy learning new things this way. >> [...] > > -- > Best Regards, > Nick Knutov > http://knutov.com > ICQ: 272873706 > Voice: +7-904-84-23-130 > _______________________________________________ > dancer-users mailing list > dancer-users at dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users From mail at knutov.com Tue Sep 2 22:23:04 2014 From: mail at knutov.com (Nick Knutov) Date: Wed, 03 Sep 2014 03:23:04 +0600 Subject: [dancer-users] Upload form tutorial In-Reply-To: References: <540627B2.5040300@knutov.com> Message-ID: <54063538.8010402@knutov.com> Yes I hope. But I don't know how to do it yet. 03.09.2014 3:13, Alex ?????: > This is possible with Dancer? > >> Am 02.09.2014 um 22:25 schrieb Nick Knutov : >> >> >> More interesting is how to upload with jquery upload plugin and Dancer - >> http://blueimp.github.io/jQuery-File-Upload/ >> >> >> 03.09.2014 2:10, Maxwell Carey ?????: >>> Not quite a tutorial, but the docs for Dancer::Request::Upload >>> contain a >>> good, simple example: >>> [...] >>> >>> On Tue, Sep 2, 2014 at 1:53 PM, Alex Becker >> > wrote: >>> >>> Dear all, >>> >>> is there a tutorial how to create a Perl upload form with Dancer? >>> Something basic and simple like this but without CGI? -> >>> http://www.perlmeme.org/tutorials/cgi_upload.html >>> Because, when I was a real noob, I learned Perl from scripts like >>> these. And I still enjoy learning new things this way. >>> [...] >> >> -- >> Best Regards, >> Nick Knutov >> http://knutov.com >> ICQ: 272873706 >> Voice: +7-904-84-23-130 >> _______________________________________________ >> dancer-users mailing list >> dancer-users at dancer.pm >> http://lists.preshweb.co.uk/mailman/listinfo/dancer-users > _______________________________________________ > dancer-users mailing list > dancer-users at dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users > -- Best Regards, Nick Knutov http://knutov.com ICQ: 272873706 Voice: +7-904-84-23-130 From warren at etr-usa.com Wed Sep 3 00:08:20 2014 From: warren at etr-usa.com (Warren Young) Date: Tue, 02 Sep 2014 17:08:20 -0600 Subject: [dancer-users] Upload form tutorial In-Reply-To: References: <540627B2.5040300@knutov.com> Message-ID: <54064DE4.3050405@etr-usa.com> On 9/2/2014 15:13, Alex wrote: > This is possible with Dancer? Yes. We've been doing this for many years now, first with Apache::ASP, and now with Dancer 1. As the linked-to page says, you only need a server-side platform that understands HTML form file uploads. To do this really right, you need a browser that understands the HTML5 File API, but that's pretty much every browser going back many years, except for IE, where it didn't appear until IE10: http://caniuse.com/#feat=fileapi I can't share the JS or Dancer code, since it's part of a proprietary app, but I can assure you that the tutorials you'll find for the popular server-side web frameworks translate easily to Dancer. There isn't any trickery involved. Just translate the PHP or whatever code you've dug up in the way that seems most obvious, and it's probably correct. The end result is much better than the old "submit single huge blob to multipart HTML form" way of doing file uploads, particularly for large files and/or slow networks. Anyone trying this and failing should make use of Cunningham's Law: The fastest way to get the right answer on the Internet is to post the wrong answer. That is, post your broken code and I or someone else will quickly tell you where you screwed up. :) Asking strangers to provide a ready to use example is less effective. From xsawyerx at gmail.com Sat Sep 6 23:37:35 2014 From: xsawyerx at gmail.com (Sawyer X) Date: Sun, 7 Sep 2014 00:37:35 +0200 Subject: [dancer-users] Question about Perl Dancer Framework In-Reply-To: References: Message-ID: Hi Jean-Marie. Welcome! :) Let's go over the code you showed. > get '/index' => sub { template 'index' }; That will declare a path "/index" for a GET request which will render a template called (if you're using the default templating framework) "index.tt". So far so good. > get '/' => sub { template 'login' }; When someone goes to the main page, render 'login.tt'. > get 'test' => sub { > template 'test'; > }; You probably want to change this to "get '/test'" instead of "get 'test'". Paths should begin with "/", almost always. > #return ''; In this case, you want to simply use "redirect" keyword which would do this for you: get '/test' => sub { redirect "/"; # redirect to main page }; In your example, you're trying to redirect to "./views/test.tt" which is a file. HTTP redirects are for *paths*, not *files*. If you want people who go to "/wrong/place" to go to "/test" which renders the right template ("test.tt"), you would write this: get '/wrong/place => sub { redirect '/test' }; get '/test => sub { template 'test'; } Does this help? S. On Mon, Sep 1, 2014 at 6:45 PM, jean-marie.bourbon at armaturetech.com < jean-marie.bourbon at armaturetech.com> wrote: > > > On 09/01/2014 03:56 AM, jean-marie.bourbon at armaturetech.com wrote: > > Hi guys! > > > > I recently tried to build my own web application using Dancer but I'm a > basic perl developer and I have any interrogations about this framework. > > > > I've first tried to build a login page based on your "navbar_login" > example. > > Once logged in I try to call another page named "test" but it seems to > not work (I don't know how to call my page and how Dancer work exactly .. > to be honest :-( . ) > > : > > I have a login.pm module, main.tt (in views/layout/) index.tt and > test.tt in views. > > Im my login.pm I have declared my routes as following: > > > > get '/index' => sub { template 'index' }; > > > > get '/' => sub { template 'login' }; > > > > get 'test' => sub { > > template 'test'; > > }; > > > > So, once logged in I try (and fail) to call my page like this: > > > > > > elsif($password eq "12345") { > > #print "ok"; > > #return ''; > > #return template 'examples/photo_carousel';# 'index'; > > #my @animals = qw/dogs cats camels mooses vogons/; > > return template 'test' => { > > show => "launching test.tt", > > }; > > #session $username => params->{$username}; > > #redirect params ->{'index'}; > > > > #show_ > > } > > > > Fail also with redirect parameter .. But why and how to call my test > page ? > > I don't understand why it doesn't work, can you explain me please ? > > > > Thanks a lot ! > > > _______________________________________________ > dancer-users mailing list > dancer-users at dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From yanick at babyl.dyndns.org Tue Sep 9 01:53:58 2014 From: yanick at babyl.dyndns.org (Yanick Champoux) Date: Mon, 08 Sep 2014 20:53:58 -0400 Subject: [dancer-users] Dancer 1 v1.3127 on its way to CPAN Message-ID: <540E4FA6.1090505@babyl.dyndns.org> Hi all! A new version of Dancer 1 is on its way to CPAN as we speak -- the changelog is provided below for your pleasure. As usual, a big thank to everyone who pitched in. You're all wonderful, wonderful people. :-) Joy, `/anick 1.3127 2014-09-08 [BUG FIXES] - Test was using deprecated 'import_warnings'. (GH#1045, mokko) - Fix default test names for headers and redirection test methods. (GH#1048, odyniec) - DANCER_SERVER_TOKENS and DANCER_SESSION_INFO are now DANCER_NO_SERVER_TOKENS and DANCER_NO_SESSION_INFO. And working. :-) (GH#1014, Yanick Champoux) - 'any' wasn't understanding 'del' (only 'delete'). (GH#1044, Yanick Champoux) [DISTRIBUTION] - Now using Dist::Zilla as package manager. [DOCUMENTATION] - Correct POD formatting for HTTP methods in introduction.pod. (GH#1047, Lx) [ENHANCEMENTS] - environment configs are now merged with the global config, versus the previous behavior that was overriding the whole config segments. (GH#1016, Yanick Champoux) - Dancer::Handler::Debug now accepts env variables from the command-line. (GH#1056, Yanick Champoux) - Accessing values abstracted as methods in Dancer::Session. (GH#1000, John Wittkoski) From racke at linuxia.de Wed Sep 10 10:52:39 2014 From: racke at linuxia.de (Stefan Hornburg (Racke)) Date: Wed, 10 Sep 2014 11:52:39 +0200 Subject: [dancer-users] Final call for early bird tickets Message-ID: <54101F67.3020102@linuxia.de> Early bird tickets for the Perl Dancer conference are available for sale until 12th September. You are saving 20 $ on the ticket for the training (6./7. October) and 30 $ on the ticket for the conference (8./9. October). On top of that students save 50% with a valid student ID. Please register for the conference on http://act.perl.dance/eic2014/registration.html and follow the payment instructions on the bottom of the page. Our main speakers are Sawyer X (Dancer) and Peter Rabbitson (DBIx::Class). Presentations are about Dancer, DBIx::Class and E-Commerce amongst other topics. Check http://act.perl.dance/eic2014/talks for more information. You can also still submit your own presentation at http://act.perl.dance/eic2014/newtalk. The conference is sponsored by Bottlenose, Endpoint, Booking.com, Perusion, West Branch Angler and M & D. Go to http://act.perl.dance for more information or contact us at 2014 at perl.dance. Regards Racke -- Perl and Dancer Development Visit our Perl::Dancer conference 2014: http://act.perl.dance/ From mike at nimbusrecording.com Wed Sep 10 19:39:41 2014 From: mike at nimbusrecording.com (Mike Schroeder) Date: Wed, 10 Sep 2014 11:39:41 -0700 Subject: [dancer-users] Looking for a developer... Message-ID: Hi all - I've been using Dancer for years and have watched this list for years - thank you to everyone for a great framework. In my new role at a new company (an audio engineering and production school), I searched for an off the shelf system to do what I wanted, and finally gave up and wrote my own. Dancer, Rose::DB::Object, Bootstrap and MySQL - amazing what you can do in 3-4 months of spare time :) The project is up and in production, running well, and now we are wanting to add more features, etc. I am too busy doing my real job (CEO) to have the time to do the development work on the system. I'm looking for someone who can can SSH into our servers from anywhere, work within my existing architecture to extend and add features, refactor some of my prototype code (it's not horrible, but I know it could be better), and help move the project forward. The ideal candidate would have experience with Dancer, Rose::DB::Object, Bootstrap and MySQL. There is also a POE-based daemon using Rose::DB::Object running alongside for long-running asynchronous job handling, so POE experience would be helpful as well. This is not a full-time job - more project based work to add new features, etc. I expect to keep building this out over the next year, so I'm looking for a good long term partner to work with. I'm ok with different timezones, as long as we can find some common time for Skype etc. (I'm in Vancouver, so Pacific Timezone). If you are interested, you can send an email to mike at nimbusrecording dot com. Let me know your experience and expectations for payment. Thanks all - I really appreciate the Dancer community and what it allows us all to create. Best, Mike. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ra.jones at dpw.clara.co.uk Wed Sep 10 20:19:09 2014 From: ra.jones at dpw.clara.co.uk (Richard Jones) Date: Wed, 10 Sep 2014 20:19:09 +0100 Subject: [dancer-users] Looking for a developer... In-Reply-To: References: Message-ID: <5410A42D.7040405@dpw.clara.co.uk> Hello Mike, I was very interested to read about your experience. I'm not touting for the job as I have a full-time job already. But just to say I'm a recent convert to Dancer2 from developing long-term with CGI::Application/RBDO/MySQL. I'm most interested in how you integrated Rose with Dancer. I haven't tried it yet as all my recent apps are small enough to use DBIx::Simple, but I'm planning a bigger one that will need an ORM. Do you use the MVC architecture? Do you use an adapter class for Rose or just rely on the Dancer DB plugin? Is your project open source or are you not able to expose the code base publicly? Good luck recruiting. On 10/09/2014 19:39, Mike Schroeder wrote: > Hi all - I've been using Dancer for years and have watched this list > for years - thank you to everyone for a great framework. > > In my new role at a new company (an audio engineering and production > school), I searched for an off the shelf system to do what I wanted, > and finally gave up and wrote my own. Dancer, Rose::DB::Object, > Bootstrap and MySQL - amazing what you can do in 3-4 months of spare > time :) > > The project is up and in production, running well, and now we are > wanting to add more features, etc. I am too busy doing my real job > (CEO) to have the time to do the development work on the system. > > I'm looking for someone who can can SSH into our servers from > anywhere, work within my existing architecture to extend and add > features, refactor some of my prototype code (it's not horrible, but I > know it could be better), and help move the project forward. > > The ideal candidate would have experience with Dancer, > Rose::DB::Object, Bootstrap and MySQL. There is also a POE-based > daemon using Rose::DB::Object running alongside for long-running > asynchronous job handling, so POE experience would be helpful as well. > > This is not a full-time job - more project based work to add new > features, etc. I expect to keep building this out over the next year, > so I'm looking for a good long term partner to work with. I'm ok with > different timezones, as long as we can find some common time for Skype > etc. (I'm in Vancouver, so Pacific Timezone). > > If you are interested, you can send an email to mike at > nimbusrecording dot com. Let me know your experience and expectations > for payment. > > Thanks all - I really appreciate the Dancer community and what it > allows us all to create. > > Best, > > Mike. > > > > _______________________________________________ > dancer-users mailing list > dancer-users at dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users -- Richard Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: From mike at nimbusrecording.com Wed Sep 10 21:00:51 2014 From: mike at nimbusrecording.com (Mike Schroeder) Date: Wed, 10 Sep 2014 13:00:51 -0700 Subject: [dancer-users] Looking for a developer... In-Reply-To: <5410A42D.7040405@dpw.clara.co.uk> References: <5410A42D.7040405@dpw.clara.co.uk> Message-ID: Hi Richard - not sure mine is the most elegant approach vis a vi plugins - but it is working, and it is fast :) For production I'm running multiple instances of Dancer with shared memcached for session management, all behind balance. This is all on a 12-core OS X Mavericks box and barely makes a blip on utilization. 1) I generated all the Rose::DB::Object classes from the MySQL schema for the RDBO classes and Manager classes. 2) I wrote a few helper functions to convert DBO objects in hash or array of hash suitable for Dancer templating (I'll copy those in below). I still use HTML::Template over TT just so that I can have non-coder HTML designers work with the templates, so these data structures work for that template engine. The result is a route that looks like this: #---------------------------------------------------------------------- get '/modal/points/:student_id' => sub { #---------------------------------------------------------------------- my $student = NDB::Student->new( id => params->{student_id} )->load; my $rv = dbo2h($student); template "staff/modal/points", $rv, {layout => "simple"}; }; Here are a few other sample routes: #---------------------------------------------------------------------- post '/studio' => sub { #---------------------------------------------------------------------- my @fields = ( qw( studio_name campus_id location session_rate calendar_id ) ); dbo_add_update("NDB::Studio", { params }, \@fields ); redirect "/admin/campus"; }; #---------------------------------------------------------------------- post '/studio/delete' => sub { #---------------------------------------------------------------------- my $p = NDB::Studio->new( id => params->{id} ); if ( params->{id} == params->{confirm_id} ) { $p->delete; } redirect "/admin/campus"; }; I also have some other helpers that follow RDBO relationships and inflate the data structures for templating: #---------------------------------------------------------------------- get '/campus' => sub { #---------------------------------------------------------------------- my $campuses = NDB::Campus::Manager->get_campus(); my $rv = dbom2aoh( $campuses, { studios => 'studio_list', staff => 'staff_list', } ); template "admin/campus", { campus_list => $rv, add_navbar() }, { layout => 'staff'}; }; 3) The helper functions help glue Dancer and RDBO together: =head2 dbo2h() dbo2h - convert a DBO object into a hash of key/value pairs. my $hashref = dbo2h( $dboobject, $date_format_string, $expandhash, $prepend ); =cut sub dbo2h { my $row = shift; my $date_format = shift || '%Y-%m-%d %T'; my $expand = shift; my $prepend = shift; my $parent_prepend = shift; my %hash = $row->column_value_pairs; foreach my $key ( keys %$expand ) { my $reln = $expand->{$key}; if ( $prepend ) { $hash{$reln . '_' . $key} = ( $row->$reln ? $row->$reln->$key : '' ); } else { $hash{$key} = ( $row->$reln ? $row->$reln->$key : ''); } } foreach my $key ( keys %hash ) { if ( ref $hash{$key} eq 'DateTime' ) { $hash{$key} = $hash{$key}->strftime($date_format); } elsif ( ref $hash{$key} eq 'Time::Clock' ) { $hash{$key} = $hash{$key}->as_string; } $hash{$key} =~ s/\s+$//g; if ( $parent_prepend ) { $hash{$parent_prepend.'_'.$key} = delete $hash{$key}; } } return \%hash; } =head2 dbo2aoh() dbo2aoh - convert a DBO set of objects into an array of hash of key/value pairs. my $arrayref = dbo2aoh( $dboarray, $date_format_string, $expandhash, $prepend ); =cut sub dbo2aoh { my $rows = shift; my $date_format = shift; my $expandhash = shift; my $prepend = shift; my $parent_prepend = shift; my @results; foreach my $row ( @$rows ) { push(@results, dbo2h( $row, $date_format, $expandhash, $prepend, $parent_prepend ) ); } return \@results; } =head2 dbo_add_update() dbo_add_update - convert Dancer params into DBO add/update my @fields = ( qw( field1 field2 field3 ) ); @errors = dbo_update( 'NDB::Lecture', { params }, \@fields, ); =cut sub dbo_add_update { my ( $class, $p, $fields ) = @_; my ( $obj, @errors ); if ( $p->{id} ) { $obj = $class->new( id => $p->{id} ); push(@errors, "No such record") unless $obj->load_speculative; unless ( @errors ) { foreach my $field ( @$fields ) { $obj->$field( $p->{$field} ) if exists $p->{$field}; } $obj->save; } } else { my %columns; foreach my $field ( @$fields ) { $columns{$field} = $p->{$field} if exists $p->{$field}; } $obj = $class->new( %columns ); $obj->save; } return $obj; } =head2 dbom2aoh() dbom2row - convert dbo to AOH and add DBOM relationships as child AOH $rv = dbo_update( $dbo, { relationship => 'hash_key' }, $date_format_string, $expandhash, $prepend ); =cut sub dbom2aoh { my ( $parent, $map, $dateformat, $expand, $prepend ) = @_; my @rv; foreach my $dbo ( @$parent ) { my $row = dbo2h( $dbo, $dateformat, $expand, $prepend ); foreach my $reln ( keys %$map ) { my $children = $dbo->$reln; $row->{ $map->{$reln} } = dbo2aoh( $children, $dateformat ); } push @rv, $row; } return \@rv; } Like I said in my initial post - I'm sure there are refactor opportunities in my code - so please be kind :) I tried to go for readability over conciseness so that I could hand it off at some point. Hope that helps. Best, Mike. On Wed, Sep 10, 2014 at 12:19 PM, Richard Jones wrote: > Hello Mike, > > I was very interested to read about your experience. I'm not touting for > the job as I have a full-time job already. But just to say I'm a recent > convert to Dancer2 from developing long-term with > CGI::Application/RBDO/MySQL. I'm most interested in how you integrated Rose > with Dancer. I haven't tried it yet as all my recent apps are small enough > to use DBIx::Simple, but I'm planning a bigger one that will need an ORM. > Do you use the MVC architecture? Do you use an adapter class for Rose or > just rely on the Dancer DB plugin? Is your project open source or are you > not able to expose the code base publicly? > > Good luck recruiting. > > > On 10/09/2014 19:39, Mike Schroeder wrote: > > Hi all - I've been using Dancer for years and have watched this list > for years - thank you to everyone for a great framework. > > In my new role at a new company (an audio engineering and production > school), I searched for an off the shelf system to do what I wanted, and > finally gave up and wrote my own. Dancer, Rose::DB::Object, Bootstrap and > MySQL - amazing what you can do in 3-4 months of spare time :) > > The project is up and in production, running well, and now we are > wanting to add more features, etc. I am too busy doing my real job (CEO) > to have the time to do the development work on the system. > > I'm looking for someone who can can SSH into our servers from anywhere, > work within my existing architecture to extend and add features, refactor > some of my prototype code (it's not horrible, but I know it could be > better), and help move the project forward. > > The ideal candidate would have experience with Dancer, Rose::DB::Object, > Bootstrap and MySQL. There is also a POE-based daemon using > Rose::DB::Object running alongside for long-running asynchronous job > handling, so POE experience would be helpful as well. > > This is not a full-time job - more project based work to add new > features, etc. I expect to keep building this out over the next year, so > I'm looking for a good long term partner to work with. I'm ok with > different timezones, as long as we can find some common time for Skype etc. > (I'm in Vancouver, so Pacific Timezone). > > If you are interested, you can send an email to mike at nimbusrecording > dot com. Let me know your experience and expectations for payment. > > Thanks all - I really appreciate the Dancer community and what it allows > us all to create. > > Best, > > Mike. > > > > _______________________________________________ > dancer-users mailing listdancer-users at dancer.pmhttp://lists.preshweb.co.uk/mailman/listinfo/dancer-users > > > -- > Richard Jones > > > _______________________________________________ > dancer-users mailing list > dancer-users at dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From darren at darrenduncan.net Thu Sep 11 07:58:18 2014 From: darren at darrenduncan.net (Darren Duncan) Date: Wed, 10 Sep 2014 23:58:18 -0700 Subject: [dancer-users] Looking for a developer... In-Reply-To: References: Message-ID: <5411480A.3090807@darrenduncan.net> Mike, I strongly recommend you switch your project to PostgreSQL from MySQL while it is still relatively young and small, so that you can grow with the better DBMS rather than putting more energy into the current one. You won't regret changing, and it will make it easier to grow after. -- Darren Duncan On 2014-09-10, 11:39 AM, Mike Schroeder wrote: > Hi all - I've been using Dancer for years and have watched this list for years - > thank you to everyone for a great framework. > > In my new role at a new company (an audio engineering and production school), I > searched for an off the shelf system to do what I wanted, and finally gave up > and wrote my own. Dancer, Rose::DB::Object, Bootstrap and MySQL - amazing what > you can do in 3-4 months of spare time :) > > The project is up and in production, running well, and now we are wanting to add > more features, etc. I am too busy doing my real job (CEO) to have the time to > do the development work on the system. > > I'm looking for someone who can can SSH into our servers from anywhere, work > within my existing architecture to extend and add features, refactor some of my > prototype code (it's not horrible, but I know it could be better), and help move > the project forward. > > The ideal candidate would have experience with Dancer, Rose::DB::Object, > Bootstrap and MySQL. There is also a POE-based daemon using Rose::DB::Object > running alongside for long-running asynchronous job handling, so POE experience > would be helpful as well. > > This is not a full-time job - more project based work to add new features, etc. > I expect to keep building this out over the next year, so I'm looking for a > good long term partner to work with. I'm ok with different timezones, as long as > we can find some common time for Skype etc. (I'm in Vancouver, so Pacific Timezone). > > If you are interested, you can send an email to mike at nimbusrecording dot com. > Let me know your experience and expectations for payment. > > Thanks all - I really appreciate the Dancer community and what it allows us all > to create. > > Best, > > Mike. From darren at darrenduncan.net Thu Sep 11 08:01:49 2014 From: darren at darrenduncan.net (Darren Duncan) Date: Thu, 11 Sep 2014 00:01:49 -0700 Subject: [dancer-users] Looking for a developer... In-Reply-To: <5411480A.3090807@darrenduncan.net> References: <5411480A.3090807@darrenduncan.net> Message-ID: <541148DD.8050204@darrenduncan.net> On 2014-09-10, 11:58 PM, Darren Duncan wrote: > Mike, I strongly recommend you switch your project to PostgreSQL from MySQL > while it is still relatively young and small, so that you can grow with the > better DBMS rather than putting more energy into the current one. You won't > regret changing, and it will make it easier to grow after. -- Darren Duncan Further to my point, since you have an asynchronous model, Postgres' built in LISTEN/NOTIFY feature, natively supported by DBD::Pg, should be very useful to you. -- Darren Duncan > On 2014-09-10, 11:39 AM, Mike Schroeder wrote: >> Hi all - I've been using Dancer for years and have watched this list for years - >> thank you to everyone for a great framework. >> >> In my new role at a new company (an audio engineering and production school), I >> searched for an off the shelf system to do what I wanted, and finally gave up >> and wrote my own. Dancer, Rose::DB::Object, Bootstrap and MySQL - amazing what >> you can do in 3-4 months of spare time :) >> >> The project is up and in production, running well, and now we are wanting to add >> more features, etc. I am too busy doing my real job (CEO) to have the time to >> do the development work on the system. >> >> I'm looking for someone who can can SSH into our servers from anywhere, work >> within my existing architecture to extend and add features, refactor some of my >> prototype code (it's not horrible, but I know it could be better), and help move >> the project forward. >> >> The ideal candidate would have experience with Dancer, Rose::DB::Object, >> Bootstrap and MySQL. There is also a POE-based daemon using Rose::DB::Object >> running alongside for long-running asynchronous job handling, so POE experience >> would be helpful as well. >> >> This is not a full-time job - more project based work to add new features, etc. >> I expect to keep building this out over the next year, so I'm looking for a >> good long term partner to work with. I'm ok with different timezones, as long as >> we can find some common time for Skype etc. (I'm in Vancouver, so Pacific >> Timezone). >> >> If you are interested, you can send an email to mike at nimbusrecording dot com. >> Let me know your experience and expectations for payment. >> >> Thanks all - I really appreciate the Dancer community and what it allows us all >> to create. >> >> Best, >> >> Mike. From hugues at max4mail.com Thu Sep 11 08:02:27 2014 From: hugues at max4mail.com (Hugues) Date: Thu, 11 Sep 2014 09:02:27 +0200 Subject: [dancer-users] Dancer 1 v1.3127 on its way to CPAN In-Reply-To: <540E4FA6.1090505@babyl.dyndns.org> References: <540E4FA6.1090505@babyl.dyndns.org> Message-ID: <54114903.6070704@max4mail.com> Thanks Yanick Update is done cpanm Dancer --> Working on Dancer Fetching http://www.cpan.org/authors/id/Y/YA/YANICK/Dancer-1.3129.tar.gz ... OK Configuring Dancer-1.3129 ... OK Building and testing Dancer-1.3129 ... OK Successfully installed Dancer-1.3129 (upgraded from 1.3125) 1 distribution installed All is ok for me bye Hugues. Le 09/09/2014 02:53, Yanick Champoux a ?crit : > Hi all! > > A new version of Dancer 1 is on its way to CPAN as we speak -- the > changelog is provided below for your pleasure. > > As usual, a big thank to everyone who pitched in. You're all > wonderful, wonderful people. :-) > > Joy, > `/anick > > 1.3127 2014-09-08 > [BUG FIXES] > - Test was using deprecated 'import_warnings'. (GH#1045, mokko) > - Fix default test names for headers and redirection test methods. > (GH#1048, odyniec) > - DANCER_SERVER_TOKENS and DANCER_SESSION_INFO are now > DANCER_NO_SERVER_TOKENS and DANCER_NO_SESSION_INFO. And working. :-) > (GH#1014, Yanick Champoux) > - 'any' wasn't understanding 'del' (only 'delete'). (GH#1044, Yanick > Champoux) > > [DISTRIBUTION] > - Now using Dist::Zilla as package manager. > > [DOCUMENTATION] > - Correct POD formatting for HTTP methods in introduction.pod. > (GH#1047, Lx) > > [ENHANCEMENTS] > - environment configs are now merged with the global config, versus the > previous behavior that was overriding the whole config segments. > (GH#1016, Yanick Champoux) > - Dancer::Handler::Debug now accepts env variables from the > command-line. (GH#1056, Yanick Champoux) > - Accessing values abstracted as methods in Dancer::Session. (GH#1000, > John Wittkoski) > _______________________________________________ > dancer-users mailing list > dancer-users at dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users From ra.jones at dpw.clara.co.uk Thu Sep 11 10:52:05 2014 From: ra.jones at dpw.clara.co.uk (Richard Jones) Date: Thu, 11 Sep 2014 10:52:05 +0100 Subject: [dancer-users] Looking for a developer... In-Reply-To: References: <5410A42D.7040405@dpw.clara.co.uk> Message-ID: <541170C5.6040303@dpw.clara.co.uk> Thanks for the examples Mike. I see you are calling and manipulating your RBDO classes directly in your routes. That answers my integration question. I tend to keep all that stuff in separate model classes so that I could change ORM to say DBIX::Class without any change to the D2 classes. But it does increase complexity. Just a thought regarding the expansion helpers - you don't utilise the as_tree() function anywhere? I realise your helpers do more than just simple object-to-hash conversion. my $rv = dbo2h($student); my $rv = $student->as_tree; my $rv = $student->as_tree(deflate => 0); # to keep eg DateTime objects On 10/09/2014 21:00, Mike Schroeder wrote: > Hi Richard - not sure mine is the most elegant approach vis a vi > plugins - but it is working, and it is fast :) For production I'm > running multiple instances of Dancer with shared memcached for session > management, all behind balance. This is all on a 12-core OS X > Mavericks box and barely makes a blip on utilization. > > 1) I generated all the Rose::DB::Object classes from the MySQL schema > for the RDBO classes and Manager classes. > > 2) I wrote a few helper functions to convert DBO objects in hash or > array of hash suitable for Dancer templating (I'll copy those in > below). I still use HTML::Template over TT just so that I can have > non-coder HTML designers work with the templates, so these data > structures work for that template engine. The result is a route that > looks like this: > > #---------------------------------------------------------------------- > get '/modal/points/:student_id' => sub { > #---------------------------------------------------------------------- > my $student = NDB::Student->new( id => params->{student_id} )->load; > my $rv = dbo2h($student); > template "staff/modal/points", $rv, {layout => "simple"}; > }; > > Here are a few other sample routes: > > #---------------------------------------------------------------------- > post '/studio' => sub { > #---------------------------------------------------------------------- > my @fields = ( qw( studio_name campus_id location session_rate > calendar_id ) ); > dbo_add_update("NDB::Studio", { params }, \@fields ); > redirect "/admin/campus"; > }; > > #---------------------------------------------------------------------- > post '/studio/delete' => sub { > #---------------------------------------------------------------------- > my $p = NDB::Studio->new( id => params->{id} ); > if ( params->{id} == params->{confirm_id} ) { > $p->delete; > } > redirect "/admin/campus"; > }; > > I also have some other helpers that follow RDBO relationships and > inflate the data structures for templating: > > #---------------------------------------------------------------------- > get '/campus' => sub { > #---------------------------------------------------------------------- > my $campuses = NDB::Campus::Manager->get_campus(); > my $rv = dbom2aoh( $campuses, { studios => 'studio_list', staff > => 'staff_list', } ); > template "admin/campus", { campus_list => $rv, add_navbar() }, { > layout => 'staff'}; > }; > > > 3) The helper functions help glue Dancer and RDBO together: > > > =head2 dbo2h() > > dbo2h - convert a DBO object into a hash of key/value pairs. > > my $hashref = dbo2h( $dboobject, $date_format_string, $expandhash, > $prepend ); > > =cut > > sub dbo2h { > my $row = shift; > my $date_format = shift || '%Y-%m-%d %T'; > my $expand = shift; > my $prepend = shift; > my $parent_prepend = shift; > my %hash = $row->column_value_pairs; > foreach my $key ( keys %$expand ) { > my $reln = $expand->{$key}; > if ( $prepend ) { > $hash{$reln . '_' . $key} = ( $row->$reln ? $row->$reln->$key > : '' ); > } else { > $hash{$key} = ( $row->$reln ? $row->$reln->$key : ''); > } > } > foreach my $key ( keys %hash ) { > if ( ref $hash{$key} eq 'DateTime' ) { > $hash{$key} = $hash{$key}->strftime($date_format); > } > elsif ( ref $hash{$key} eq 'Time::Clock' ) { > $hash{$key} = $hash{$key}->as_string; > } > $hash{$key} =~ s/\s+$//g; > if ( $parent_prepend ) { > $hash{$parent_prepend.'_'.$key} = delete $hash{$key}; > } > } > return \%hash; > } > > =head2 dbo2aoh() > > dbo2aoh - convert a DBO set of objects into an array of hash of > key/value pairs. > > my $arrayref = dbo2aoh( $dboarray, $date_format_string, > $expandhash, $prepend ); > > =cut > > sub dbo2aoh { > my $rows = shift; > my $date_format = shift; > my $expandhash = shift; > my $prepend = shift; > my $parent_prepend = shift; > my @results; > foreach my $row ( @$rows ) { > push(@results, dbo2h( $row, $date_format, $expandhash, $prepend, > $parent_prepend ) ); > } > return \@results; > } > > > =head2 dbo_add_update() > > dbo_add_update - convert Dancer params into DBO add/update > > my @fields = ( qw( field1 field2 field3 ) ); > @errors = dbo_update( 'NDB::Lecture', { params }, \@fields, ); > > =cut > > sub dbo_add_update { > my ( $class, $p, $fields ) = @_; > my ( $obj, @errors ); > > if ( $p->{id} ) { > $obj = $class->new( id => $p->{id} ); > push(@errors, "No such record") unless $obj->load_speculative; > > unless ( @errors ) { > foreach my $field ( @$fields ) { > $obj->$field( $p->{$field} ) if exists $p->{$field}; > } > $obj->save; > } > } else { > my %columns; > foreach my $field ( @$fields ) { > $columns{$field} = $p->{$field} if exists $p->{$field}; > } > $obj = $class->new( %columns ); > $obj->save; > } > return $obj; > } > > =head2 dbom2aoh() > > dbom2row - convert dbo to AOH and add DBOM relationships as child AOH > > $rv = dbo_update( $dbo, { relationship => 'hash_key' }, > $date_format_string, $expandhash, $prepend ); > > =cut > > sub dbom2aoh { > my ( $parent, $map, $dateformat, $expand, $prepend ) = @_; > my @rv; > foreach my $dbo ( @$parent ) { > my $row = dbo2h( $dbo, $dateformat, $expand, $prepend ); > foreach my $reln ( keys %$map ) { > my $children = $dbo->$reln; > $row->{ $map->{$reln} } = dbo2aoh( $children, $dateformat ); > } > push @rv, $row; > } > return \@rv; > } > > Like I said in my initial post - I'm sure there are refactor > opportunities in my code - so please be kind :) I tried to go for > readability over conciseness so that I could hand it off at some point. > > Hope that helps. > > Best, > > Mike. > > > > On Wed, Sep 10, 2014 at 12:19 PM, Richard Jones > > wrote: > > Hello Mike, > > I was very interested to read about your experience. I'm not > touting for the job as I have a full-time job already. But just to > say I'm a recent convert to Dancer2 from developing long-term with > CGI::Application/RBDO/MySQL. I'm most interested in how you > integrated Rose with Dancer. I haven't tried it yet as all my > recent apps are small enough to use DBIx::Simple, but I'm planning > a bigger one that will need an ORM. Do you use the MVC > architecture? Do you use an adapter class for Rose or just rely on > the Dancer DB plugin? Is your project open source or are you not > able to expose the code base publicly? > > Good luck recruiting. > > > On 10/09/2014 19:39, Mike Schroeder wrote: >> Hi all - I've been using Dancer for years and have watched this >> list for years - thank you to everyone for a great framework. >> >> In my new role at a new company (an audio engineering and >> production school), I searched for an off the shelf system to do >> what I wanted, and finally gave up and wrote my own. Dancer, >> Rose::DB::Object, Bootstrap and MySQL - amazing what you can do >> in 3-4 months of spare time :) >> >> The project is up and in production, running well, and now we are >> wanting to add more features, etc. I am too busy doing my real >> job (CEO) to have the time to do the development work on the system. >> >> I'm looking for someone who can can SSH into our servers from >> anywhere, work within my existing architecture to extend and add >> features, refactor some of my prototype code (it's not horrible, >> but I know it could be better), and help move the project forward. >> >> The ideal candidate would have experience with Dancer, >> Rose::DB::Object, Bootstrap and MySQL. There is also a POE-based >> daemon using Rose::DB::Object running alongside for long-running >> asynchronous job handling, so POE experience would be helpful as >> well. >> >> This is not a full-time job - more project based work to add new >> features, etc. I expect to keep building this out over the next >> year, so I'm looking for a good long term partner to work with. >> I'm ok with different timezones, as long as we can find some >> common time for Skype etc. (I'm in Vancouver, so Pacific Timezone). >> >> If you are interested, you can send an email to mike at >> nimbusrecording dot com. Let me know your experience and >> expectations for payment. >> >> Thanks all - I really appreciate the Dancer community and what it >> allows us all to create. >> >> Best, >> >> Mike. >> >> >> >> _______________________________________________ >> dancer-users mailing list >> dancer-users at dancer.pm >> http://lists.preshweb.co.uk/mailman/listinfo/dancer-users > > -- > Richard Jones > > > _______________________________________________ > dancer-users mailing list > dancer-users at dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users > > > > > _______________________________________________ > dancer-users mailing list > dancer-users at dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users -- Richard Jones -------------- next part -------------- An HTML attachment was scrubbed... URL: From yanick at babyl.dyndns.org Thu Sep 11 14:23:01 2014 From: yanick at babyl.dyndns.org (Yanick Champoux) Date: Thu, 11 Sep 2014 09:23:01 -0400 Subject: [dancer-users] Dancer 1 v1.3127 on its way to CPAN In-Reply-To: <54114903.6070704@max4mail.com> References: <540E4FA6.1090505@babyl.dyndns.org> <54114903.6070704@max4mail.com> Message-ID: <5411A235.8010700@babyl.dyndns.org> On 14-09-11 03:02 AM, Hugues wrote: > Update is done > > cpanm Dancer > --> Working on Dancer > Fetching http://www.cpan.org/authors/id/Y/YA/YANICK/Dancer-1.3129.tar.gz > ... > > All is ok for me Excellent. As you might have noticed, two other releases went out in quick succession because the dzil conversion made two booboos (a bogus dependency and the 'dancer' script went awol for a moment). Fortunately, eagle-eyed users warned me within hours of the releases, and I was able to fix everything pretty quickly. :-) Enjoy! `/anick From xsawyerx at gmail.com Thu Sep 11 16:46:22 2014 From: xsawyerx at gmail.com (Sawyer X) Date: Thu, 11 Sep 2014 17:46:22 +0200 Subject: [dancer-users] Dancer2 Roadmap - your help needed! Message-ID: Hey everyone, we're working on creating the Dancer2 roadmap. We need your help! We want to design it with you, and we want to know: * What do you think should be on the roadmap for Dancer2? * What do you like to see being done? * What would you help with, if it was on the plan? As the last item suggests, we're interesting in getting much more help with implementing this plan, once we have it written, so expect many "call to action"s. :) Let's open a discussion! -------------- next part -------------- An HTML attachment was scrubbed... URL: From tmurray at wumpus-cave.net Thu Sep 11 18:23:02 2014 From: tmurray at wumpus-cave.net (Timm Murray) Date: Thu, 11 Sep 2014 12:23:02 -0500 Subject: [dancer-users] Dancer2 Roadmap - your help needed! In-Reply-To: References: Message-ID: One of my big projects right now involves streaming a live webcam into an HTML5 video stream, which means it needs to stream a filehandle. I have a bug in the system to implement this in send_file(): https://github.com/PerlDancer/Dancer2/issues/659 I ended up backporting to Dancer1 because of hitting this. Even better would be to have a simple function call that takes a filehandle directly and streams it without needed to specify callbacks. A smaller issue is to have an easy way to disable splat behavior. I'm reimplementing an existing REST API that has some literal '*' in many of the calls. With things on Dancer1, I was able to get it to work with a regex match, though that didn't seem to work when I tried it on Dancer2. Either way, a regex seems like an unnecessarily complicated way of solving this. Thanks, Timm On Thu, Sep 11, 2014 at 10:46 AM, Sawyer X wrote: > Hey everyone, > > we're working on creating the Dancer2 roadmap. We need your help! > > We want to design it with you, and we want to know: > * What do you think should be on the roadmap for Dancer2? > * What do you like to see being done? > * What would you help with, if it was on the plan? > > As the last item suggests, we're interesting in getting much more help > with implementing this plan, once we have it written, so expect many "call > to action"s. :) > > Let's open a discussion! > > _______________________________________________ > dancer-users mailing list > dancer-users at dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tmurray at wumpus-cave.net Thu Sep 11 18:28:25 2014 From: tmurray at wumpus-cave.net (Timm Murray) Date: Thu, 11 Sep 2014 12:28:25 -0500 Subject: [dancer-users] Dancer2 Roadmap - your help needed! In-Reply-To: References: Message-ID: I should add that this is my first Real Dancer Project, so maybe I'm just missing something. On Thu, Sep 11, 2014 at 12:23 PM, Timm Murray wrote: > One of my big projects right now involves streaming a live webcam into an > HTML5 video stream, which means it needs to stream a filehandle. I have a > bug in the system to implement this in send_file(): > > https://github.com/PerlDancer/Dancer2/issues/659 > > I ended up backporting to Dancer1 because of hitting this. > > Even better would be to have a simple function call that takes a > filehandle directly and streams it without needed to specify callbacks. > > A smaller issue is to have an easy way to disable splat behavior. I'm > reimplementing an existing REST API that has some literal '*' in many of > the calls. With things on Dancer1, I was able to get it to work with a > regex match, though that didn't seem to work when I tried it on Dancer2. > Either way, a regex seems like an unnecessarily complicated way of solving > this. > > Thanks, > Timm > > > On Thu, Sep 11, 2014 at 10:46 AM, Sawyer X wrote: > >> Hey everyone, >> >> we're working on creating the Dancer2 roadmap. We need your help! >> >> We want to design it with you, and we want to know: >> * What do you think should be on the roadmap for Dancer2? >> * What do you like to see being done? >> * What would you help with, if it was on the plan? >> >> As the last item suggests, we're interesting in getting much more help >> with implementing this plan, once we have it written, so expect many "call >> to action"s. :) >> >> Let's open a discussion! >> >> _______________________________________________ >> dancer-users mailing list >> dancer-users at dancer.pm >> http://lists.preshweb.co.uk/mailman/listinfo/dancer-users >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From gabor at szabgab.com Thu Sep 11 18:28:42 2014 From: gabor at szabgab.com (Gabor Szabo) Date: Thu, 11 Sep 2014 20:28:42 +0300 Subject: [dancer-users] Dancer2 Roadmap - your help needed! In-Reply-To: References: Message-ID: Can multiple Dancer2 applications launched in the same Starman already? If not, then that would be an important one. IMHO. Gabor -------------- next part -------------- An HTML attachment was scrubbed... URL: From mike at nimbusrecording.com Thu Sep 11 19:05:35 2014 From: mike at nimbusrecording.com (Mike Schroeder) Date: Thu, 11 Sep 2014 11:05:35 -0700 Subject: [dancer-users] Looking for a developer... In-Reply-To: <541170C5.6040303@dpw.clara.co.uk> References: <5410A42D.7040405@dpw.clara.co.uk> <541170C5.6040303@dpw.clara.co.uk> Message-ID: Thanks Richard - to be honest I'm not sure why I didn't take advantage of as_tree() - I've been using my dbo2aoh helpers for so many years I got stuck in a rut. Good feedback on the abstraction. I was in a bit of a hurry to knock this one off, and as Winston Churchill said, "I didn't have the time to write you a shorter letter". Best, Mike. On Thu, Sep 11, 2014 at 2:52 AM, Richard Jones wrote: > Thanks for the examples Mike. I see you are calling and manipulating your > RBDO classes directly in your routes. That answers my integration question. > I tend to keep all that stuff in separate model classes so that I could > change ORM to say DBIX::Class without any change to the D2 classes. But it > does increase complexity. Just a thought regarding the expansion helpers - > you don't utilise the as_tree() function anywhere? I realise your helpers > do more than just simple object-to-hash conversion. > > my $rv = dbo2h($student); > my $rv = $student->as_tree; > my $rv = $student->as_tree(deflate => 0); # to keep eg DateTime objects > > On 10/09/2014 21:00, Mike Schroeder wrote: > > Hi Richard - not sure mine is the most elegant approach vis a vi plugins - > but it is working, and it is fast :) For production I'm running multiple > instances of Dancer with shared memcached for session management, all > behind balance. This is all on a 12-core OS X Mavericks box and barely > makes a blip on utilization. > > 1) I generated all the Rose::DB::Object classes from the MySQL schema > for the RDBO classes and Manager classes. > > 2) I wrote a few helper functions to convert DBO objects in hash or > array of hash suitable for Dancer templating (I'll copy those in below). I > still use HTML::Template over TT just so that I can have non-coder HTML > designers work with the templates, so these data structures work for that > template engine. The result is a route that looks like this: > > #---------------------------------------------------------------------- > get '/modal/points/:student_id' => sub { > #---------------------------------------------------------------------- > my $student = NDB::Student->new( id => params->{student_id} )->load; > my $rv = dbo2h($student); > template "staff/modal/points", $rv, {layout => "simple"}; > }; > > Here are a few other sample routes: > > #---------------------------------------------------------------------- > post '/studio' => sub { > #---------------------------------------------------------------------- > my @fields = ( qw( studio_name campus_id location session_rate > calendar_id ) ); > dbo_add_update("NDB::Studio", { params }, \@fields ); > redirect "/admin/campus"; > }; > > #---------------------------------------------------------------------- > post '/studio/delete' => sub { > #---------------------------------------------------------------------- > my $p = NDB::Studio->new( id => params->{id} ); > if ( params->{id} == params->{confirm_id} ) { > $p->delete; > } > redirect "/admin/campus"; > }; > > I also have some other helpers that follow RDBO relationships and > inflate the data structures for templating: > > #---------------------------------------------------------------------- > get '/campus' => sub { > #---------------------------------------------------------------------- > my $campuses = NDB::Campus::Manager->get_campus(); > my $rv = dbom2aoh( $campuses, { studios => 'studio_list', staff => > 'staff_list', } ); > template "admin/campus", { campus_list => $rv, add_navbar() }, { layout > => 'staff'}; > }; > > > 3) The helper functions help glue Dancer and RDBO together: > > > =head2 dbo2h() > > dbo2h - convert a DBO object into a hash of key/value pairs. > > my $hashref = dbo2h( $dboobject, $date_format_string, $expandhash, > $prepend ); > > =cut > > sub dbo2h { > my $row = shift; > my $date_format = shift || '%Y-%m-%d %T'; > my $expand = shift; > my $prepend = shift; > my $parent_prepend = shift; > my %hash = $row->column_value_pairs; > foreach my $key ( keys %$expand ) { > my $reln = $expand->{$key}; > if ( $prepend ) { > $hash{$reln . '_' . $key} = ( $row->$reln ? $row->$reln->$key : > '' ); > } else { > $hash{$key} = ( $row->$reln ? $row->$reln->$key : ''); > } > } > foreach my $key ( keys %hash ) { > if ( ref $hash{$key} eq 'DateTime' ) { > $hash{$key} = $hash{$key}->strftime($date_format); > } > elsif ( ref $hash{$key} eq 'Time::Clock' ) { > $hash{$key} = $hash{$key}->as_string; > } > $hash{$key} =~ s/\s+$//g; > if ( $parent_prepend ) { > $hash{$parent_prepend.'_'.$key} = delete $hash{$key}; > } > } > return \%hash; > } > > =head2 dbo2aoh() > > dbo2aoh - convert a DBO set of objects into an array of hash of > key/value pairs. > > my $arrayref = dbo2aoh( $dboarray, $date_format_string, $expandhash, > $prepend ); > > =cut > > sub dbo2aoh { > my $rows = shift; > my $date_format = shift; > my $expandhash = shift; > my $prepend = shift; > my $parent_prepend = shift; > my @results; > foreach my $row ( @$rows ) { > push(@results, dbo2h( $row, $date_format, $expandhash, $prepend, > $parent_prepend ) ); > } > return \@results; > } > > > =head2 dbo_add_update() > > dbo_add_update - convert Dancer params into DBO add/update > > my @fields = ( qw( field1 field2 field3 ) ); > @errors = dbo_update( 'NDB::Lecture', { params }, \@fields, ); > > =cut > > sub dbo_add_update { > my ( $class, $p, $fields ) = @_; > my ( $obj, @errors ); > > if ( $p->{id} ) { > $obj = $class->new( id => $p->{id} ); > push(@errors, "No such record") unless $obj->load_speculative; > > unless ( @errors ) { > foreach my $field ( @$fields ) { > $obj->$field( $p->{$field} ) if exists $p->{$field}; > } > $obj->save; > } > } else { > my %columns; > foreach my $field ( @$fields ) { > $columns{$field} = $p->{$field} if exists $p->{$field}; > } > $obj = $class->new( %columns ); > $obj->save; > } > return $obj; > } > > =head2 dbom2aoh() > > dbom2row - convert dbo to AOH and add DBOM relationships as child AOH > > $rv = dbo_update( $dbo, { relationship => 'hash_key' }, > $date_format_string, $expandhash, $prepend ); > > =cut > > sub dbom2aoh { > my ( $parent, $map, $dateformat, $expand, $prepend ) = @_; > my @rv; > foreach my $dbo ( @$parent ) { > my $row = dbo2h( $dbo, $dateformat, $expand, $prepend ); > foreach my $reln ( keys %$map ) { > my $children = $dbo->$reln; > $row->{ $map->{$reln} } = dbo2aoh( $children, $dateformat ); > } > push @rv, $row; > } > return \@rv; > } > > Like I said in my initial post - I'm sure there are refactor > opportunities in my code - so please be kind :) I tried to go for > readability over conciseness so that I could hand it off at some point. > > Hope that helps. > > Best, > > Mike. > > > > On Wed, Sep 10, 2014 at 12:19 PM, Richard Jones > wrote: > >> Hello Mike, >> >> I was very interested to read about your experience. I'm not touting for >> the job as I have a full-time job already. But just to say I'm a recent >> convert to Dancer2 from developing long-term with >> CGI::Application/RBDO/MySQL. I'm most interested in how you integrated Rose >> with Dancer. I haven't tried it yet as all my recent apps are small enough >> to use DBIx::Simple, but I'm planning a bigger one that will need an ORM. >> Do you use the MVC architecture? Do you use an adapter class for Rose or >> just rely on the Dancer DB plugin? Is your project open source or are you >> not able to expose the code base publicly? >> >> Good luck recruiting. >> >> >> On 10/09/2014 19:39, Mike Schroeder wrote: >> >> Hi all - I've been using Dancer for years and have watched this list >> for years - thank you to everyone for a great framework. >> >> In my new role at a new company (an audio engineering and production >> school), I searched for an off the shelf system to do what I wanted, and >> finally gave up and wrote my own. Dancer, Rose::DB::Object, Bootstrap and >> MySQL - amazing what you can do in 3-4 months of spare time :) >> >> The project is up and in production, running well, and now we are >> wanting to add more features, etc. I am too busy doing my real job (CEO) >> to have the time to do the development work on the system. >> >> I'm looking for someone who can can SSH into our servers from anywhere, >> work within my existing architecture to extend and add features, refactor >> some of my prototype code (it's not horrible, but I know it could be >> better), and help move the project forward. >> >> The ideal candidate would have experience with Dancer, >> Rose::DB::Object, Bootstrap and MySQL. There is also a POE-based daemon >> using Rose::DB::Object running alongside for long-running asynchronous job >> handling, so POE experience would be helpful as well. >> >> This is not a full-time job - more project based work to add new >> features, etc. I expect to keep building this out over the next year, so >> I'm looking for a good long term partner to work with. I'm ok with >> different timezones, as long as we can find some common time for Skype etc. >> (I'm in Vancouver, so Pacific Timezone). >> >> If you are interested, you can send an email to mike at nimbusrecording >> dot com. Let me know your experience and expectations for payment. >> >> Thanks all - I really appreciate the Dancer community and what it >> allows us all to create. >> >> Best, >> >> Mike. >> >> >> >> _______________________________________________ >> dancer-users mailing listdancer-users at dancer.pmhttp://lists.preshweb.co.uk/mailman/listinfo/dancer-users >> >> >> -- >> Richard Jones >> >> >> _______________________________________________ >> dancer-users mailing list >> dancer-users at dancer.pm >> http://lists.preshweb.co.uk/mailman/listinfo/dancer-users >> >> > > > _______________________________________________ > dancer-users mailing listdancer-users at dancer.pmhttp://lists.preshweb.co.uk/mailman/listinfo/dancer-users > > > -- > Richard Jones > > > _______________________________________________ > dancer-users mailing list > dancer-users at dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From asb.cpan at gmail.com Thu Sep 11 20:58:59 2014 From: asb.cpan at gmail.com (Alex Becker) Date: Thu, 11 Sep 2014 21:58:59 +0200 Subject: [dancer-users] Dancer 1 or Dancer 2? Message-ID: Hi! I'm starting a smaller web application. Would it make sense to use Dancer 2 already? Best regards, Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: From jack.lareau at gmail.com Thu Sep 11 22:00:40 2014 From: jack.lareau at gmail.com (Jacques Lareau) Date: Thu, 11 Sep 2014 17:00:40 -0400 Subject: [dancer-users] Dancer2 Roadmap - your help needed! In-Reply-To: References: Message-ID: A style guide (mostly for plugins). I'm a big fan of johnpapa's AngularJS style guide . I think it would benefit mostly plugins development. If you take a look at 3 major plugins source: Database , REST and DBIC . 3 different ways to register keywords ( sub anonymous vs ref ). Different version and abstract declarations. die vs croak. Show keyword declarations at top or bottom? Maybe a style guide on how to decouple business logic from dancer routes (file splitting, modules for business). But I understand that style guide's are highly opinionated and may not suit every team or project. But a general one would be better than nothing in my opinion. Or maybe a style guide has nothing to do with Dancer2 core... On Thu, Sep 11, 2014 at 1:28 PM, Gabor Szabo wrote: > Can multiple Dancer2 applications launched in the same Starman already? If > not, then that would be an important one. IMHO. > > Gabor > > > _______________________________________________ > dancer-users mailing list > dancer-users at dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at vincew.net Thu Sep 11 22:18:23 2014 From: info at vincew.net (VinceW) Date: Thu, 11 Sep 2014 23:18:23 +0200 Subject: [dancer-users] Dancer2 Roadmap - your help needed! In-Reply-To: References: Message-ID: <5412119F.2070700@vincew.net> My 5cts disclaimer: Just (about 18 months) getting my feet wet with Perl/D1 (coming from PHP/framework environment) - mapping of current D1 modules against current D2 modules - priority listing of D1 modules needed to have in D2 - migration path from D1 -> D2 I would like to help the D1/D2 project. Having dev, git, linux experience, knowing a fraction of Perl (compared to others here on the list). Able to visit NL-PM and/or AmsterdamX.pm Willing to learn Best, VinceW On 09/11/2014 05:46 PM, Sawyer X wrote: > Hey everyone, > > we're working on creating the Dancer2 roadmap. We need your help! > > We want to design it with you, and we want to know: > * What do you think should be on the roadmap for Dancer2? > * What do you like to see being done? > * What would you help with, if it was on the plan? > > As the last item suggests, we're interesting in getting much more help with > implementing this plan, once we have it written, so expect many "call to > action"s. :) > > Let's open a discussion! > > > > _______________________________________________ > dancer-users mailing list > dancer-users at dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From xsawyerx at gmail.com Fri Sep 12 09:13:39 2014 From: xsawyerx at gmail.com (Sawyer X) Date: Fri, 12 Sep 2014 10:13:39 +0200 Subject: [dancer-users] Dancer2 Roadmap - your help needed! In-Reply-To: References: Message-ID: On Thu, Sep 11, 2014 at 7:28 PM, Gabor Szabo wrote: > Can multiple Dancer2 applications launched in the same Starman already? > Yup. -------------- next part -------------- An HTML attachment was scrubbed... URL: From xsawyerx at gmail.com Fri Sep 12 09:16:34 2014 From: xsawyerx at gmail.com (Sawyer X) Date: Fri, 12 Sep 2014 10:16:34 +0200 Subject: [dancer-users] Dancer2 Roadmap - your help needed! In-Reply-To: <5412119F.2070700@vincew.net> References: <5412119F.2070700@vincew.net> Message-ID: So I'm trying to think of how to aggregate all of these into a proper roadmap. We could add all of these as Github issues, or as Github wiki pages. My problem with doing it in issues is that it might conflate with bugs and feature requests. I'm actually not only interested in feature requests. I'm interesting in formalizing the direction Dancer2 is going in, and discussing how to get there. Eventually I want to end up with a document saying "This is where we're going and how". (for different values of "how" :) Thoughts? On Thu, Sep 11, 2014 at 11:18 PM, VinceW wrote: > My 5cts > > disclaimer: Just (about 18 months) getting my feet wet with Perl/D1 > (coming from PHP/framework environment) > > - mapping of current D1 modules against current D2 modules > - priority listing of D1 modules needed to have in D2 > - migration path from D1 -> D2 > > > I would like to help the D1/D2 project. > Having dev, git, linux experience, knowing a fraction of Perl (compared to > others here on the list). > Able to visit NL-PM and/or AmsterdamX.pm > Willing to learn > > Best, > VinceW > > > On 09/11/2014 05:46 PM, Sawyer X wrote: > > Hey everyone, > > we're working on creating the Dancer2 roadmap. We need your help! > > We want to design it with you, and we want to know: > * What do you think should be on the roadmap for Dancer2? > * What do you like to see being done? > * What would you help with, if it was on the plan? > > As the last item suggests, we're interesting in getting much more help with > implementing this plan, once we have it written, so expect many "call to > action"s. :) > > Let's open a discussion! > > > > > _______________________________________________ > dancer-users mailing listdancer-users at dancer.pmhttp://lists.preshweb.co.uk/mailman/listinfo/dancer-users > > > > _______________________________________________ > dancer-users mailing list > dancer-users at dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From xsawyerx at gmail.com Fri Sep 12 09:18:13 2014 From: xsawyerx at gmail.com (Sawyer X) Date: Fri, 12 Sep 2014 10:18:13 +0200 Subject: [dancer-users] Dancer 1 or Dancer 2? In-Reply-To: References: Message-ID: It depends on the features you want, and how much you're willing to put up with. :) Dancer2 is still not fully stable. Things are changing. However, it has some spiffier features and allows some things which weren't possible in D1. For the normal day-to-day stuff, it should perfectly fine. Hit us up with any issues you find! :) On Thu, Sep 11, 2014 at 9:58 PM, Alex Becker wrote: > Hi! > > I'm starting a smaller web application. > Would it make sense to use Dancer 2 already? > > Best regards, > Alex > > _______________________________________________ > dancer-users mailing list > dancer-users at dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From racke at linuxia.de Fri Sep 12 09:18:59 2014 From: racke at linuxia.de (Stefan Hornburg (Racke)) Date: Fri, 12 Sep 2014 10:18:59 +0200 Subject: [dancer-users] Dancer2 Roadmap - your help needed! In-Reply-To: References: <5412119F.2070700@vincew.net> Message-ID: <5412AC73.3040102@linuxia.de> On 09/12/2014 10:16 AM, Sawyer X wrote: > So I'm trying to think of how to aggregate all of these into a proper roadmap. > > We could add all of these as Github issues, or as Github wiki pages. > My problem with doing it in issues is that it might conflate with bugs and feature requests. > > I'm actually not only interested in feature requests. I'm interesting in formalizing the direction Dancer2 is going in, and discussing how to get there. Eventually I want to end up with a document saying "This is where we're going and how". (for different values of "how" :) > > Thoughts? I think GH Wiki is the place to go. Easier to collaborate as opposed to issues as well. Regards Racke -- Perl and Dancer Development Visit our Perl::Dancer conference 2014: http://act.perl.dance/ From info at vincew.net Fri Sep 12 09:30:18 2014 From: info at vincew.net (VinceW) Date: Fri, 12 Sep 2014 10:30:18 +0200 Subject: [dancer-users] Dancer2 Roadmap - your help needed! In-Reply-To: References: <5412119F.2070700@vincew.net> Message-ID: <5412AF1A.7060807@vincew.net> I suggest to have the (pre) final roadmap in the wiki (for instance ROADMAP-2015) on the other hand .... , discussions on topics to go in the roadmap, are best placed into the issue queu because - easy adding comments/reactions to it - keeping history of the discussion - closing of the discussion To organize this we could use the extended search function for issues, mentioning: ROADMAP in:title Matches issues with ROADMAP in their title. one could even decide to differentiate this more to ROADMAP-2015 so when in a few years a new roadmap has to be created, that title tag could be ROADMAP-2017 Best, VinceW On 09/12/2014 10:16 AM, Sawyer X wrote: > So I'm trying to think of how to aggregate all of these into a proper > roadmap. > > We could add all of these as Github issues, or as Github wiki pages. > My problem with doing it in issues is that it might conflate with bugs and > feature requests. > > I'm actually not only interested in feature requests. I'm interesting in > formalizing the direction Dancer2 is going in, and discussing how to get > there. Eventually I want to end up with a document saying "This is where > we're going and how". (for different values of "how" :) > > Thoughts? > > > On Thu, Sep 11, 2014 at 11:18 PM, VinceW wrote: > >> My 5cts >> >> disclaimer: Just (about 18 months) getting my feet wet with Perl/D1 >> (coming from PHP/framework environment) >> >> - mapping of current D1 modules against current D2 modules >> - priority listing of D1 modules needed to have in D2 >> - migration path from D1 -> D2 >> >> >> I would like to help the D1/D2 project. >> Having dev, git, linux experience, knowing a fraction of Perl (compared to >> others here on the list). >> Able to visit NL-PM and/or AmsterdamX.pm >> Willing to learn >> >> Best, >> VinceW >> >> >> On 09/11/2014 05:46 PM, Sawyer X wrote: >> >> Hey everyone, >> >> we're working on creating the Dancer2 roadmap. We need your help! >> >> We want to design it with you, and we want to know: >> * What do you think should be on the roadmap for Dancer2? >> * What do you like to see being done? >> * What would you help with, if it was on the plan? >> >> As the last item suggests, we're interesting in getting much more help with >> implementing this plan, once we have it written, so expect many "call to >> action"s. :) >> >> Let's open a discussion! >> >> >> >> >> _______________________________________________ >> dancer-users mailing listdancer-users at dancer.pmhttp://lists.preshweb.co.uk/mailman/listinfo/dancer-users >> >> >> >> _______________________________________________ >> dancer-users mailing list >> dancer-users at dancer.pm >> http://lists.preshweb.co.uk/mailman/listinfo/dancer-users >> >> > > > _______________________________________________ > dancer-users mailing list > dancer-users at dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From jsanmartin at gmail.com Fri Sep 12 09:34:42 2014 From: jsanmartin at gmail.com (=?UTF-8?B?SnVhbiBKb3PDqSAnUGVjbycgU2FuIE1hcnTDrW4=?=) Date: Fri, 12 Sep 2014 10:34:42 +0200 Subject: [dancer-users] Dancer2 Roadmap - your help needed! In-Reply-To: <5412AF1A.7060807@vincew.net> References: <5412119F.2070700@vincew.net> <5412AF1A.7060807@vincew.net> Message-ID: Hi all, I would like D2 achieve the goal: "D2 ready for production... in any scenario". IMHO, these could be the 4 sub-goals: 1) D2 vs D1: Develop features/plugins that are in D1 but missing in D2. 2) D2 as a solid rock: Close as many issues (bugs) as possible. 3) D2 enhancements: integration. There is not need to create the specific plugin for each case, just the documentation/tutorial on how to connect your Dancer app with.. 4) D2 homepage: www.dancer.org seems to talk about D1. What about www.perldancer2.org or join both on the same site? I could buy the domain and dedicate space for webhosting. Happy hacking, Peco 2014-09-12 10:30 GMT+02:00 VinceW : > I suggest to have the (pre) final roadmap in the wiki (for instance > ROADMAP-2015) > > on the other hand .... , discussions on topics to go in the roadmap, are > best placed into the issue queu because > - easy adding comments/reactions to it > - keeping history of the discussion > - closing of the discussion > > To organize this we could use the extended search function for issues, > mentioning: > > ROADMAP in:title > Matches > issues with ROADMAP in their title. one could even decide to > differentiate this more to ROADMAP-2015 > > so when in a few years a new roadmap has to be created, that title tag > could be ROADMAP-2017 > > Best, > VinceW > > > > On 09/12/2014 10:16 AM, Sawyer X wrote: > > So I'm trying to think of how to aggregate all of these into a proper > roadmap. > > We could add all of these as Github issues, or as Github wiki pages. > My problem with doing it in issues is that it might conflate with bugs and > feature requests. > > I'm actually not only interested in feature requests. I'm interesting in > formalizing the direction Dancer2 is going in, and discussing how to get > there. Eventually I want to end up with a document saying "This is where > we're going and how". (for different values of "how" :) > > Thoughts? > > > On Thu, Sep 11, 2014 at 11:18 PM, VinceW wrote: > > > My 5cts > > disclaimer: Just (about 18 months) getting my feet wet with Perl/D1 > (coming from PHP/framework environment) > > - mapping of current D1 modules against current D2 modules > - priority listing of D1 modules needed to have in D2 > - migration path from D1 -> D2 > > > I would like to help the D1/D2 project. > Having dev, git, linux experience, knowing a fraction of Perl (compared to > others here on the list). > Able to visit NL-PM and/or AmsterdamX.pm > Willing to learn > > Best, > VinceW > > > On 09/11/2014 05:46 PM, Sawyer X wrote: > > Hey everyone, > > we're working on creating the Dancer2 roadmap. We need your help! > > We want to design it with you, and we want to know: > * What do you think should be on the roadmap for Dancer2? > * What do you like to see being done? > * What would you help with, if it was on the plan? > > As the last item suggests, we're interesting in getting much more help with > implementing this plan, once we have it written, so expect many "call to > action"s. :) > > Let's open a discussion! > > > > > ______________________________ > _________________ > dancer-users mailing listdancer-users at dancer.pmhttp://lists.preshweb.co.uk/mailman/listinfo/dancer-users > > > > _______________________________________________ > dancer-users mailing listdancer-users at dancer.pmhttp://lists.preshweb.co.uk/mailman/listinfo/dancer-users > > > > _______________________________________________ > dancer-users mailing listdancer-users at dancer.pmhttp://lists.preshweb.co.uk/mailman/listinfo/dancer-users > > > > _______________________________________________ > dancer-users mailing list > dancer-users at dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From gabor at szabgab.com Fri Sep 12 09:39:48 2014 From: gabor at szabgab.com (Gabor Szabo) Date: Fri, 12 Sep 2014 11:39:48 +0300 Subject: [dancer-users] Dancer 1 or Dancer 2? In-Reply-To: References: Message-ID: On Fri, Sep 12, 2014 at 11:18 AM, Sawyer X wrote: > It depends on the features you want, and how much you're willing to put up > with. :) > > Dancer2 is still not fully stable. Things are changing. However, it has > some spiffier features and allows some things which weren't possible in D1. > > > Is there a comparison table between D1 and D2 ? Gabor -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at vincew.net Fri Sep 12 09:59:03 2014 From: info at vincew.net (VinceW) Date: Fri, 12 Sep 2014 10:59:03 +0200 Subject: [dancer-users] Dancer2 Roadmap - your help needed! In-Reply-To: References: <5412119F.2070700@vincew.net> <5412AF1A.7060807@vincew.net> Message-ID: <5412B5D7.2080508@vincew.net> 4) I would say keep it on -1- site. For end-users more logical, for maintenance too. Also info about differences, upgrade paths etc are more logical over there. Best, VinceW On 09/12/2014 10:34 AM, Juan Jos? 'Peco' San Mart?n wrote: > Hi all, > > I would like D2 achieve the goal: "D2 ready for production... in any > scenario". > > IMHO, these could be the 4 sub-goals: > 1) D2 vs D1: Develop features/plugins that are in D1 but missing in D2. > 2) D2 as a solid rock: Close as many issues (bugs) as possible. > 3) D2 enhancements: integration. There is not need to create the specific > plugin for each case, just the documentation/tutorial on how to connect > your Dancer app with.. > 4) D2 homepage: www.dancer.org seems to talk about D1. What about > www.perldancer2.org or join both on the same site? I could buy the domain > and dedicate space for webhosting. > > Happy hacking, > > Peco > > 2014-09-12 10:30 GMT+02:00 VinceW : > >> I suggest to have the (pre) final roadmap in the wiki (for instance >> ROADMAP-2015) >> >> on the other hand .... , discussions on topics to go in the roadmap, are >> best placed into the issue queu because >> - easy adding comments/reactions to it >> - keeping history of the discussion >> - closing of the discussion >> >> To organize this we could use the extended search function for issues, >> mentioning: >> >> ROADMAP in:title >> Matches >> issues with ROADMAP in their title. one could even decide to >> differentiate this more to ROADMAP-2015 >> >> so when in a few years a new roadmap has to be created, that title tag >> could be ROADMAP-2017 >> >> Best, >> VinceW >> >> >> >> On 09/12/2014 10:16 AM, Sawyer X wrote: >> >> So I'm trying to think of how to aggregate all of these into a proper >> roadmap. >> >> We could add all of these as Github issues, or as Github wiki pages. >> My problem with doing it in issues is that it might conflate with bugs and >> feature requests. >> >> I'm actually not only interested in feature requests. I'm interesting in >> formalizing the direction Dancer2 is going in, and discussing how to get >> there. Eventually I want to end up with a document saying "This is where >> we're going and how". (for different values of "how" :) >> >> Thoughts? >> >> >> On Thu, Sep 11, 2014 at 11:18 PM, VinceW wrote: >> >> >> My 5cts >> >> disclaimer: Just (about 18 months) getting my feet wet with Perl/D1 >> (coming from PHP/framework environment) >> >> - mapping of current D1 modules against current D2 modules >> - priority listing of D1 modules needed to have in D2 >> - migration path from D1 -> D2 >> >> >> I would like to help the D1/D2 project. >> Having dev, git, linux experience, knowing a fraction of Perl (compared to >> others here on the list). >> Able to visit NL-PM and/or AmsterdamX.pm >> Willing to learn >> >> Best, >> VinceW >> >> >> On 09/11/2014 05:46 PM, Sawyer X wrote: >> >> Hey everyone, >> >> we're working on creating the Dancer2 roadmap. We need your help! >> >> We want to design it with you, and we want to know: >> * What do you think should be on the roadmap for Dancer2? >> * What do you like to see being done? >> * What would you help with, if it was on the plan? >> >> As the last item suggests, we're interesting in getting much more help with >> implementing this plan, once we have it written, so expect many "call to >> action"s. :) >> >> Let's open a discussion! >> >> >> >> >> ______________________________ >> _________________ >> dancer-users mailing listdancer-users at dancer.pmhttp://lists.preshweb.co.uk/mailman/listinfo/dancer-users >> >> >> >> _______________________________________________ >> dancer-users mailing listdancer-users at dancer.pmhttp://lists.preshweb.co.uk/mailman/listinfo/dancer-users >> >> >> >> _______________________________________________ >> dancer-users mailing listdancer-users at dancer.pmhttp://lists.preshweb.co.uk/mailman/listinfo/dancer-users >> >> >> >> _______________________________________________ >> dancer-users mailing list >> dancer-users at dancer.pm >> http://lists.preshweb.co.uk/mailman/listinfo/dancer-users >> >> > > > _______________________________________________ > dancer-users mailing list > dancer-users at dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From sukria at gmail.com Fri Sep 12 09:59:33 2014 From: sukria at gmail.com (Alexis Sukrieh) Date: Fri, 12 Sep 2014 10:59:33 +0200 Subject: [dancer-users] Dancer 1 or Dancer 2? In-Reply-To: References: Message-ID: 2014-09-12 10:39 GMT+02:00 Gabor Szabo : > On Fri, Sep 12, 2014 at 11:18 AM, Sawyer X wrote: > >> It depends on the features you want, and how much you're willing to put >> up with. :) >> >> Dancer2 is still not fully stable. Things are changing. However, it has >> some spiffier features and allows some things which weren't possible in D1. >> >> > Is there a comparison table between D1 and D2 ? > ?That would be something very good to provide, indeed. -- Alexis Sukrieh http://twitter.com/sukria - http://blog.sukria.net "People get annoyed when you try to debug them." -- Larry Wall -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at vincew.net Fri Sep 12 10:00:39 2014 From: info at vincew.net (VinceW) Date: Fri, 12 Sep 2014 11:00:39 +0200 Subject: [dancer-users] Dancer 1 or Dancer 2? In-Reply-To: References: Message-ID: <5412B637.7080304@vincew.net> It was also mentioned in the discussion about the roadmap for D2 Best, VinceW On 09/12/2014 10:59 AM, Alexis Sukrieh wrote: > 2014-09-12 10:39 GMT+02:00 Gabor Szabo : > >> On Fri, Sep 12, 2014 at 11:18 AM, Sawyer X wrote: >> >>> It depends on the features you want, and how much you're willing to put >>> up with. :) >>> >>> Dancer2 is still not fully stable. Things are changing. However, it has >>> some spiffier features and allows some things which weren't possible in D1. >>> >>> >> Is there a comparison table between D1 and D2 ? >> > That would be something very good to provide, indeed. > > > > > _______________________________________________ > dancer-users mailing list > dancer-users at dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From davserer at gmail.com Fri Sep 12 10:18:51 2014 From: davserer at gmail.com (=?UTF-8?B?S292w6FjcyBEw6F2aWQgWyBEYXZzIF0=?=) Date: Fri, 12 Sep 2014 11:18:51 +0200 Subject: [dancer-users] Dancer2 Roadmap - your help needed! In-Reply-To: <5412B5D7.2080508@vincew.net> References: <5412119F.2070700@vincew.net> <5412AF1A.7060807@vincew.net> <5412B5D7.2080508@vincew.net> Message-ID: While going forward, implementing new features is good, we should not forget about the documentation as well. On Fri, Sep 12, 2014 at 10:59 AM, VinceW wrote: > > 4) I would say keep it on -1- site. For end-users more logical, for > maintenance too. > Also info about differences, upgrade paths etc are more logical over there. > > Best, > VinceW > > > On 09/12/2014 10:34 AM, Juan Jos? 'Peco' San Mart?n wrote: > > Hi all, > > I would like D2 achieve the goal: "D2 ready for production... in any > scenario". > > IMHO, these could be the 4 sub-goals: > 1) D2 vs D1: Develop features/plugins that are in D1 but missing in D2. > 2) D2 as a solid rock: Close as many issues (bugs) as possible. > 3) D2 enhancements: integration. There is not need to create the specific > plugin for each case, just the documentation/tutorial on how to connect > your Dancer app with.. > 4) D2 homepage: www.dancer.org seems to talk about D1. What aboutwww.perldancer2.org or join both on the same site? I could buy the domain > and dedicate space for webhosting. > > Happy hacking, > > Peco > > 2014-09-12 10:30 GMT+02:00 VinceW : > > > I suggest to have the (pre) final roadmap in the wiki (for instance > ROADMAP-2015) > > on the other hand .... , discussions on topics to go in the roadmap, are > best placed into the issue queu because > - easy adding comments/reactions to it > - keeping history of the discussion > - closing of the discussion > > To organize this we could use the extended search function for issues, > mentioning: > > ROADMAP in:title > Matches > issues with ROADMAP in their title. one could even decide to > differentiate this more to ROADMAP-2015 > > so when in a few years a new roadmap has to be created, that title tag > could be ROADMAP-2017 > > Best, > VinceW > > > > On 09/12/2014 10:16 AM, Sawyer X wrote: > > So I'm trying to think of how to aggregate all of these into a proper > roadmap. > > We could add all of these as Github issues, or as Github wiki pages. > My problem with doing it in issues is that it might conflate with bugs and > feature requests. > > I'm actually not only interested in feature requests. I'm interesting in > formalizing the direction Dancer2 is going in, and discussing how to get > there. Eventually I want to end up with a document saying "This is where > we're going and how". (for different values of "how" :) > > Thoughts? > > > On Thu, Sep 11, 2014 at 11:18 PM, VinceW wrote: > > > My 5cts > > disclaimer: Just (about 18 months) getting my feet wet with Perl/D1 > (coming from PHP/framework environment) > > - mapping of current D1 modules against current D2 modules > - priority listing of D1 modules needed to have in D2 > - migration path from D1 -> D2 > > > I would like to help the D1/D2 project. > Having dev, git, linux experience, knowing a fraction of Perl (compared to > others here on the list). > Able to visit NL-PM and/or AmsterdamX.pm > Willing to learn > > Best, > VinceW > > > On 09/11/2014 05:46 PM, Sawyer X wrote: > > Hey everyone, > > we're working on creating the Dancer2 roadmap. We need your help! > > We want to design it with you, and we want to know: > * What do you think should be on the roadmap for Dancer2? > * What do you like to see being done? > * What would you help with, if it was on the plan? > > As the last item suggests, we're interesting in getting much more help with > implementing this plan, once we have it written, so expect many "call to > action"s. :) > > Let's open a discussion! > > > > > ______________________________ > _________________ > dancer-users mailing listdancer-users at dancer.pmhttp://lists.preshweb.co.uk/mailman/listinfo/dancer-users > > > > > _______________________________________________ > dancer-users mailing listdancer-users at dancer.pmhttp://lists.preshweb.co.uk/mailman/listinfo/dancer-users > > > > _______________________________________________ > dancer-users mailing listdancer-users at dancer.pmhttp://lists.preshweb.co.uk/mailman/listinfo/dancer-users > > > > _______________________________________________ > dancer-users mailing listdancer-users at dancer.pmhttp://lists.preshweb.co.uk/mailman/listinfo/dancer-users > > > > _______________________________________________ > dancer-users mailing listdancer-users at dancer.pmhttp://lists.preshweb.co.uk/mailman/listinfo/dancer-users > > > > _______________________________________________ > dancer-users mailing list > dancer-users at dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From davserer at gmail.com Fri Sep 12 10:21:18 2014 From: davserer at gmail.com (=?UTF-8?B?S292w6FjcyBEw6F2aWQgWyBEYXZzIF0=?=) Date: Fri, 12 Sep 2014 11:21:18 +0200 Subject: [dancer-users] Dancer 1 or Dancer 2? In-Reply-To: <5412B637.7080304@vincew.net> References: <5412B637.7080304@vincew.net> Message-ID: One thing I've noticed is that in Dancer2 the before hooks are executed even on static files; that way https://metacpan.org/pod/distribution/Dancer/lib/Dancer/Cookbook.pod#Sessions-and-logging-in is not working at all, because if the user is not logged in, the static (css, js etc) files are not served. Back at the time that was one of the reasons I went with Dancer1 instead of Dancer2. On Fri, Sep 12, 2014 at 11:00 AM, VinceW wrote: > It was also mentioned in the discussion about the roadmap for D2 > > Best, > VinceW > > On 09/12/2014 10:59 AM, Alexis Sukrieh wrote: > > 2014-09-12 10:39 GMT+02:00 Gabor Szabo : > > > On Fri, Sep 12, 2014 at 11:18 AM, Sawyer X wrote: > > > It depends on the features you want, and how much you're willing to put > up with. :) > > Dancer2 is still not fully stable. Things are changing. However, it has > some spiffier features and allows some things which weren't possible in D1. > > > > Is there a comparison table between D1 and D2 ? > > > ?That would be something very good to provide, indeed. > > > > > > _______________________________________________ > dancer-users mailing listdancer-users at dancer.pmhttp://lists.preshweb.co.uk/mailman/listinfo/dancer-users > > > > _______________________________________________ > dancer-users mailing list > dancer-users at dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at vincew.net Fri Sep 12 12:40:50 2014 From: info at vincew.net (VinceW) Date: Fri, 12 Sep 2014 13:40:50 +0200 Subject: [dancer-users] comparison table D1/D2 Message-ID: <5412DBC2.6040609@vincew.net> In two recent threads of this list a comparison table was mentioned. I had this on my wish list for D1/D2 too and I was just fiddling with one. a first draft is currently available on: http://eurweb.eu perhaps someone would like to have a look at it and provide some feedback about setup, data in the list, etc when list is ready, it could be taken to perldancer.org Best, VinceW From xsawyerx at gmail.com Fri Sep 12 13:35:48 2014 From: xsawyerx at gmail.com (Sawyer X) Date: Fri, 12 Sep 2014 14:35:48 +0200 Subject: [dancer-users] Dancer 1 or Dancer 2? In-Reply-To: References: <5412B637.7080304@vincew.net> Message-ID: Unfortunately that is a terrible example. The concept of blocking all requests in a before() hook is... let's say, naive. In reality you would like to simply block specific requests according to session, a la David Golden's Auth::Tiny. The before hooks are basically run on every request. Static files are now served through the File handler. That means it will trigger the before hooks because it's a normal request. I would love to do it using the Static middleware, but then it will happen before a route check on it, so we can't have that. On Fri, Sep 12, 2014 at 11:21 AM, Kov?cs D?vid [ Davs ] wrote: > One thing I've noticed is that in Dancer2 the before hooks are executed > even on static files; that way > https://metacpan.org/pod/distribution/Dancer/lib/Dancer/Cookbook.pod#Sessions-and-logging-in > is not working at all, because if the user is not logged in, the static > (css, js etc) files are not served. Back at the time that was one of the > reasons I went with Dancer1 instead of Dancer2. > > On Fri, Sep 12, 2014 at 11:00 AM, VinceW wrote: > >> It was also mentioned in the discussion about the roadmap for D2 >> >> Best, >> VinceW >> >> On 09/12/2014 10:59 AM, Alexis Sukrieh wrote: >> >> 2014-09-12 10:39 GMT+02:00 Gabor Szabo : >> >> >> On Fri, Sep 12, 2014 at 11:18 AM, Sawyer X wrote: >> >> >> It depends on the features you want, and how much you're willing to put >> up with. :) >> >> Dancer2 is still not fully stable. Things are changing. However, it has >> some spiffier features and allows some things which weren't possible in D1. >> >> >> >> Is there a comparison table between D1 and D2 ? >> >> >> ?That would be something very good to provide, indeed. >> >> >> >> >> >> _______________________________________________ >> dancer-users mailing listdancer-users at dancer.pmhttp://lists.preshweb.co.uk/mailman/listinfo/dancer-users >> >> >> >> _______________________________________________ >> dancer-users mailing list >> dancer-users at dancer.pm >> http://lists.preshweb.co.uk/mailman/listinfo/dancer-users >> >> > > _______________________________________________ > dancer-users mailing list > dancer-users at dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From xsawyerx at gmail.com Fri Sep 12 13:36:37 2014 From: xsawyerx at gmail.com (Sawyer X) Date: Fri, 12 Sep 2014 14:36:37 +0200 Subject: [dancer-users] comparison table D1/D2 In-Reply-To: <5412DBC2.6040609@vincew.net> References: <5412DBC2.6040609@vincew.net> Message-ID: We're working on a migration document and I think this would fit there very well at the top. https://github.com/PerlDancer/Dancer2/wiki/Migration On Fri, Sep 12, 2014 at 1:40 PM, VinceW wrote: > In two recent threads of this list a comparison table was mentioned. > > I had this on my wish list for D1/D2 too and I was just fiddling with one. > > a first draft is currently available on: http://eurweb.eu > perhaps someone would like to have a look at it and provide some feedback > about setup, data in the list, etc > > when list is ready, it could be taken to perldancer.org > > Best, > VinceW > _______________________________________________ > dancer-users mailing list > dancer-users at dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From hvo.pm at xs4all.nl Fri Sep 12 14:13:23 2014 From: hvo.pm at xs4all.nl (Henk van Oers) Date: Fri, 12 Sep 2014 15:13:23 +0200 (CEST) Subject: [dancer-users] comparison table D1/D2 In-Reply-To: References: <5412DBC2.6040609@vincew.net> Message-ID: On Fri, 12 Sep 2014, Sawyer X wrote: > We're working on a migration document and I think this would fit there very well at the top. > https://github.com/PerlDancer/Dancer2/wiki/Migration Nice. You also wrote about D2: "" However, it has some spiffier features and allows some things which weren't possible in D1. "" Can you make a list of those things? > On Fri, Sep 12, 2014 at 1:40 PM, VinceW wrote: > perhaps someone would like to have a look at it and provide some feedback about setup, data in the list, etc > > when list is ready, it could be taken to perldancer.org I have a list of FreeBSD ports: Port: p5-Dancer-Plugin-DBIC-0.2100 Port: p5-Dancer-Plugin-Database-2.09_1 Port: p5-Dancer-Plugin-Database-Core-0.07 Port: p5-Dancer-Plugin-Redis-0.8 Port: p5-Dancer-Session-Memcached-0.2.02 Port: p5-Dancer-Debug-0.03 Port: p5-Dancer-Plugin-Email-1.0201 Port: p5-Dancer-Plugin-Auth-Extensible-0.30 Port: p5-Dancer-Plugin-Auth-Extensible-Provider-Usergroup-0.21 Port: p5-Dancer-Plugin-Passphrase-2.0.1 Port: p5-Dancer-1.3120 Port: p5-Dancer-Logger-Log4perl-0.9.0 Port: p5-Dancer-Plugin-ExtDirect-1.03 Port: p5-Dancer-Plugin-Feed-1.131470 Port: p5-Dancer-Plugin-Lexicon-0.06 Port: p5-Dancer-Plugin-REST-0.11 Port: p5-Dancer-Plugin-SiteMap-0.14 Port: p5-Dancer-Plugin-ValidationClass-0.120490 Port: p5-Dancer-Session-Cookie-0.22 Port: p5-Dancer-Template-Xslate-0.03_1 Port: p5-Dancer2-0.141000_1 What to do with them? -- Henk From info at vincew.net Fri Sep 12 14:20:23 2014 From: info at vincew.net (VinceW) Date: Fri, 12 Sep 2014 15:20:23 +0200 Subject: [dancer-users] comparison table D1/D2 In-Reply-To: References: <5412DBC2.6040609@vincew.net> Message-ID: <5412F317.70608@vincew.net> On 09/12/2014 03:13 PM, Henk van Oers wrote: > > On Fri, 12 Sep 2014, Sawyer X wrote: > >> We're working on a migration document and I think this would fit >> there very well at the top. >> https://github.com/PerlDancer/Dancer2/wiki/Migration > > Nice. > > You also wrote about D2: > "" > However, it has some spiffier features and allows some things which > weren't possible in D1. > "" > Can you make a list of those things? > >> On Fri, Sep 12, 2014 at 1:40 PM, VinceW wrote: > >> perhaps someone would like to have a look at it and provide >> some feedback about setup, data in the list, etc >> >> when list is ready, it could be taken to perldancer.org > > I have a list of FreeBSD ports: > > Port: p5-Dancer-Plugin-DBIC-0.2100 > Port: p5-Dancer-Plugin-Database-2.09_1 > Port: p5-Dancer-Plugin-Database-Core-0.07 > Port: p5-Dancer-Plugin-Redis-0.8 > Port: p5-Dancer-Session-Memcached-0.2.02 > Port: p5-Dancer-Debug-0.03 > Port: p5-Dancer-Plugin-Email-1.0201 > Port: p5-Dancer-Plugin-Auth-Extensible-0.30 > Port: p5-Dancer-Plugin-Auth-Extensible-Provider-Usergroup-0.21 > Port: p5-Dancer-Plugin-Passphrase-2.0.1 > Port: p5-Dancer-1.3120 > Port: p5-Dancer-Logger-Log4perl-0.9.0 > Port: p5-Dancer-Plugin-ExtDirect-1.03 > Port: p5-Dancer-Plugin-Feed-1.131470 > Port: p5-Dancer-Plugin-Lexicon-0.06 > Port: p5-Dancer-Plugin-REST-0.11 > Port: p5-Dancer-Plugin-SiteMap-0.14 > Port: p5-Dancer-Plugin-ValidationClass-0.120490 > Port: p5-Dancer-Session-Cookie-0.22 > Port: p5-Dancer-Template-Xslate-0.03_1 > Port: p5-Dancer2-0.141000_1 > > What to do with them? > Perhaps we should make a separate list for specific ports (FreeBSD, Debian, etc ...) ? From racke at linuxia.de Fri Sep 12 14:21:24 2014 From: racke at linuxia.de (Stefan Hornburg (Racke)) Date: Fri, 12 Sep 2014 15:21:24 +0200 Subject: [dancer-users] Dancer 1 or Dancer 2? In-Reply-To: References: <5412B637.7080304@vincew.net> Message-ID: <5412F354.1090906@linuxia.de> On 09/12/2014 02:35 PM, Sawyer X wrote: > Unfortunately that is a terrible example. The concept of blocking all requests in a before() hook is... let's say, naive. In reality you would like to simply block specific requests according to session, a la David Golden's Auth::Tiny. > > The before hooks are basically run on every request. Static files are now served through the File handler. That means it will trigger the before hooks because it's a normal request. > I would love to do it using the Static middleware, but then it will happen before a route check on it, so we can't have that. I still disagree with this change of behaviour from Dancer 1 to Dancer 2. What is the benefit of calling before hook for public files? Also in a production environment you might deliver static files with some other software (Nginx, ...) and you loose control on these public files anyway. Regards Racke -- Perl and Dancer Development Visit our Perl::Dancer conference 2014: http://act.perl.dance/ From xsawyerx at gmail.com Fri Sep 12 14:56:36 2014 From: xsawyerx at gmail.com (Sawyer X) Date: Fri, 12 Sep 2014 15:56:36 +0200 Subject: [dancer-users] Dancer 1 or Dancer 2? In-Reply-To: <5412F354.1090906@linuxia.de> References: <5412B637.7080304@vincew.net> <5412F354.1090906@linuxia.de> Message-ID: On Fri, Sep 12, 2014 at 3:21 PM, Stefan Hornburg (Racke) wrote: > On 09/12/2014 02:35 PM, Sawyer X wrote: > > Unfortunately that is a terrible example. The concept of blocking all > requests in a before() hook is... let's say, naive. In reality you would > like to simply block specific requests according to session, a la David > Golden's Auth::Tiny. > > > > The before hooks are basically run on every request. Static files are > now served through the File handler. That means it will trigger the before > hooks because it's a normal request. > > I would love to do it using the Static middleware, but then it will > happen before a route check on it, so we can't have that. > > I still disagree with this change of behaviour from Dancer 1 to Dancer 2. > What is the benefit of calling before hook for public files? > Also in a production environment you might deliver static files with some > other software (Nginx, ...) and you loose control on > these public files anyway. > The point is that this is not a selection of behavior. It isn't "we want a before hook on public files", but "because public files are serves as a handler, they will have before hooks called too". It's implicit behavior because of the restructuring of public files as file handlers. -------------- next part -------------- An HTML attachment was scrubbed... URL: From xsawyerx at gmail.com Fri Sep 12 14:58:03 2014 From: xsawyerx at gmail.com (Sawyer X) Date: Fri, 12 Sep 2014 15:58:03 +0200 Subject: [dancer-users] comparison table D1/D2 In-Reply-To: <5412F317.70608@vincew.net> References: <5412DBC2.6040609@vincew.net> <5412F317.70608@vincew.net> Message-ID: I don't think "ports" actually means "porting", but the FreeBSD ports system. It means "a package of the following for FreeBSD." On Fri, Sep 12, 2014 at 3:20 PM, VinceW wrote: > On 09/12/2014 03:13 PM, Henk van Oers wrote: > >> >> On Fri, 12 Sep 2014, Sawyer X wrote: >> >> We're working on a migration document and I think this would fit there >>> very well at the top. >>> https://github.com/PerlDancer/Dancer2/wiki/Migration >>> >> >> Nice. >> >> You also wrote about D2: >> "" >> However, it has some spiffier features and allows some things which >> weren't possible in D1. >> "" >> Can you make a list of those things? >> >> On Fri, Sep 12, 2014 at 1:40 PM, VinceW wrote: >>> >> >> perhaps someone would like to have a look at it and provide some >>> feedback about setup, data in the list, etc >>> >>> when list is ready, it could be taken to perldancer.org >>> >> >> I have a list of FreeBSD ports: >> >> Port: p5-Dancer-Plugin-DBIC-0.2100 >> Port: p5-Dancer-Plugin-Database-2.09_1 >> Port: p5-Dancer-Plugin-Database-Core-0.07 >> Port: p5-Dancer-Plugin-Redis-0.8 >> Port: p5-Dancer-Session-Memcached-0.2.02 >> Port: p5-Dancer-Debug-0.03 >> Port: p5-Dancer-Plugin-Email-1.0201 >> Port: p5-Dancer-Plugin-Auth-Extensible-0.30 >> Port: p5-Dancer-Plugin-Auth-Extensible-Provider-Usergroup-0.21 >> Port: p5-Dancer-Plugin-Passphrase-2.0.1 >> Port: p5-Dancer-1.3120 >> Port: p5-Dancer-Logger-Log4perl-0.9.0 >> Port: p5-Dancer-Plugin-ExtDirect-1.03 >> Port: p5-Dancer-Plugin-Feed-1.131470 >> Port: p5-Dancer-Plugin-Lexicon-0.06 >> Port: p5-Dancer-Plugin-REST-0.11 >> Port: p5-Dancer-Plugin-SiteMap-0.14 >> Port: p5-Dancer-Plugin-ValidationClass-0.120490 >> Port: p5-Dancer-Session-Cookie-0.22 >> Port: p5-Dancer-Template-Xslate-0.03_1 >> Port: p5-Dancer2-0.141000_1 >> >> What to do with them? >> >> Perhaps we should make a separate list for specific ports (FreeBSD, > Debian, etc ...) ? > > > > _______________________________________________ > dancer-users mailing list > dancer-users at dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at vincew.net Fri Sep 12 15:57:44 2014 From: info at vincew.net (VinceW) Date: Fri, 12 Sep 2014 16:57:44 +0200 Subject: [dancer-users] comparison table D1/D2 In-Reply-To: References: <5412DBC2.6040609@vincew.net> <5412F317.70608@vincew.net> Message-ID: <541309E8.9090807@vincew.net> On 09/12/2014 03:58 PM, Sawyer X wrote: > I don't think "ports" actually means "porting", but the FreeBSD ports > system. It means "a package of the following for FreeBSD." that was my interpretation also. Debian has also it's own package system. I can think of other distros too. Should module packages for various distribution go on this list, or create another one for that information? The latter has my preference, there are so many distributions, I think it's worth a list on its own :-) portable in comparison table was meant to mean: can a module for D1 be ported to D2 or vice versa Best, VinceW > On Fri, Sep 12, 2014 at 3:20 PM, VinceW wrote: > >> On 09/12/2014 03:13 PM, Henk van Oers wrote: >> >>> On Fri, 12 Sep 2014, Sawyer X wrote: >>> >>> We're working on a migration document and I think this would fit there >>>> very well at the top. >>>> https://github.com/PerlDancer/Dancer2/wiki/Migration >>>> >>> Nice. >>> >>> You also wrote about D2: >>> "" >>> However, it has some spiffier features and allows some things which >>> weren't possible in D1. >>> "" >>> Can you make a list of those things? >>> >>> On Fri, Sep 12, 2014 at 1:40 PM, VinceW wrote: >>> perhaps someone would like to have a look at it and provide some >>>> feedback about setup, data in the list, etc >>>> >>>> when list is ready, it could be taken to perldancer.org >>>> >>> I have a list of FreeBSD ports: >>> >>> Port: p5-Dancer-Plugin-DBIC-0.2100 >>> Port: p5-Dancer-Plugin-Database-2.09_1 >>> Port: p5-Dancer-Plugin-Database-Core-0.07 >>> Port: p5-Dancer-Plugin-Redis-0.8 >>> Port: p5-Dancer-Session-Memcached-0.2.02 >>> Port: p5-Dancer-Debug-0.03 >>> Port: p5-Dancer-Plugin-Email-1.0201 >>> Port: p5-Dancer-Plugin-Auth-Extensible-0.30 >>> Port: p5-Dancer-Plugin-Auth-Extensible-Provider-Usergroup-0.21 >>> Port: p5-Dancer-Plugin-Passphrase-2.0.1 >>> Port: p5-Dancer-1.3120 >>> Port: p5-Dancer-Logger-Log4perl-0.9.0 >>> Port: p5-Dancer-Plugin-ExtDirect-1.03 >>> Port: p5-Dancer-Plugin-Feed-1.131470 >>> Port: p5-Dancer-Plugin-Lexicon-0.06 >>> Port: p5-Dancer-Plugin-REST-0.11 >>> Port: p5-Dancer-Plugin-SiteMap-0.14 >>> Port: p5-Dancer-Plugin-ValidationClass-0.120490 >>> Port: p5-Dancer-Session-Cookie-0.22 >>> Port: p5-Dancer-Template-Xslate-0.03_1 >>> Port: p5-Dancer2-0.141000_1 >>> >>> What to do with them? >>> >>> Perhaps we should make a separate list for specific ports (FreeBSD, >> Debian, etc ...) ? >> >> >> >> _______________________________________________ >> dancer-users mailing list >> dancer-users at dancer.pm >> http://lists.preshweb.co.uk/mailman/listinfo/dancer-users >> > > > _______________________________________________ > dancer-users mailing list > dancer-users at dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From hvo.pm at xs4all.nl Fri Sep 12 21:36:59 2014 From: hvo.pm at xs4all.nl (Henk van Oers) Date: Fri, 12 Sep 2014 22:36:59 +0200 (CEST) Subject: [dancer-users] comparison table D1/D2 In-Reply-To: <541309E8.9090807@vincew.net> References: <5412DBC2.6040609@vincew.net> <5412F317.70608@vincew.net> <541309E8.9090807@vincew.net> Message-ID: On Fri, 12 Sep 2014, VinceW wrote: > On 09/12/2014 03:58 PM, Sawyer X wrote: >> >> I don't think "ports" actually means "porting", but the FreeBSD ports >> system. It means "a package of the following for FreeBSD." Yes. Sorry for the "DSL" :-) > that was my interpretation also. Debian has also it's own package system. I can think of other distros too. > > Should module packages for various distribution go on this list, or create another one for that information? > The latter has my preference, there are so many distributions, I think it's worth a list on its own :-) The FreeBSD ports collection is not a distribution but *is* a list on its own. I can do the magic, from source, optional dependencies, custom packages. > portable in comparison table was meant to mean: can a module for D1 be ported to D2 or vice versa In D1 I am missing https://metacpan.org/pod/Dancer2::Plugin#on_plugin_import and the my $dsl = shift; [snip] > Port: p5-Dancer2-0.141000_1 > > What to do with them? - First: upgrade to 0.150000 - Next: Make a "FreeBSD port" for https://metacpan.org/pod/Dancer2::Plugin::DBIC Can't live without DBIC :-) -- Henk From hvo.pm at xs4all.nl Sat Sep 13 07:56:46 2014 From: hvo.pm at xs4all.nl (Henk van Oers) Date: Sat, 13 Sep 2014 08:56:46 +0200 (CEST) Subject: [dancer-users] comparison table D1/D2 In-Reply-To: References: <5412DBC2.6040609@vincew.net> <5412F317.70608@vincew.net> <541309E8.9090807@vincew.net> Message-ID: On Fri, 12 Sep 2014, Henk van Oers wrote: [...] > In D1 I am missing https://metacpan.org/pod/Dancer2::Plugin#on_plugin_import This whould make my D1 plugins useable in D2. See: https://github.com/PerlDancer/Dancer2/wiki/Migration "" plugin_setting Cannot be called anymore outside register or on_plugin_import. "" -- Henk From xsawyerx at gmail.com Sun Sep 14 20:30:55 2014 From: xsawyerx at gmail.com (Sawyer X) Date: Sun, 14 Sep 2014 21:30:55 +0200 Subject: [dancer-users] Dancer Plugins Maintainers team on Github Message-ID: Hi all! :) I've just created a new team on Github's PerlDancer organization called Plugins Maintainers[1]. This team will consist on anyone and everyone that want to help maintain Dancer (both D1 and D2) plugins. I've already added all the plugin repos that we have under the organization. Team members are able to both read and write to the repos. If you're unsure about a change, feel free to just discuss it with the other team. Open an issue, request responses. We're all here for each other. I'd like to thank all the volunteers we have in the community. I hope this will make it easier on you to contribute in the future. If you want to help with plugins, please oh please let us know and we'll add you to the team. :) [1] https://github.com/orgs/PerlDancer/teams/plugins-maintainers/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From xsawyerx at gmail.com Sun Sep 14 20:52:17 2014 From: xsawyerx at gmail.com (Sawyer X) Date: Sun, 14 Sep 2014 21:52:17 +0200 Subject: [dancer-users] Dancer Advent Calendar Message-ID: Hi everyone, again, :) I've taken the liberty to start a list of possible articles for the Dancer Advent Calendar (coming this December to a calendar near you!) and I would be very happy if you could add your own suggestions. If you want to also indicate that you're going to write it yourself (whether for sure, or only tentatively), feel free to add that too. https://github.com/PerlDancer/Dancer2/wiki/Advent-Calendar -------------- next part -------------- An HTML attachment was scrubbed... URL: From sarah.alm at financejobs.co Sun Sep 14 21:31:16 2014 From: sarah.alm at financejobs.co (Sarah Alm) Date: Sun, 14 Sep 2014 20:31:16 +0000 Subject: [dancer-users] Adding Finance Jobs to the dancefloor Message-ID: <20140914203116.GJ31523@debian> Hi everybody, We just launched our new jobs board focusing on the finance industry: https://www.financejobs.co We use Perl and Dancer as our framework and we would be proud to be included on the Dancer dance floor :) Feedback also welcome. Sarah -- Sarah Alm https://www.financejobs.co From hvo.pm at xs4all.nl Sun Sep 14 21:55:51 2014 From: hvo.pm at xs4all.nl (Henk van Oers) Date: Sun, 14 Sep 2014 22:55:51 +0200 (CEST) Subject: [dancer-users] Dancer Plugins Maintainers team on Github In-Reply-To: References: Message-ID: On Sun, 14 Sep 2014, Sawyer X wrote: > [1]?https://github.com/orgs/PerlDancer/teams/plugins-maintainers/ I get a 404 :( -- Henk From davserer at gmail.com Sun Sep 14 21:57:06 2014 From: davserer at gmail.com (=?UTF-8?B?S292w6FjcyBEw6F2aWQgWyBEYXZzIF0=?=) Date: Sun, 14 Sep 2014 22:57:06 +0200 Subject: [dancer-users] Dancer Plugins Maintainers team on Github In-Reply-To: References: Message-ID: Works for me On Sun, Sep 14, 2014 at 10:55 PM, Henk van Oers wrote: > > On Sun, 14 Sep 2014, Sawyer X wrote: > > [1] https://github.com/orgs/PerlDancer/teams/plugins-maintainers/ >> > > I get a 404 :( > > -- > Henk > _______________________________________________ > dancer-users mailing list > dancer-users at dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew at illywhacker.net Sun Sep 14 22:03:13 2014 From: andrew at illywhacker.net (Andrew Solomon) Date: Sun, 14 Sep 2014 22:03:13 +0100 Subject: [dancer-users] Dancer Plugins Maintainers team on Github In-Reply-To: References: Message-ID: I also get a 404. On Sun, Sep 14, 2014 at 9:55 PM, Henk van Oers wrote: > > On Sun, 14 Sep 2014, Sawyer X wrote: > >> [1] https://github.com/orgs/PerlDancer/teams/plugins-maintainers/ > > > I get a 404 :( > > -- > Henk > _______________________________________________ > dancer-users mailing list > dancer-users at dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users From yanick at babyl.dyndns.org Mon Sep 15 00:12:57 2014 From: yanick at babyl.dyndns.org (Yanick Champoux) Date: Sun, 14 Sep 2014 19:12:57 -0400 Subject: [dancer-users] Dancer Plugins Maintainers team on Github In-Reply-To: References: Message-ID: <20140914231257.GA11440@gilgamesh.babyl.dyndns.org> On Sun, Sep 14, 2014 at 10:03:13PM +0100, Andrew Solomon wrote: > I also get a 404. I'm not 100% sure, but I think you have to be a perldancer admin to see that page. But, basically, it's just the list of peeps belonging to the plugins-maintainers group. Which, right now, consists of SawyerX, DavsX, polletix and deluxaran (something tells me the roster list will soon get longer). .. btw, is it me, or is that group could also be named "the X-Men"? :-) Joy, `/anick From warren at etr-usa.com Mon Sep 15 20:01:24 2014 From: warren at etr-usa.com (Warren Young) Date: Mon, 15 Sep 2014 13:01:24 -0600 Subject: [dancer-users] Recent Perl 5.8 compatibility breakage: mro Message-ID: <54173784.4020201@etr-usa.com> A recent update to Dancer apparently introduced a requirement for the 'mro' module, which is a Perl 5.10+ thing according to: http://search.cpan.org/~rjbs/perl-5.20.0/ext/mro/mro.pm I hope this can be fixed. One of the key reasons I chose Dancer is that it still worked on Perl 5.8, which is what RHEL 5 shipped with, which will still be in support for years: http://goo.gl/gUzmww It's too early to be dropping Perl 5.8, IMHO. Yes, I know, Modern Perl, 12 years old, yadda yadda. Perl 5.8 was the current version for over 5 years, so it got itself into a *lot* of places before 5.10 finally came around to displace it. From warren at etr-usa.com Mon Sep 15 20:07:13 2014 From: warren at etr-usa.com (Warren Young) Date: Mon, 15 Sep 2014 13:07:13 -0600 Subject: [dancer-users] Recent Perl 5.8 compatibility breakage: mro In-Reply-To: <54173784.4020201@etr-usa.com> References: <54173784.4020201@etr-usa.com> Message-ID: <541738E1.3040904@etr-usa.com> On 9/15/2014 13:01, Warren Young wrote: > A recent update to Dancer apparently introduced a requirement for the > 'mro' module Forgot to include the cpanm output: # cpanm Dancer --> Working on Dancer Fetching http://www.cpan.org/authors/id/Y/YA/YANICK/Dancer-1.3129.tar.gz ... OK Configuring Dancer-1.3129 ... OK ==> Found dependencies: mro skipping R/RJ/RJBS/perl-5.20.0.tar.gz ! Installing the dependencies failed: Module 'mro' is not installed ! Bailing out the installation for Dancer-1.3129. # cpanm mro skipping R/RJ/RJBS/perl-5.20.0.tar.gz No, cpanm, please don't try to install Perl 5.20 on this old box. Another thought: If there's a desire to push Dancer forward in terms of Perl support, is there a good reason not to keep it on the Dancer2 line? Isn't Dancer1 supposed to be in maintenance mode primarily, nice and stable? From sthoenna at gmail.com Mon Sep 15 20:09:55 2014 From: sthoenna at gmail.com (Yitzchak Scott-Thoennes) Date: Mon, 15 Sep 2014 12:09:55 -0700 Subject: [dancer-users] Recent Perl 5.8 compatibility breakage: mro In-Reply-To: <54173784.4020201@etr-usa.com> References: <54173784.4020201@etr-usa.com> Message-ID: When mro was first introduced, MRO::Compat was created for older perls; with any luck, it can be used for Dancer. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcarey at ucar.edu Mon Sep 15 20:09:43 2014 From: mcarey at ucar.edu (Maxwell Carey) Date: Mon, 15 Sep 2014 13:09:43 -0600 Subject: [dancer-users] Recent Perl 5.8 compatibility breakage: mro In-Reply-To: <54173784.4020201@etr-usa.com> References: <54173784.4020201@etr-usa.com> Message-ID: I'm not sure what bits of mro are used in Dancer, but MRO::Compat may work as a drop-in replacement. From the documentation : The "mro" namespace provides several utilities for dealing with method resolution order and method caching in general in Perl 5.9.5 and higher. This module provides those interfaces for earlier versions of Perl (back to 5.6.0 anyways). It is a harmless no-op to use this module on 5.9.5+. That is to say, code which properly uses MRO::Compat will work unmodified on both older Perls and 5.9.5+. If you're writing a piece of software that would like to use the parts of 5.9.5+'s mro:: interfaces that are supported here, and you want compatibility with older Perls, this is the module for you. On Mon, Sep 15, 2014 at 1:01 PM, Warren Young wrote: > A recent update to Dancer apparently introduced a requirement for the > 'mro' module, which is a Perl 5.10+ thing according to: > > http://search.cpan.org/~rjbs/perl-5.20.0/ext/mro/mro.pm > > I hope this can be fixed. One of the key reasons I chose Dancer is that > it still worked on Perl 5.8, which is what RHEL 5 shipped with, which will > still be in support for years: http://goo.gl/gUzmww > > It's too early to be dropping Perl 5.8, IMHO. Yes, I know, Modern Perl, > 12 years old, yadda yadda. Perl 5.8 was the current version for over 5 > years, so it got itself into a *lot* of places before 5.10 finally came > around to displace it. > _______________________________________________ > dancer-users mailing list > dancer-users at dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From warren at etr-usa.com Mon Sep 15 20:33:07 2014 From: warren at etr-usa.com (Warren Young) Date: Mon, 15 Sep 2014 13:33:07 -0600 Subject: [dancer-users] Recent Perl 5.8 compatibility breakage: mro In-Reply-To: References: <54173784.4020201@etr-usa.com> Message-ID: <54173EF3.7000706@etr-usa.com> On 9/15/2014 13:09, Yitzchak Scott-Thoennes wrote: > When mro was first introduced, MRO::Compat was created for older perls; > with any luck, it can be used for Dancer. This problem appears to be due to t/lib/TestPluginMRO.pm. There isn't a "use mro" anywhere else in the 1.3129 dist tree. Changing the "use mro 'c3'" line to reference MRO::Compat allows it to pass "make test," and it appears to now run. (More testing required.) By walking back through the versions, it appears this breakage was introduced in 1.3126. Unfortunately, there was no announcement on the list for 1.3.126, so I can't guess what change required this. From xsawyerx at gmail.com Mon Sep 15 20:43:43 2014 From: xsawyerx at gmail.com (Sawyer X) Date: Mon, 15 Sep 2014 21:43:43 +0200 Subject: [dancer-users] Dancer Plugins Maintainers team on Github In-Reply-To: <20140914231257.GA11440@gilgamesh.babyl.dyndns.org> References: <20140914231257.GA11440@gilgamesh.babyl.dyndns.org> Message-ID: I'm sorry, but I'll bet Yanick is right (as he always is). I wish the team could be clearly public. Anyway, as I stated, whoever wishes to join, just let us know and you'll be added. :) On Mon, Sep 15, 2014 at 1:12 AM, Yanick Champoux wrote: > On Sun, Sep 14, 2014 at 10:03:13PM +0100, Andrew Solomon wrote: > > I also get a 404. > > I'm not 100% sure, but I think you have to be a perldancer > admin to see that page. But, basically, it's just the list > of peeps belonging to the plugins-maintainers group. > Which, right now, consists of SawyerX, DavsX, polletix > and deluxaran (something tells me the roster list will > soon get longer). > > .. btw, is it me, or is that group could also be > named "the X-Men"? :-) > > Joy, > `/anick > > _______________________________________________ > dancer-users mailing list > dancer-users at dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From xsawyerx at gmail.com Mon Sep 15 20:46:17 2014 From: xsawyerx at gmail.com (Sawyer X) Date: Mon, 15 Sep 2014 21:46:17 +0200 Subject: [dancer-users] Recent Perl 5.8 compatibility breakage: mro In-Reply-To: <54173EF3.7000706@etr-usa.com> References: <54173784.4020201@etr-usa.com> <54173EF3.7000706@etr-usa.com> Message-ID: Opening an issue on Github will be the fastest way to see this resolved. It's easier for us to monitor issues on Github than on the list. If you don't have the time, I'll be happy to open one for you, but then you don't get the credit and our thank you for identifying the problem. :) On Mon, Sep 15, 2014 at 9:33 PM, Warren Young wrote: > On 9/15/2014 13:09, Yitzchak Scott-Thoennes wrote: > >> When mro was first introduced, MRO::Compat was created for older perls; >> with any luck, it can be used for Dancer. >> > > This problem appears to be due to t/lib/TestPluginMRO.pm. There isn't a > "use mro" anywhere else in the 1.3129 dist tree. > > Changing the "use mro 'c3'" line to reference MRO::Compat allows it to > pass "make test," and it appears to now run. (More testing required.) > > By walking back through the versions, it appears this breakage was > introduced in 1.3126. Unfortunately, there was no announcement on the list > for 1.3.126, so I can't guess what change required this. > > _______________________________________________ > dancer-users mailing list > dancer-users at dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From xsawyerx at gmail.com Mon Sep 15 20:50:10 2014 From: xsawyerx at gmail.com (Sawyer X) Date: Mon, 15 Sep 2014 21:50:10 +0200 Subject: [dancer-users] Adding Finance Jobs to the dancefloor In-Reply-To: <20140914203116.GJ31523@debian> References: <20140914203116.GJ31523@debian> Message-ID: Hi Sarah, :) we would love to add the website. We will just need the short description you would love to have on the Dancefloor. :) You can email the list, email me personally (xsawyerx AT cpan DOT org), or submit a pull request for the Github repo: https://github.com/PerlDancer/perldancer-website Whatever you prefer. :) On Sun, Sep 14, 2014 at 10:31 PM, Sarah Alm wrote: > Hi everybody, > > We just launched our new jobs board focusing on the finance industry: > > https://www.financejobs.co > > We use Perl and Dancer as our framework and we would be proud to be > included on > the Dancer dance floor :) > > Feedback also welcome. > > Sarah > > -- > Sarah Alm > https://www.financejobs.co > _______________________________________________ > dancer-users mailing list > dancer-users at dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From warren at etr-usa.com Mon Sep 15 20:54:28 2014 From: warren at etr-usa.com (Warren Young) Date: Mon, 15 Sep 2014 13:54:28 -0600 Subject: [dancer-users] Recent Perl 5.8 compatibility breakage: mro In-Reply-To: References: <54173784.4020201@etr-usa.com> <54173EF3.7000706@etr-usa.com> Message-ID: <541743F4.7060009@etr-usa.com> On 9/15/2014 13:46, Sawyer X wrote: > Opening an issue on Github will be the fastest way to see this resolved. Done: https://github.com/PerlDancer/Dancer/issues/1069 From sarah.alm at financejobs.co Mon Sep 15 21:26:59 2014 From: sarah.alm at financejobs.co (Sarah Alm) Date: Mon, 15 Sep 2014 20:26:59 +0000 Subject: [dancer-users] Adding Finance Jobs to the dancefloor In-Reply-To: References: <20140914203116.GJ31523@debian> Message-ID: <20140915202659.GF5630@d1stkfactory> Hi, Thanks for the love! And the love is straight back at you and the other contributors for bringing us Dancer as we <3 the framework :) Here's the description: "Finance Jobs aims to be the biggest finance jobs board in the world. We're not there yet, but we're going to try hard to get there while having fun along the way." Thanks! Sarah On Mon, Sep 15, 2014 at 09:50:10PM +0200, Sawyer X wrote: > Hi Sarah, :) > > we would love to add the website. We will just need the short description > you would love to have on the Dancefloor. :) > > You can email the list, email me personally (xsawyerx AT cpan DOT org), or > submit a pull request for the Github repo: > https://github.com/PerlDancer/perldancer-website > > Whatever you prefer. :) -- Sarah Alm https://www.financejobs.co From dave.s.doyle at gmail.com Mon Sep 15 22:15:38 2014 From: dave.s.doyle at gmail.com (Dave Doyle) Date: Mon, 15 Sep 2014 17:15:38 -0400 Subject: [dancer-users] Corp page/section for perldancer.org Message-ID: Hi Dancers, My company is not particularly interested in letting me put up anything on the dancefloor because they feel this is a security issue (revealing the framework). I guess I can see that to a degree even if I think it's wrong, but it is what it is. What they would be willing to do is if there were a section for "companies that use dancer" on the dancefloor where they would be happy to drop a logo. I'm not sure this is what folks would want but I was hoping to do something like that to show that we do use it. Has any thought been given to that? I realize this could be considered free corporate advertising by some but it's meant to be a show of support. Would there be any interest in this? Good idea? Bad idea? If people thought it wasn't great, my thought would be a nominal donation (which I'm not sure I could convince $work to do, but hey, worth trying) to allow the logo? Thoughts? Thanks, Dave -- dave.s.doyle at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From xsawyerx at cpan.org Mon Sep 15 22:26:34 2014 From: xsawyerx at cpan.org (Sawyer X) Date: Mon, 15 Sep 2014 23:26:34 +0200 Subject: [dancer-users] Adding Finance Jobs to the dancefloor In-Reply-To: <20140915202659.GF5630@d1stkfactory> References: <20140914203116.GJ31523@debian> <20140915202659.GF5630@d1stkfactory> Message-ID: I have added you to the website metadata. As soon as the website is deployed (which happens automatically, if I recall correctly), you will appear there! If you experience a delay, let us know. Thank you for the kind words, and good luck in your endeavor! :) On Mon, Sep 15, 2014 at 10:26 PM, Sarah Alm wrote: > Hi, > > Thanks for the love! And the love is straight back at you and the other > contributors for bringing us Dancer as we <3 the framework :) > > Here's the description: > > "Finance Jobs aims to be the biggest finance jobs board in the world. > We're > not there yet, but we're going to try hard to get there while having fun > along the way." > > Thanks! > > Sarah > > On Mon, Sep 15, 2014 at 09:50:10PM +0200, Sawyer X wrote: > > Hi Sarah, :) > > > > we would love to add the website. We will just need the short description > > you would love to have on the Dancefloor. :) > > > > You can email the list, email me personally (xsawyerx AT cpan DOT org), > or > > submit a pull request for the Github repo: > > https://github.com/PerlDancer/perldancer-website > > > > Whatever you prefer. :) > > -- > Sarah Alm > https://www.financejobs.co > _______________________________________________ > dancer-users mailing list > dancer-users at dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From yanick at babyl.dyndns.org Mon Sep 15 23:18:57 2014 From: yanick at babyl.dyndns.org (Yanick Champoux) Date: Mon, 15 Sep 2014 18:18:57 -0400 Subject: [dancer-users] Recent Perl 5.8 compatibility breakage: mro In-Reply-To: <541743F4.7060009@etr-usa.com> References: <54173784.4020201@etr-usa.com> <54173EF3.7000706@etr-usa.com> <541743F4.7060009@etr-usa.com> Message-ID: <20140915221857.GA20578@gilgamesh.babyl.dyndns.org> On Mon, Sep 15, 2014 at 01:54:28PM -0600, Warren Young wrote: > On 9/15/2014 13:46, Sawyer X wrote: > >Opening an issue on Github will be the fastest way to see this resolved. > > Done: https://github.com/PerlDancer/Dancer/issues/1069 Patch pushed to devel, will be published in a new release once I reach home tonight. (and yeah, I did terrible things to the pooch there, sorry 'bout that) Joy, `/anick -- From sarah.alm at financejobs.co Mon Sep 15 23:23:40 2014 From: sarah.alm at financejobs.co (Sarah Alm) Date: Mon, 15 Sep 2014 22:23:40 +0000 Subject: [dancer-users] Adding Finance Jobs to the dancefloor In-Reply-To: References: <20140914203116.GJ31523@debian> <20140915202659.GF5630@d1stkfactory> Message-ID: <20140915222340.GG5630@d1stkfactory> Thanks for adding us, and again thanks for Dancer! Sarah On Mon, Sep 15, 2014 at 11:26:34PM +0200, Sawyer X wrote: > I have added you to the website metadata. As soon as the website is > deployed (which happens automatically, if I recall correctly), you will > appear there! If you experience a delay, let us know. > > Thank you for the kind words, and good luck in your endeavor! :) > > On Mon, Sep 15, 2014 at 10:26 PM, Sarah Alm > wrote: > > > Hi, > > > > Thanks for the love! And the love is straight back at you and the other > > contributors for bringing us Dancer as we <3 the framework :) > > > > Here's the description: > > > > "Finance Jobs aims to be the biggest finance jobs board in the world. > > We're > > not there yet, but we're going to try hard to get there while having fun > > along the way." > > > > Thanks! > > > > Sarah > > > > On Mon, Sep 15, 2014 at 09:50:10PM +0200, Sawyer X wrote: > > > Hi Sarah, :) > > > > > > we would love to add the website. We will just need the short description > > > you would love to have on the Dancefloor. :) > > > > > > You can email the list, email me personally (xsawyerx AT cpan DOT org), > > or > > > submit a pull request for the Github repo: > > > https://github.com/PerlDancer/perldancer-website > > > > > > Whatever you prefer. :) > > > > -- > > Sarah Alm > > https://www.financejobs.co > > _______________________________________________ > > dancer-users mailing list > > dancer-users at dancer.pm > > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users > > > _______________________________________________ > dancer-users mailing list > dancer-users at dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users -- Sarah Alm https://www.financejobs.co From jack.lareau at gmail.com Mon Sep 15 23:56:35 2014 From: jack.lareau at gmail.com (Jacques Lareau) Date: Mon, 15 Sep 2014 18:56:35 -0400 Subject: [dancer-users] Corp page/section for perldancer.org In-Reply-To: References: Message-ID: I think it's a great idea. We use Dancer for lots internal apps, so we can't really show anything. +1 On Mon, Sep 15, 2014 at 5:15 PM, Dave Doyle wrote: > Hi Dancers, > > My company is not particularly interested in letting me put up anything on > the dancefloor because they feel this is a security issue (revealing the > framework). I guess I can see that to a degree even if I think it's wrong, > but it is what it is. > > What they would be willing to do is if there were a section for "companies > that use dancer" on the dancefloor where they would be happy to drop a > logo. I'm not sure this is what folks would want but I was hoping to do > something like that to show that we do use it. Has any thought been given > to that? > > I realize this could be considered free corporate advertising by some but > it's meant to be a show of support. Would there be any interest in this? > Good idea? Bad idea? If people thought it wasn't great, my thought would > be a nominal donation (which I'm not sure I could convince $work to do, but > hey, worth trying) to allow the logo? > > Thoughts? > > Thanks, > Dave > -- > dave.s.doyle at gmail.com > > _______________________________________________ > dancer-users mailing list > dancer-users at dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rao.chenlin at gmail.com Tue Sep 16 00:14:31 2014 From: rao.chenlin at gmail.com (rao chenlin) Date: Mon, 15 Sep 2014 23:14:31 +0000 (UTC) Subject: [dancer-users] =?utf-8?b?5oiR5q2j5ZyoIExpbmtlZEluICjpooboi7EpIA==?= =?utf-8?b?5ouT5bGV6IGM5Lia5Lq66ISJ77yM5biM5pyb6IO95LiO5oKo5bu656uL6IGU?= =?utf-8?b?57O7?= Message-ID: <1420964137.9962000.1410822871683.JavaMail.app@ela4-app2316.prod> ??: ??? LinkedIn (??) ????????????????? rao ????: http://www.linkedin.com/blink?simpleRedirect=0Qe3AVc30SejcRcjAVcjgTcjARfkh9rCZFt65QqnpKqipMrD1Be4Nir3RVpkJApn9xq7cCt7dBtmtvpnhFtCVFfmJB9C5QoORBt6BSrCAJt7dBtmsJr6RBfmtKqmJzon9Q9ClQqnpKimtBkClOs3Rx9DERbmcQcmBCd31FbmBUdnwUpzRBfP9SbSkLrmZzbCVFp6lHrCBIbDtTtOYLeDdMt7hE&msgID=I7894907984_1&markAsRead= ????????????????????????????????????????????????????: http://www.linkedin.com/blink?simpleRedirect=6RMhj8BsClzrC5Ac3gBsT9BsTkJsClzrC5AfmNFomRB9DhMoj0Oe6EPsTpDcCMOtzRAqm4CcjoMc38Zp6ACciQZp6BJ9DERbmcQcmBCd31FbmBUdnwUpzRAqmkCt7dBtmtvpnhFtCVFfmJB9B4ScSh5hSxmhD9JhB51fmVBqSZkp6BJ9DdKtjRQ9DERbmcQcmBCd31FbmBUdnwUpzRBfP9SbSkLrmZzbCVFp6lHrCBIbDtTtOYLeDdMt7hE&msgID=I7894907984_1&markAsRead= ????????????: http://www.linkedin.com/blink?simpleRedirect=3wUdPgZp4BBr6dFt79x9DhPpnlDnSlQqnpKqjRHpipIsBlBoSBSsCljsClJrThPtmcZoipWdiRzd35FpzgMqiRFu3lUe6oZpjYOtyZBbSRLoOVKqmhBqSVFr2VTtTsLbPFMt7hE&msgID=I7894907984_1&markAsRead= © 2014?LinkedIn Corporation?2029 Stierlin Ct. Mountain View, CA 94043, USA -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at vincew.net Tue Sep 16 11:07:04 2014 From: info at vincew.net (VinceW) Date: Tue, 16 Sep 2014 12:07:04 +0200 Subject: [dancer-users] second draft of comparison table D1/D2 In-Reply-To: <5412DBC2.6040609@vincew.net> References: <5412DBC2.6040609@vincew.net> Message-ID: <54180BC8.8070704@vincew.net> Hello all, currently there is a second draft version of the comparison table D1/D2 It is a static page generated by a script which pulls it's data from CPAN. The script is currently running manualy. I've still a few options to implement, like - adding hyperlinks to various items in the list - filtering out some errors in the module names - output template for - html (almost done) - markup language - git wiki ?? Comments, remarks, feature requests are more than welcome. Best, VinceW On 09/12/2014 01:40 PM, VinceW wrote: > In two recent threads of this list a comparison table was mentioned. > > I had this on my wish list for D1/D2 too and I was just fiddling with > one. > > a first draft is currently available on: http://eurweb.eu > perhaps someone would like to have a look at it and provide some > feedback about setup, data in the list, etc > > when list is ready, it could be taken to perldancer.org > > Best, > VinceW > _______________________________________________ > dancer-users mailing list > dancer-users at dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users From info at vincew.net Tue Sep 16 11:38:51 2014 From: info at vincew.net (VinceW) Date: Tue, 16 Sep 2014 12:38:51 +0200 Subject: [dancer-users] second draft of comparison table D1/D2 In-Reply-To: <54180BC8.8070704@vincew.net> References: <5412DBC2.6040609@vincew.net> <54180BC8.8070704@vincew.net> Message-ID: <5418133B.7010809@vincew.net> On 09/16/2014 12:07 PM, VinceW wrote: > Hello all, > > currently there is a second draft version of the comparison table D1/D2 > link to the list is at: http://eurweb.eu Best, VinceW > It is a static page generated by a script which pulls it's data from > CPAN. > The script is currently running manualy. > > I've still a few options to implement, like > - adding hyperlinks to various items in the list > - filtering out some errors in the module names > - output template for > - html (almost done) > - markup language > - git wiki ?? > > Comments, remarks, feature requests are more than welcome. > > Best, > VinceW > > > > > On 09/12/2014 01:40 PM, VinceW wrote: >> In two recent threads of this list a comparison table was mentioned. >> >> I had this on my wish list for D1/D2 too and I was just fiddling with >> one. >> >> a first draft is currently available on: http://eurweb.eu >> perhaps someone would like to have a look at it and provide some >> feedback about setup, data in the list, etc >> >> when list is ready, it could be taken to perldancer.org >> >> Best, >> VinceW >> _______________________________________________ >> dancer-users mailing list >> dancer-users at dancer.pm >> http://lists.preshweb.co.uk/mailman/listinfo/dancer-users > > _______________________________________________ > dancer-users mailing list > dancer-users at dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users From david at cantrell.org.uk Tue Sep 16 13:41:06 2014 From: david at cantrell.org.uk (David Cantrell) Date: Tue, 16 Sep 2014 13:41:06 +0100 Subject: [dancer-users] Recent Perl 5.8 compatibility breakage: mro In-Reply-To: <54173EF3.7000706@etr-usa.com> References: <54173784.4020201@etr-usa.com> <54173EF3.7000706@etr-usa.com> Message-ID: <20140916124106.GC16658@bytemark.barnyard.co.uk> On Mon, Sep 15, 2014 at 01:33:07PM -0600, Warren Young wrote: > By walking back through the versions, it appears this breakage was > introduced in 1.3126. Unfortunately, there was no announcement on the > list for 1.3.126, so I can't guess what change required this. https://metacpan.org/diff/file?target=YANICK/Dancer-1.3126/&source=YANICK/Dancer-1.3125/ isn't very helpful in this case, but it's a good place to start when trying to figger out stuff like this. 'git blame' says it appeared in https://github.com/PerlDancer/Dancer/commit/53a8276 which ended up in https://github.com/PerlDancer/Dancer/tree/v1.3120, whose changelog leads us to https://github.com/PerlDancer/Dancer/pull/974. So it's a test to see if stuff works when mro Stuff has been turned on outside Dancer. -- David Cantrell | top google result for "topless karaoke murders" Blessed are the pessimists, for they test their backups From yanick at babyl.dyndns.org Tue Sep 16 15:58:39 2014 From: yanick at babyl.dyndns.org (Yanick Champoux) Date: Tue, 16 Sep 2014 10:58:39 -0400 Subject: [dancer-users] Recent Perl 5.8 compatibility breakage: mro In-Reply-To: <20140916124106.GC16658@bytemark.barnyard.co.uk> References: <54173784.4020201@etr-usa.com> <54173EF3.7000706@etr-usa.com> <20140916124106.GC16658@bytemark.barnyard.co.uk> Message-ID: <20140916145839.GA27926@gilgamesh.babyl.dyndns.org> On Tue, Sep 16, 2014 at 01:41:06PM +0100, David Cantrell wrote: > On Mon, Sep 15, 2014 at 01:33:07PM -0600, Warren Young wrote: > > > By walking back through the versions, it appears this breakage was > > introduced in 1.3126. Unfortunately, there was no announcement on the > > list for 1.3.126, so I can't guess what change required this. > > https://metacpan.org/diff/file?target=YANICK/Dancer-1.3126/&source=YANICK/Dancer-1.3125/ > > isn't very helpful in this case, but it's a good place to start when > trying to figger out stuff like this. > > 'git blame' says it appeared in > https://github.com/PerlDancer/Dancer/commit/53a8276 which ended up in > https://github.com/PerlDancer/Dancer/tree/v1.3120, whose changelog leads > us to https://github.com/PerlDancer/Dancer/pull/974. > > So it's a test to see if stuff works when mro Stuff has been turned on > outside Dancer. Excellent detective work. :-) And yeah, there was this new test, and then I did the massive switch to dzilla. One of the plugins I'm using is AutoPrereqs, and unfortunately a few bogus dependencies slipped in. Apologies for that, and with the release of yesterday, I think things should be alright now. Well, *most* things. There is still issue 1068, where monkeyswitching YAML to YAML::XS proved to cause issues with the new merging of configurations. A fix for that should be issued in the next few days. Joy, `/anick -- From hvo.pm at xs4all.nl Tue Sep 16 21:26:14 2014 From: hvo.pm at xs4all.nl (Henk van Oers) Date: Tue, 16 Sep 2014 22:26:14 +0200 (CEST) Subject: [dancer-users] Adopting Dancer::Plugin::Passphrase Message-ID: I am a user of Dancer::Plugin::Passphrase The author, James Aitken, is no longer among us. I would like to make a Dancer2::Plugin::Passphrase based on the work of James (c). Are others working on this? What would be the next stap? Regards, Henk van Oers PAUSE-ID: HVOERS Nic: HVO34-RIPE From james at ronanweb.co.uk Wed Sep 17 09:33:36 2014 From: james at ronanweb.co.uk (James Ronan) Date: Wed, 17 Sep 2014 09:33:36 +0100 Subject: [dancer-users] Adopting Dancer::Plugin::Passphrase In-Reply-To: References: Message-ID: <54194760.2070700@ronanweb.co.uk> On 16/09/14 21:26, Henk van Oers wrote: > > I am a user of Dancer::Plugin::Passphrase > The author, James Aitken, is no longer among us. > > I would like to make a Dancer2::Plugin::Passphrase > based on the work of James (c). I think the most sensible step, if no-one else is working on a similar module, would be for you to adopt Dancer::Plugin::Passphrase and release the Dancer2 version along side it. I think James would be glad to know his work was being updated and used. > Are others working on this? > What would be the next stap? Make a request for COMAINT on the dist, I'm sure the powers that be will grant it given that James is no longer able to "agree" it. If it helps, as his friend, I agree to it on his behalf ;) Cheers, JamesR -- James Ronan From msouth at gmail.com Wed Sep 17 18:29:46 2014 From: msouth at gmail.com (Mike South) Date: Wed, 17 Sep 2014 12:29:46 -0500 Subject: [dancer-users] Dancer 1 or Dancer 2? In-Reply-To: References: <5412B637.7080304@vincew.net> <5412F354.1090906@linuxia.de> Message-ID: On Fri, Sep 12, 2014 at 8:56 AM, Sawyer X wrote: > On Fri, Sep 12, 2014 at 3:21 PM, Stefan Hornburg (Racke) > wrote: > >> On 09/12/2014 02:35 PM, Sawyer X wrote: >> > Unfortunately that is a terrible example. The concept of blocking all >> requests in a before() hook is... let's say, naive. In reality you would >> like to simply block specific requests according to session, a la David >> Golden's Auth::Tiny. >> > [Disclaimer: I have only ever used Dancer1. I lurk here specifically so that I will know when things are stable enough to start building new stuff in Dancer2. Please pardon my ignorance or just press delete.] What do you mean by "in reality you would like to simply block specific requests according to session"? I have live code being used in a mission critical and highly sensitive project with a before hook (approximately) like this: hook before => sub { #whitelist /ip route as not needing any auth check return if (request->path_info =~ m{(^/ip$)|}); my $user = Dancer::Plugin::Auth::Extensible::Provider::Redacted->ip_login(); var user => $user; $user or die "no user"; }; This is very clean design; anyone adding a new route (and the nature of the project and team were such that this was happening without me really being able to oversee it, and contributions were being made by Dancer novices) could not accidentally make that route available without authentication. If they needed an un-authenticated route, they would have to go through the before hook. I'm not sure I'm understanding what you're talking about here (I don't know what a "route check" is, for example), but it sounds to me like Dancer2 removes this capability? > >> > The before hooks are basically run on every request. Static files are >> now served through the File handler. That means it will trigger the before >> hooks because it's a normal request. >> > I would love to do it using the Static middleware, but then it will >> happen before a route check on it, so we can't have that. >> >> I still disagree with this change of behaviour from Dancer 1 to Dancer 2. >> What is the benefit of calling before hook for public files? >> Also in a production environment you might deliver static files with some >> other software (Nginx, ...) and you loose control on >> these public files anyway. >> > > > The point is that this is not a selection of behavior. It isn't "we want a > before hook on public files", but "because public files are serves as a > handler, they will have before hooks called too". It's implicit behavior > because of the restructuring of public files as file handlers. > I suppose I could do the same as I have above but put in an exception in my before hook allowing through public files--would that be feasible in the new architecture? Rather than considering the cited example naive, I kind of think it's naive to think you _wouldn't_ have applications where everything served by code is locked down, and all static files are unrestricted. I would think you really want to have the option of having static files served with as little intervention by code as possible. mike -------------- next part -------------- An HTML attachment was scrubbed... URL: From jack.lareau at gmail.com Wed Sep 17 18:41:28 2014 From: jack.lareau at gmail.com (Jacques Lareau) Date: Wed, 17 Sep 2014 13:41:28 -0400 Subject: [dancer-users] Dancer 1 or Dancer 2? In-Reply-To: References: <5412B637.7080304@vincew.net> <5412F354.1090906@linuxia.de> Message-ID: That is exactly how I handle auth in all my apps. It's also shown as an example in the cookbook. Not sure why it's naive. On Wed, Sep 17, 2014 at 1:29 PM, Mike South wrote: > > > On Fri, Sep 12, 2014 at 8:56 AM, Sawyer X wrote: > >> On Fri, Sep 12, 2014 at 3:21 PM, Stefan Hornburg (Racke) < >> racke at linuxia.de> wrote: >> >>> On 09/12/2014 02:35 PM, Sawyer X wrote: >>> > Unfortunately that is a terrible example. The concept of blocking all >>> requests in a before() hook is... let's say, naive. In reality you would >>> like to simply block specific requests according to session, a la David >>> Golden's Auth::Tiny. >>> >> [Disclaimer: I have only ever used Dancer1. I lurk here specifically so > that I will know when things are stable enough to start building new stuff > in Dancer2. Please pardon my ignorance or just press delete.] > > What do you mean by "in reality you would like to simply block specific > requests according to session"? > > I have live code being used in a mission critical and highly sensitive > project with a before hook (approximately) like this: > > hook before => sub { > #whitelist /ip route as not needing any auth check > return if (request->path_info =~ m{(^/ip$)|}); > > my $user = > Dancer::Plugin::Auth::Extensible::Provider::Redacted->ip_login(); > > var user => $user; > > $user or die "no user"; > }; > > This is very clean design; anyone adding a new route (and the nature of > the project and team were such that this was happening without me really > being able to oversee it, and contributions were being made by Dancer > novices) could not accidentally make that route available without > authentication. If they needed an un-authenticated route, they would have > to go through the before hook. > > I'm not sure I'm understanding what you're talking about here (I don't > know what a "route check" is, for example), but it sounds to me like > Dancer2 removes this capability? > > > >>> > The before hooks are basically run on every request. Static files are >>> now served through the File handler. That means it will trigger the before >>> hooks because it's a normal request. >>> > I would love to do it using the Static middleware, but then it will >>> happen before a route check on it, so we can't have that. >>> >>> I still disagree with this change of behaviour from Dancer 1 to Dancer >>> 2. What is the benefit of calling before hook for public files? >>> Also in a production environment you might deliver static files with >>> some other software (Nginx, ...) and you loose control on >>> these public files anyway. >>> >> >> >> The point is that this is not a selection of behavior. It isn't "we want >> a before hook on public files", but "because public files are serves as a >> handler, they will have before hooks called too". It's implicit behavior >> because of the restructuring of public files as file handlers. >> > > I suppose I could do the same as I have above but put in an exception in > my before hook allowing through public files--would that be feasible in the > new architecture? > > Rather than considering the cited example naive, I kind of think it's > naive to think you _wouldn't_ have applications where everything served by > code is locked down, and all static files are unrestricted. > > I would think you really want to have the option of having static files > served with as little intervention by code as possible. > > mike > > _______________________________________________ > dancer-users mailing list > dancer-users at dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From xdg at xdg.me Wed Sep 17 19:18:22 2014 From: xdg at xdg.me (David Golden) Date: Wed, 17 Sep 2014 14:18:22 -0400 Subject: [dancer-users] Adopting Dancer::Plugin::Passphrase In-Reply-To: <54194760.2070700@ronanweb.co.uk> References: <54194760.2070700@ronanweb.co.uk> Message-ID: On Wed, Sep 17, 2014 at 4:33 AM, James Ronan wrote: > > If it helps, as his friend, I agree to it on his behalf ;) > James, Requests to the Dancer project for information/details on James' passing were not returned, so James' modules weren't put into the usual "custodial" status. Was an obituary published or are there additional details that can be shared to corroborate what happened? Regards, David Golden PAUSE Admin for IDs -- David Golden Twitter/IRC: @xdg -------------- next part -------------- An HTML attachment was scrubbed... URL: From james at ronanweb.co.uk Thu Sep 18 09:17:29 2014 From: james at ronanweb.co.uk (James Ronan) Date: Thu, 18 Sep 2014 09:17:29 +0100 Subject: [dancer-users] Adopting Dancer::Plugin::Passphrase In-Reply-To: References: <54194760.2070700@ronanweb.co.uk> Message-ID: <541A9519.3030606@ronanweb.co.uk> Hi David, On 17/09/14 19:18, David Golden wrote: > On Wed, Sep 17, 2014 at 4:33 AM, James Ronan > wrote: > > > If it helps, as his friend, I agree to it on his behalf ;) > > > James, > > Requests to the Dancer project for information/details on James' passing > were not returned, so James' modules weren't put into the usual > "custodial" status. Was an obituary published or are there additional > details that can be shared to corroborate what happened? As James was estranged from his family it took some time for them to be tracked down, and as a result it's been difficult for us to get any more information. As far as we know, the accident he had a couple of months previous to his passing - where by he was struck by a motor vehicle whilst on foot - was the underlying cause. When he returned to work, and we spent some time talking, he told me that the doctors had confirmed that he had some form of damage to his brain, but they were happy he was showing good progress with healing and so he was allowed to return to work. Over the course of those 2 months the injury to his leg was well on it's way to healing and he no longer required the walking stick he was using. About a week later we didn't hear from James for the tail end of a week (This was not uncommon as we all telecommute and occasionally we just get on with what we're doing). The shock came on the Monday morning when we had a message from his girlfriend that he had passed away. The details weren't clear, he had apparently returned to hospital because he was feeling unwell, as to whether he passed away in hospital or was again released we're unsure. Needless to say we didn't really press his girlfriend for more information given the situation. I can confirm however that due to the support of his friends, the Perl community and even some complete strangers, that James did get a decent funeral and a proper send off. So my personal thanks to all those that contributed, as it was a send off he deserved. Hope this helps shed some light, and allows us to keep James' modules going. Thanks again, JamesR -- James Ronan From james at ronanweb.co.uk Thu Sep 18 09:26:34 2014 From: james at ronanweb.co.uk (James Ronan) Date: Thu, 18 Sep 2014 09:26:34 +0100 Subject: [dancer-users] Adopting Dancer::Plugin::Passphrase In-Reply-To: <541A9519.3030606@ronanweb.co.uk> References: <54194760.2070700@ronanweb.co.uk> <541A9519.3030606@ronanweb.co.uk> Message-ID: <541A973A.8090206@ronanweb.co.uk> Further to this, regarding an obituary - I had a dig and found it: http://goo.gl/Ua6Mu3 On 18/09/14 09:17, James Ronan wrote: > Hi David, > > On 17/09/14 19:18, David Golden wrote: >> On Wed, Sep 17, 2014 at 4:33 AM, James Ronan > > wrote: >> >> >> If it helps, as his friend, I agree to it on his behalf ;) >> >> >> James, >> >> Requests to the Dancer project for information/details on James' passing >> were not returned, so James' modules weren't put into the usual >> "custodial" status. Was an obituary published or are there additional >> details that can be shared to corroborate what happened? > > As James was estranged from his family it took some time for them to be > tracked down, and as a result it's been difficult for us to get any more > information. > > As far as we know, the accident he had a couple of months previous to > his passing - where by he was struck by a motor vehicle whilst on foot - > was the underlying cause. > > When he returned to work, and we spent some time talking, he told me > that the doctors had confirmed that he had some form of damage to his > brain, but they were happy he was showing good progress with healing and > so he was allowed to return to work. Over the course of those 2 months > the injury to his leg was well on it's way to healing and he no longer > required the walking stick he was using. > > About a week later we didn't hear from James for the tail end of a week > (This was not uncommon as we all telecommute and occasionally we just > get on with what we're doing). The shock came on the Monday morning when > we had a message from his girlfriend that he had passed away. > The details weren't clear, he had apparently returned to hospital > because he was feeling unwell, as to whether he passed away in hospital > or was again released we're unsure. Needless to say we didn't really > press his girlfriend for more information given the situation. > > I can confirm however that due to the support of his friends, the Perl > community and even some complete strangers, that James did get a decent > funeral and a proper send off. So my personal thanks to all those that > contributed, as it was a send off he deserved. > > Hope this helps shed some light, and allows us to keep James' modules going. > > Thanks again, > JamesR > > -- James Ronan From fabrice.gabolde at gmail.com Thu Sep 18 09:36:53 2014 From: fabrice.gabolde at gmail.com (Fabrice Gabolde) Date: Thu, 18 Sep 2014 10:36:53 +0200 Subject: [dancer-users] Recent Perl 5.8 compatibility breakage: mro In-Reply-To: <20140916145839.GA27926@gilgamesh.babyl.dyndns.org> References: <54173784.4020201@etr-usa.com> <54173EF3.7000706@etr-usa.com> <20140916124106.GC16658@bytemark.barnyard.co.uk> <20140916145839.GA27926@gilgamesh.babyl.dyndns.org> Message-ID: On Tue, Sep 16, 2014 at 4:58 PM, Yanick Champoux wrote: > On Tue, Sep 16, 2014 at 01:41:06PM +0100, David Cantrell wrote: >> On Mon, Sep 15, 2014 at 01:33:07PM -0600, Warren Young wrote: >> >>> By walking back through the versions, it appears this breakage was >>> introduced in 1.3126. Unfortunately, there was no announcement on >>> the list for 1.3.126, so I can't guess what change required this. >> >> https://metacpan.org/diff/file?target=YANICK/Dancer-1.3126/&source=YANICK/Dancer-1.3125/ >> >> isn't very helpful in this case, but it's a good place to start when >> trying to figger out stuff like this. >> >> 'git blame' says it appeared in >> https://github.com/PerlDancer/Dancer/commit/53a8276 which ended up in >> https://github.com/PerlDancer/Dancer/tree/v1.3120, whose changelog leads >> us to https://github.com/PerlDancer/Dancer/pull/974. >> >> So it's a test to see if stuff works when mro Stuff has been turned on >> outside Dancer. > > Excellent detective work. :-) > > And yeah, there was this new test, and then I did the massive > switch to dzilla. One of the plugins I'm using is AutoPrereqs, > and unfortunately a few bogus dependencies slipped in. Apologies > for that, and with the release of yesterday, I think things should > be alright now. Indeed, excellent detective work. I'd have gotten away with it too, if not for those meddling kids... Just to clarify the MRO thing, I was the one who introduced both files (the TestPluginMRO.pm test lib and the 05b_plugins_and_c3.t test). It's a test to check that GH #974 is correctly implemented. I forget why plugins with C3 were a necessity at the time... it was a request from a coworker of mine and the fix was easy. The way the tests work is, 1. if we can load the TestPluginMRO library, it's a success; 2. if we can't and it's because the mro pragma is not available, we skip the tests; 3. if it's for another reason then the fix is not correct and we fail the tests. Step 2 ensured at the time that we would not penalize users with older installations. Since then Dancer switched to dzil with AutoPrereqs, which is easy to confuse in this sort of situation with optional modules. I note that this already caused a failure on old Perl installations (GH #1062)... because Test::More didn't have "skip" in very old versions :/ Sorry for the mess! -- Fabrice Gabolde From xdg at xdg.me Thu Sep 18 14:34:41 2014 From: xdg at xdg.me (David Golden) Date: Thu, 18 Sep 2014 09:34:41 -0400 Subject: [dancer-users] Adopting Dancer::Plugin::Passphrase In-Reply-To: <541A973A.8090206@ronanweb.co.uk> References: <54194760.2070700@ronanweb.co.uk> <541A9519.3030606@ronanweb.co.uk> <541A973A.8090206@ronanweb.co.uk> Message-ID: James, Thank you for filling in the missing pieces and providing an obituary link. I've transitioned JAITKEN to PAUSE custodial status and transferred his modules to the ADOPTME account. PAUSE maintainers will transfer ownership of those modules to anyone who volunteers to take over. Regards, David On Thu, Sep 18, 2014 at 4:26 AM, James Ronan wrote: > Further to this, regarding an obituary - I had a dig and found it: > > http://goo.gl/Ua6Mu3 > > > On 18/09/14 09:17, James Ronan wrote: > > Hi David, > > > > On 17/09/14 19:18, David Golden wrote: > >> On Wed, Sep 17, 2014 at 4:33 AM, James Ronan >> > wrote: > >> > >> > >> If it helps, as his friend, I agree to it on his behalf ;) > >> > >> > >> James, > >> > >> Requests to the Dancer project for information/details on James' passing > >> were not returned, so James' modules weren't put into the usual > >> "custodial" status. Was an obituary published or are there additional > >> details that can be shared to corroborate what happened? > > > > As James was estranged from his family it took some time for them to be > > tracked down, and as a result it's been difficult for us to get any more > > information. > > > > As far as we know, the accident he had a couple of months previous to > > his passing - where by he was struck by a motor vehicle whilst on foot - > > was the underlying cause. > > > > When he returned to work, and we spent some time talking, he told me > > that the doctors had confirmed that he had some form of damage to his > > brain, but they were happy he was showing good progress with healing and > > so he was allowed to return to work. Over the course of those 2 months > > the injury to his leg was well on it's way to healing and he no longer > > required the walking stick he was using. > > > > About a week later we didn't hear from James for the tail end of a week > > (This was not uncommon as we all telecommute and occasionally we just > > get on with what we're doing). The shock came on the Monday morning when > > we had a message from his girlfriend that he had passed away. > > The details weren't clear, he had apparently returned to hospital > > because he was feeling unwell, as to whether he passed away in hospital > > or was again released we're unsure. Needless to say we didn't really > > press his girlfriend for more information given the situation. > > > > I can confirm however that due to the support of his friends, the Perl > > community and even some complete strangers, that James did get a decent > > funeral and a proper send off. So my personal thanks to all those that > > contributed, as it was a send off he deserved. > > > > Hope this helps shed some light, and allows us to keep James' modules > going. > > > > Thanks again, > > JamesR > > > > > > -- > James Ronan > -- David Golden Twitter/IRC: @xdg -------------- next part -------------- An HTML attachment was scrubbed... URL: From hvo.pm at xs4all.nl Thu Sep 18 15:45:27 2014 From: hvo.pm at xs4all.nl (Henk van Oers) Date: Thu, 18 Sep 2014 16:45:27 +0200 (CEST) Subject: [dancer-users] Adopting Dancer::Plugin::Passphrase In-Reply-To: References: <54194760.2070700@ronanweb.co.uk> <541A9519.3030606@ronanweb.co.uk> <541A973A.8090206@ronanweb.co.uk> Message-ID: David, I'd like to adopt Dancer-Plugin-Passphrase My ID is HVOERS Regards, Henk PS @JR: Thank you for your help. On Thu, 18 Sep 2014, David Golden wrote: > James, > > Thank you for filling in the missing pieces and providing an obituary link.? I've transitioned JAITKEN to PAUSE custodial status > and transferred his modules to the ADOPTME account. > > PAUSE maintainers will transfer ownership of those modules to anyone who volunteers to take over. > > Regards, > David > > > On Thu, Sep 18, 2014 at 4:26 AM, James Ronan wrote: > Further to this, regarding an obituary - I had a dig and found it: > > http://goo.gl/Ua6Mu3 From davidp at preshweb.co.uk Thu Sep 18 15:58:24 2014 From: davidp at preshweb.co.uk (David Precious) Date: Thu, 18 Sep 2014 15:58:24 +0100 Subject: [dancer-users] Adopting Dancer::Plugin::Passphrase In-Reply-To: References: <54194760.2070700@ronanweb.co.uk> <541A9519.3030606@ronanweb.co.uk> <541A973A.8090206@ronanweb.co.uk> Message-ID: <20140918155824.457a8eb7@columbia> I'd be happy to take on James' Dancer::Session::DBI, as we're active users of it and happy to maintain it (I'm BIGPRESH on CPAN). I'd be tempted to take on the awesome Acme::Addslashes too, but I think it's reached the peak of perfection already ;) On Thu, 18 Sep 2014 09:34:41 -0400 David Golden wrote: > James, > > Thank you for filling in the missing pieces and providing an obituary > link. I've transitioned JAITKEN to PAUSE custodial status and > transferred his modules to the ADOPTME account. > > PAUSE maintainers will transfer ownership of those modules to anyone > who volunteers to take over. > > Regards, > David > > > On Thu, Sep 18, 2014 at 4:26 AM, James Ronan > wrote: > > > Further to this, regarding an obituary - I had a dig and found it: > > > > http://goo.gl/Ua6Mu3 > > > > > > On 18/09/14 09:17, James Ronan wrote: > > > Hi David, > > > > > > On 17/09/14 19:18, David Golden wrote: > > >> On Wed, Sep 17, 2014 at 4:33 AM, James Ronan > > >> > wrote: > > >> > > >> > > >> If it helps, as his friend, I agree to it on his behalf ;) > > >> > > >> > > >> James, > > >> > > >> Requests to the Dancer project for information/details on James' > > >> passing were not returned, so James' modules weren't put into > > >> the usual "custodial" status. Was an obituary published or are > > >> there additional details that can be shared to corroborate what > > >> happened? > > > > > > As James was estranged from his family it took some time for them > > > to be tracked down, and as a result it's been difficult for us to > > > get any more information. > > > > > > As far as we know, the accident he had a couple of months > > > previous to his passing - where by he was struck by a motor > > > vehicle whilst on foot - was the underlying cause. > > > > > > When he returned to work, and we spent some time talking, he told > > > me that the doctors had confirmed that he had some form of damage > > > to his brain, but they were happy he was showing good progress > > > with healing and so he was allowed to return to work. Over the > > > course of those 2 months the injury to his leg was well on it's > > > way to healing and he no longer required the walking stick he was > > > using. > > > > > > About a week later we didn't hear from James for the tail end of > > > a week (This was not uncommon as we all telecommute and > > > occasionally we just get on with what we're doing). The shock > > > came on the Monday morning when we had a message from his > > > girlfriend that he had passed away. The details weren't clear, he > > > had apparently returned to hospital because he was feeling > > > unwell, as to whether he passed away in hospital or was again > > > released we're unsure. Needless to say we didn't really press > > > his girlfriend for more information given the situation. > > > > > > I can confirm however that due to the support of his friends, the > > > Perl community and even some complete strangers, that James did > > > get a decent funeral and a proper send off. So my personal thanks > > > to all those that contributed, as it was a send off he deserved. > > > > > > Hope this helps shed some light, and allows us to keep James' > > > modules > > going. > > > > > > Thanks again, > > > JamesR > > > > > > > > > > -- > > James Ronan > > > > > -- David Precious ("bigpresh") 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 From racke at linuxia.de Fri Sep 19 14:09:23 2014 From: racke at linuxia.de (Stefan Hornburg (Racke)) Date: Fri, 19 Sep 2014 15:09:23 +0200 Subject: [dancer-users] Conference News Message-ID: <541C2B03.7020701@linuxia.de> About two weeks till the first Perl::Dancer conference starts! Schedule will be released on Monday with speakers from Dancer, DBIx::Class and Interchange, notably Sawyer X and ribasushi. There is still time to sneak in a presentation, hurry up! If you want to speak or simply attend, please register at our website http://act.perl.dance/. Regards Racke -- Perl and Dancer Development Visit our Perl::Dancer conference 2014: http://act.perl.dance/ From sarah.alm at financejobs.co Tue Sep 23 12:10:51 2014 From: sarah.alm at financejobs.co (Sarah Alm) Date: Tue, 23 Sep 2014 11:10:51 +0000 Subject: [dancer-users] Adding Finance Jobs to the dancefloor In-Reply-To: References: <20140914203116.GJ31523@debian> <20140915202659.GF5630@d1stkfactory> Message-ID: <20140923111051.GL5630@d1stkfactory> Hi Dancers, On Mon, Sep 15, 2014 at 11:26:34PM +0200, Sawyer X wrote: > I have added you to the website metadata. As soon as the website is > deployed (which happens automatically, if I recall correctly), you will > appear there! If you experience a delay, let us know. Just checking what you meant by "automatically"? Is there a way to kick it off manuall? Thanks again :) Sarah -- Sarah Alm https://www.financejobs.co From davidp at preshweb.co.uk Tue Sep 23 16:44:49 2014 From: davidp at preshweb.co.uk (David Precious) Date: Tue, 23 Sep 2014 16:44:49 +0100 Subject: [dancer-users] Adding Finance Jobs to the dancefloor In-Reply-To: <20140923111051.GL5630@d1stkfactory> References: <20140914203116.GJ31523@debian> <20140915202659.GF5630@d1stkfactory> <20140923111051.GL5630@d1stkfactory> Message-ID: <20140923164449.55e33d91@columbia> On Tue, 23 Sep 2014 11:10:51 +0000 Sarah Alm wrote: > On Mon, Sep 15, 2014 at 11:26:34PM +0200, Sawyer X wrote: > > I have added you to the website metadata. As soon as the website is > > deployed (which happens automatically, if I recall correctly), you > > will appear there! If you experience a delay, let us know. > > Just checking what you meant by "automatically"? Is there a way to > kick it off manuall? I've just manually deployed the change - I believe it certainly used to automatically pull changes from time to time, but I guess I disabled it, or it doesn't work any more. Anyway, it's there now, sorry for the wait Sarah! From sarah.alm at financejobs.co Tue Sep 23 22:13:08 2014 From: sarah.alm at financejobs.co (Sarah Alm) Date: Tue, 23 Sep 2014 21:13:08 +0000 Subject: [dancer-users] Adding Finance Jobs to the dancefloor In-Reply-To: <20140923164449.55e33d91@columbia> References: <20140914203116.GJ31523@debian> <20140915202659.GF5630@d1stkfactory> <20140923111051.GL5630@d1stkfactory> <20140923164449.55e33d91@columbia> Message-ID: <20140923211308.GP31523@debian> Hi David, On Tue, Sep 23, 2014 at 04:44:49PM +0100, David Precious wrote: > > Just checking what you meant by "automatically"? Is there a way to > > kick it off manuall? > > I've just manually deployed the change - I believe it certainly used to > automatically pull changes from time to time, but I guess I disabled > it, or it doesn't work any more. > > Anyway, it's there now, sorry for the wait Sarah! We can see it's up. Thanks for kicking it off! Always Dancing, Sarah -- Sarah Alm https://www.financejobs.co From lrg_ml at gmx.net Fri Sep 26 15:06:34 2014 From: lrg_ml at gmx.net (Lutz Gehlen) Date: Fri, 26 Sep 2014 16:06:34 +0200 Subject: [dancer-users] Mysterious restarts of development server Message-ID: <201409261606.34520.lrg_ml@gmx.net> Hello everybody, I have a problem with the builtin web server of Dancer1. I use it for development and testing purposes. Sometimes - I haven't figured out what triggers this behaviour, but it happens sometimes rather quickly, sometimes after running for hours or even days - the server mysteriously switches to the development environment and port 3000. I usually start the server like this (omitting some nohup and bash redirection stuff): perl bin/app.pl --port 7000 --environment production In the output I see this: >> Dancer 1.3123 server 13413 listening on http://0.0.0.0:7000 >> Dancer::Plugin::Database::Core (0.06) >> Dancer::Plugin::Lexicon (0.05) >> Dancer::Plugin::Database::Core::Handle (0.02) >> Dancer::Plugin::Database (2.09) >> Dancer::Plugin::Auth::Basic (0.030) >> Dancer::Plugin::EscapeHTML (0.22) >> Dancer::Plugin::Ajax (1.00) == Entering the production dance floor ... [13413] core @0.000008> Dancer::Session::Storable using session_dir : sessions in /data/perl5/biodatabase/lib/perl5/Dancer/Session/Storable.pm l. 35 [13413] core @0.013884> loading Dancer::Handler::Standalone handler in /data/perl5/biodatabase/lib/perl5/Dancer/Handler.pm l. 45 [13413] core @0.014051> loading handler 'Dancer::Handler::Standalone' in /data/perl5/biodatabase/lib/perl5/Dancer.pm l. 483 So far, so good, but then - after variable amounts of time as sketched above, this: >> Dancer 1.3123 server 13413 listening on http://0.0.0.0:3000 The problem is that obviously, from now on the server is not reachable under port 7000 any more, and eventually, my testers complain and I have to restart the server. As you can see, the process ID does not change. Does the server exec itself forgetting the command line parameters? Or what else happens? I hope someone can help me avoid this behaviour. Thanks a lot, Lutz From racke at linuxia.de Fri Sep 26 15:20:46 2014 From: racke at linuxia.de (Stefan Hornburg (Racke)) Date: Fri, 26 Sep 2014 16:20:46 +0200 Subject: [dancer-users] Mysterious restarts of development server In-Reply-To: <201409261606.34520.lrg_ml@gmx.net> References: <201409261606.34520.lrg_ml@gmx.net> Message-ID: <5425763E.7000402@linuxia.de> On 09/26/2014 04:06 PM, Lutz Gehlen wrote: > Hello everybody, > I have a problem with the builtin web server of Dancer1. I use it for > development and testing purposes. Sometimes - I haven't figured out what > triggers this behaviour, but it happens sometimes rather quickly, sometimes > after running for hours or even days - the server mysteriously switches to > the development environment and port 3000. > > I usually start the server like this (omitting some nohup and bash > redirection stuff): > perl bin/app.pl --port 7000 --environment production > > In the output I see this: >>> Dancer 1.3123 server 13413 listening on http://0.0.0.0:7000 >>> Dancer::Plugin::Database::Core (0.06) >>> Dancer::Plugin::Lexicon (0.05) >>> Dancer::Plugin::Database::Core::Handle (0.02) >>> Dancer::Plugin::Database (2.09) >>> Dancer::Plugin::Auth::Basic (0.030) >>> Dancer::Plugin::EscapeHTML (0.22) >>> Dancer::Plugin::Ajax (1.00) > == Entering the production dance floor ... > [13413] core @0.000008> Dancer::Session::Storable using session_dir : > sessions in /data/perl5/biodatabase/lib/perl5/Dancer/Session/Storable.pm l. > 35 > [13413] core @0.013884> loading Dancer::Handler::Standalone handler in > /data/perl5/biodatabase/lib/perl5/Dancer/Handler.pm l. 45 > [13413] core @0.014051> loading handler 'Dancer::Handler::Standalone' in > /data/perl5/biodatabase/lib/perl5/Dancer.pm l. 483 > > So far, so good, but then - after variable amounts of time as sketched > above, this: >>> Dancer 1.3123 server 13413 listening on http://0.0.0.0:3000 > > The problem is that obviously, from now on the server is not reachable > under port 7000 any more, and eventually, my testers complain and I have to > restart the server. > > As you can see, the process ID does not change. Does the server exec itself > forgetting the command line parameters? Or what else happens? I hope > someone can help me avoid this behaviour. My recommendation is not to use the builtin web server at all. You could use same deployment for live and development, just with a different Dancer environment. Which is usually quite simple with plackup and an init script. Regards Racke -- Perl and Dancer Development Visit our Perl::Dancer conference 2014: http://act.perl.dance/ From warren at etr-usa.com Fri Sep 26 16:21:43 2014 From: warren at etr-usa.com (Warren Young) Date: Fri, 26 Sep 2014 09:21:43 -0600 Subject: [dancer-users] Mysterious restarts of development server In-Reply-To: <201409261606.34520.lrg_ml@gmx.net> References: <201409261606.34520.lrg_ml@gmx.net> Message-ID: <54258487.5000504@etr-usa.com> On 9/26/2014 08:06, Lutz Gehlen wrote: > perl bin/app.pl --port 7000 --environment production I suspect what's going on there is that something causes Dancer to re-read config.yml, which makes it use whatever port and environment settings it finds there, or defaults if you haven't given them. Therefore, set the port number in either config.yml or in environment/production.yml, depending on whether that port is always used or only used for production mode. I've run Dancer for many days, possibly even weeks configured this way, using a nonstandard port, and it never changes out from under me. From warren at etr-usa.com Fri Sep 26 16:26:22 2014 From: warren at etr-usa.com (Warren Young) Date: Fri, 26 Sep 2014 09:26:22 -0600 Subject: [dancer-users] Mysterious restarts of development server In-Reply-To: <5425763E.7000402@linuxia.de> References: <201409261606.34520.lrg_ml@gmx.net> <5425763E.7000402@linuxia.de> Message-ID: <5425859E.2080601@etr-usa.com> On 9/26/2014 08:20, Stefan Hornburg (Racke) wrote: > > My recommendation is not to use the builtin web server at all. Why? I realize that some Plack-aware Perl web servers are faster than the one built into Dancer, but isn't offloading static content generation to a reverse proxy (e.g. nginx) a bigger overall win for a typical web app than adding complexity at the Dancer layer? You imply that there may be a stability problem with the built-in Dancer web server. I haven't had any problems with it yet. From hugues at max4mail.com Fri Sep 26 16:34:28 2014 From: hugues at max4mail.com (Hugues) Date: Fri, 26 Sep 2014 17:34:28 +0200 Subject: [dancer-users] Mysterious restarts of development server In-Reply-To: <5425763E.7000402@linuxia.de> References: <201409261606.34520.lrg_ml@gmx.net> <5425763E.7000402@linuxia.de> Message-ID: <54258784.204@max4mail.com> Hello Stephan I use build in server on port 80 ./bin/app.pl --port=80 and I send debug on my console ( via ssh ) it is quick to start and easy to develop with it The only one limitation I found is on ajax query ( it doesn't work correctly) and if I lost my console - server continue to work, but no really... you need to kill it in fact this is only for testing not for production - use ngnix or apache bye Hugues Le 26/09/2014 16:20, Stefan Hornburg (Racke) a ?crit : > On 09/26/2014 04:06 PM, Lutz Gehlen wrote: >> Hello everybody, >> I have a problem with the builtin web server of Dancer1. I use it for >> development and testing purposes. Sometimes - I haven't figured out what >> triggers this behaviour, but it happens sometimes rather quickly, sometimes >> after running for hours or even days - the server mysteriously switches to >> the development environment and port 3000. >> >> I usually start the server like this (omitting some nohup and bash >> redirection stuff): >> perl bin/app.pl --port 7000 --environment production >> >> In the output I see this: >>>> Dancer 1.3123 server 13413 listening on http://0.0.0.0:7000 >>>> Dancer::Plugin::Database::Core (0.06) >>>> Dancer::Plugin::Lexicon (0.05) >>>> Dancer::Plugin::Database::Core::Handle (0.02) >>>> Dancer::Plugin::Database (2.09) >>>> Dancer::Plugin::Auth::Basic (0.030) >>>> Dancer::Plugin::EscapeHTML (0.22) >>>> Dancer::Plugin::Ajax (1.00) >> == Entering the production dance floor ... >> [13413] core @0.000008> Dancer::Session::Storable using session_dir : >> sessions in /data/perl5/biodatabase/lib/perl5/Dancer/Session/Storable.pm l. >> 35 >> [13413] core @0.013884> loading Dancer::Handler::Standalone handler in >> /data/perl5/biodatabase/lib/perl5/Dancer/Handler.pm l. 45 >> [13413] core @0.014051> loading handler 'Dancer::Handler::Standalone' in >> /data/perl5/biodatabase/lib/perl5/Dancer.pm l. 483 >> >> So far, so good, but then - after variable amounts of time as sketched >> above, this: >>>> Dancer 1.3123 server 13413 listening on http://0.0.0.0:3000 >> The problem is that obviously, from now on the server is not reachable >> under port 7000 any more, and eventually, my testers complain and I have to >> restart the server. >> >> As you can see, the process ID does not change. Does the server exec itself >> forgetting the command line parameters? Or what else happens? I hope >> someone can help me avoid this behaviour. > My recommendation is not to use the builtin web server at all. > > You could use same deployment for live and development, just with > a different Dancer environment. > > Which is usually quite simple with plackup and an init script. > > Regards > Racke > From lrg_ml at gmx.net Fri Sep 26 16:45:56 2014 From: lrg_ml at gmx.net (Lutz Gehlen) Date: Fri, 26 Sep 2014 17:45:56 +0200 Subject: [dancer-users] Mysterious restarts of development server In-Reply-To: <5425763E.7000402@linuxia.de> References: <201409261606.34520.lrg_ml@gmx.net> <5425763E.7000402@linuxia.de> Message-ID: <201409261745.56190.lrg_ml@gmx.net> Hi Racke, On Friday 26.09.2014 16:20:46 Stefan Hornburg (Racke) wrote: > On 09/26/2014 04:06 PM, Lutz Gehlen wrote: [...] > > So far, so good, but then - after variable amounts of time as sketched > > > > above, this: > >>> Dancer 1.3123 server 13413 listening on http://0.0.0.0:3000 > > > > The problem is that obviously, from now on the server is not reachable > > under port 7000 any more, and eventually, my testers complain and I > > have to restart the server. > > > > As you can see, the process ID does not change. Does the server exec > > itself forgetting the command line parameters? Or what else happens? > > I hope someone can help me avoid this behaviour. > > My recommendation is not to use the builtin web server at all. > > You could use same deployment for live and development, just with > a different Dancer environment. > > Which is usually quite simple with plackup and an init script. Thanks for your quick reply. I'm testing plackup with Starman now. Cheers, Lutz From lrg_ml at gmx.net Fri Sep 26 17:12:08 2014 From: lrg_ml at gmx.net (Lutz Gehlen) Date: Fri, 26 Sep 2014 18:12:08 +0200 Subject: [dancer-users] Mysterious restarts of development server In-Reply-To: <54258487.5000504@etr-usa.com> References: <201409261606.34520.lrg_ml@gmx.net> <54258487.5000504@etr-usa.com> Message-ID: <201409261812.08846.lrg_ml@gmx.net> Hi Warren, thanks for your reply. On Friday 26.09.2014 17:21:43 Warren Young wrote: > On 9/26/2014 08:06, Lutz Gehlen wrote: > > perl bin/app.pl --port 7000 --environment production > > I suspect what's going on there is that something causes Dancer to > re-read config.yml, which makes it use whatever port and environment > settings it finds there, or defaults if you haven't given them. Hm, I wouldn't know what causes Dancer to reread the config. The behaviour I described certainly occurs without me touching any files under the application directory. > Therefore, set the port number in either config.yml or in > environment/production.yml, depending on whether that port is always > used or only used for production mode. I agree that would take care of the port switch. Still the application would switch from production to development, which is clearly much less of a problem, but an inconvenience all the same. > I've run Dancer for many days, possibly even weeks configured this way, > using a nonstandard port, and it never changes out from under me. Thanks for that feedback, certainly interesting to know. Cheers, Lutz From warren at etr-usa.com Fri Sep 26 18:02:43 2014 From: warren at etr-usa.com (Warren Young) Date: Fri, 26 Sep 2014 11:02:43 -0600 Subject: [dancer-users] Mysterious restarts of development server In-Reply-To: <201409261812.08846.lrg_ml@gmx.net> References: <201409261606.34520.lrg_ml@gmx.net> <54258487.5000504@etr-usa.com> <201409261812.08846.lrg_ml@gmx.net> Message-ID: <54259C33.5030709@etr-usa.com> On 9/26/2014 10:12, Lutz Gehlen wrote: > On Friday 26.09.2014 17:21:43 Warren Young wrote: > >> Therefore, set the port number in either config.yml or in >> environment/production.yml, depending on whether that port is always >> used or only used for production mode. > > I agree that would take care of the port switch. Still the application > would switch from production to development, Not if config.yml also has: environment: "production" Basically, config.yml entirely takes over the role of your command line parameters. From henk at signature.nl Fri Sep 26 22:19:51 2014 From: henk at signature.nl (Henk van Oers) Date: Fri, 26 Sep 2014 23:19:51 +0200 (CEST) Subject: [dancer-users] Dancer Advent Calendar In-Reply-To: References: Message-ID: On Sun, 14 Sep 2014, Sawyer X wrote: > Hi everyone, again, :) > I've taken the liberty to start a list of possible articles for the Dancer Advent Calendar (coming this December to a calendar > near you!) and I would be very happy if you could add your own suggestions. > > If you want to also indicate that you're going to write it yourself (whether for sure, or only tentatively), feel free to add > that too. > > https://github.com/PerlDancer/Dancer2/wiki/Advent-Calendar I'am not sure but I think the Dancer DSL (domain-specific language) can be implemented in a Perl6 grammar. Just add some semantics and: tada: Dancer6 :-) -- Henk From henk at signature.nl Fri Sep 26 22:34:55 2014 From: henk at signature.nl (Henk van Oers) Date: Fri, 26 Sep 2014 23:34:55 +0200 (CEST) Subject: [dancer-users] Dancer Plugins Maintainers team on Github In-Reply-To: <20140914231257.GA11440@gilgamesh.babyl.dyndns.org> References: <20140914231257.GA11440@gilgamesh.babyl.dyndns.org> Message-ID: On Sun, 14 Sep 2014, Yanick Champoux wrote: [...] > .. btw, is it me, or is that group could also be > named "the X-Men"? :-) Aha, that's why I can't adopt James Aitken's module. I have no X... From gabor at szabgab.com Mon Sep 29 06:27:37 2014 From: gabor at szabgab.com (Gabor Szabo) Date: Mon, 29 Sep 2014 08:27:37 +0300 Subject: [dancer-users] broken images on the dancefloor? Message-ID: Looking at http://perldancer.org/dancefloor I see several broken images: e.g sck.to Lyrics Badger Daystack Is that just me and my browser or are those broken for others as well? Gabor -------------- next part -------------- An HTML attachment was scrubbed... URL: From naveedm9 at gmail.com Mon Sep 29 06:40:22 2014 From: naveedm9 at gmail.com (Naveed Massjouni) Date: Mon, 29 Sep 2014 01:40:22 -0400 Subject: [dancer-users] broken images on the dancefloor? In-Reply-To: References: Message-ID: Also, CrowdTilt should be rename to Tilt and the link should be updated to https://www.tilt.com Thanks, Naveed On Mon, Sep 29, 2014 at 1:27 AM, Gabor Szabo wrote: > Looking at http://perldancer.org/dancefloor I see several broken images: > e.g > sck.to > Lyrics Badger > Daystack > > Is that just me and my browser or are those broken for others as well? > > Gabor > > > _______________________________________________ > dancer-users mailing list > dancer-users at dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tobias at kahunaburger.com Mon Sep 29 11:20:28 2014 From: tobias at kahunaburger.com (Tobias) Date: Mon, 29 Sep 2014 04:20:28 -0600 Subject: [dancer-users] broken images on the dancefloor? In-Reply-To: References: Message-ID: On Sun, Sep 28, 2014 at 11:27 PM, Gabor Szabo wrote: > Looking at http://perldancer.org/dancefloor I see several broken images: > e.g > sck.to > Lyrics Badger > Daystack > > Is that just me and my browser or are those broken for others as well? > It's 4 hrs later, but images load fine for me. --T -------------- next part -------------- An HTML attachment was scrubbed... URL: From tobias at kahunaburger.com Mon Sep 29 11:20:28 2014 From: tobias at kahunaburger.com (Tobias) Date: Mon, 29 Sep 2014 04:20:28 -0600 Subject: [dancer-users] broken images on the dancefloor? In-Reply-To: References: Message-ID: On Sun, Sep 28, 2014 at 11:27 PM, Gabor Szabo wrote: > Looking at http://perldancer.org/dancefloor I see several broken images: > e.g > sck.to > Lyrics Badger > Daystack > > Is that just me and my browser or are those broken for others as well? > It's 4 hrs later, but images load fine for me. --T -------------- next part -------------- An HTML attachment was scrubbed... URL: From hugues at max4mail.com Mon Sep 29 11:23:22 2014 From: hugues at max4mail.com (Hugues) Date: Mon, 29 Sep 2014 12:23:22 +0200 Subject: [dancer-users] broken images on the dancefloor? In-Reply-To: References: Message-ID: <5429331A.6090107@max4mail.com> some image, load correctly but not all not for this link *sck.to , **Lyrics Badger , **Daystack * Hugues. Le 29/09/2014 12:20, Tobias a ?crit : > On Sun, Sep 28, 2014 at 11:27 PM, Gabor Szabo > wrote: > > Looking at http://perldancer.org/dancefloor I see several broken > images: > e.g > sck.to > Lyrics Badger > Daystack > > Is that just me and my browser or are those broken for others as well? > > > It's 4 hrs later, but images load fine for me. > --T > > > _______________________________________________ > dancer-users mailing list > dancer-users at dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From xsawyerx at gmail.com Mon Sep 29 13:11:44 2014 From: xsawyerx at gmail.com (Sawyer X) Date: Mon, 29 Sep 2014 14:11:44 +0200 Subject: [dancer-users] broken images on the dancefloor? In-Reply-To: <5429331A.6090107@max4mail.com> References: <5429331A.6090107@max4mail.com> Message-ID: Unfortunately we don't automatically check these things. I recently removed a website because it wasn't working anymore and we had no idea. Paging Mr. Precious, what do you think? I don't mind writing the code, but the deployment is not automatic anymore, as it seems. I think it used to be by hook but every time I tried it recently, it failed. Any comment? Naveed, could you submit an issue on the perldancer-website repo? Thanks! :) On Mon, Sep 29, 2014 at 12:23 PM, Hugues wrote: > some image, load correctly but not all > not for this link > *sck.to , **Lyrics Badger > , **Daystack * > > Hugues. > > Le 29/09/2014 12:20, Tobias a ?crit : > > On Sun, Sep 28, 2014 at 11:27 PM, Gabor Szabo wrote: > >> Looking at http://perldancer.org/dancefloor I see several broken images: >> e.g >> sck.to >> Lyrics Badger >> Daystack >> >> Is that just me and my browser or are those broken for others as well? >> > > It's 4 hrs later, but images load fine for me. > --T > > > > _______________________________________________ > dancer-users mailing listdancer-users at dancer.pmhttp://lists.preshweb.co.uk/mailman/listinfo/dancer-users > > > > _______________________________________________ > dancer-users mailing list > dancer-users at dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From davidp at preshweb.co.uk Mon Sep 29 15:04:49 2014 From: davidp at preshweb.co.uk (David Precious) Date: Mon, 29 Sep 2014 15:04:49 +0100 Subject: [dancer-users] broken images on the dancefloor? In-Reply-To: References: <5429331A.6090107@max4mail.com> Message-ID: <20140929150449.653bdb2a@columbia> On Mon, 29 Sep 2014 14:11:44 +0200 Sawyer X wrote: > Unfortunately we don't automatically check these things. > > I recently removed a website because it wasn't working anymore and we > had no idea. > > Paging Mr. Precious, what do you think? I don't mind writing the > code, but the deployment is not automatic anymore, as it seems. I > think it used to be by hook but every time I tried it recently, it > failed. Any comment? Hmm - I think perhaps the best way would be a cron job that checks all the sites in dancefloor.yml once a day and emails if any are unreachable so we can remove them if they look to be gone for good. I'm not sure we'd want to do the checking in the site itself as it could delay the page load too much, and I'm not sure we'd want them automatically removed from the list as it could just be a temporary outage - for instance, Lyrics Badger was down but should be back up after DNS propagation. From xsawyerx at gmail.com Mon Sep 29 23:35:05 2014 From: xsawyerx at gmail.com (Sawyer X) Date: Tue, 30 Sep 2014 00:35:05 +0200 Subject: [dancer-users] broken images on the dancefloor? In-Reply-To: <20140929150449.653bdb2a@columbia> References: <5429331A.6090107@max4mail.com> <20140929150449.653bdb2a@columbia> Message-ID: On Mon, Sep 29, 2014 at 4:04 PM, David Precious wrote: > On Mon, 29 Sep 2014 14:11:44 +0200 > Sawyer X wrote: > > > Unfortunately we don't automatically check these things. > > > > I recently removed a website because it wasn't working anymore and we > > had no idea. > > > > Paging Mr. Precious, what do you think? I don't mind writing the > > code, but the deployment is not automatic anymore, as it seems. I > > think it used to be by hook but every time I tried it recently, it > > failed. Any comment? > > Hmm - I think perhaps the best way would be a cron job that checks all > the sites in dancefloor.yml once a day and emails if any are > unreachable so we can remove them if they look to be gone for good. > I'm not sure we'd want to do the checking in the site itself as it > could delay the page load too much, and I'm not sure we'd want them > automatically removed from the list as it could just be a temporary > outage - for instance, Lyrics Badger was down but should be back up > after DNS propagation. > That sounds like a good approach to me. :) -------------- next part -------------- An HTML attachment was scrubbed... URL: From xsawyerx at gmail.com Mon Sep 29 23:36:24 2014 From: xsawyerx at gmail.com (Sawyer X) Date: Tue, 30 Sep 2014 00:36:24 +0200 Subject: [dancer-users] Dancer Advent Calendar In-Reply-To: References: Message-ID: That sounds like a Perl 6 Advent Calendar article to me, not Dancer article. It is pretty cool though. :) On Fri, Sep 26, 2014 at 11:19 PM, Henk van Oers wrote: > > On Sun, 14 Sep 2014, Sawyer X wrote: > > Hi everyone, again, :) >> I've taken the liberty to start a list of possible articles for the >> Dancer Advent Calendar (coming this December to a calendar >> near you!) and I would be very happy if you could add your own >> suggestions. >> >> If you want to also indicate that you're going to write it yourself >> (whether for sure, or only tentatively), feel free to add >> that too. >> >> https://github.com/PerlDancer/Dancer2/wiki/Advent-Calendar >> > > I'am not sure but I think the Dancer DSL (domain-specific language) > can be implemented in a Perl6 grammar. > Just add some semantics and: tada: Dancer6 :-) > > -- > Henk > _______________________________________________ > dancer-users mailing list > dancer-users at dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at vincew.net Mon Sep 29 23:57:57 2014 From: info at vincew.net (VinceW) Date: Tue, 30 Sep 2014 00:57:57 +0200 Subject: [dancer-users] Dancer Advent Calendar In-Reply-To: References: Message-ID: <5429E3F5.2000209@vincew.net> On 09/14/2014 09:52 PM, Sawyer X wrote: > Hi everyone, again, :) > > I've taken the liberty to start a list of possible articles for the Dancer > Advent Calendar (coming this December to a calendar near you!) and I would > be very happy if you could add your own suggestions. Would a comparison between D1 and D2 be a fit item for the calendar. Recently I've started on such ... https://github.com/VinceW/Perl-dancer-diff Best, VinceW > If you want to also indicate that you're going to write it yourself > (whether for sure, or only tentatively), feel free to add that too. > > https://github.com/PerlDancer/Dancer2/wiki/Advent-Calendar > > > > _______________________________________________ > dancer-users mailing list > dancer-users at dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From xsawyerx at gmail.com Tue Sep 30 09:26:32 2014 From: xsawyerx at gmail.com (Sawyer X) Date: Tue, 30 Sep 2014 10:26:32 +0200 Subject: [dancer-users] Dancer Advent Calendar In-Reply-To: <5429E3F5.2000209@vincew.net> References: <5429E3F5.2000209@vincew.net> Message-ID: While this is a very useful resource (and I really wish we had a ticket for moving plugins which mentions this), it relates solely to available plugins and not architectural differences, which is what I had in mind. On Tue, Sep 30, 2014 at 12:57 AM, VinceW wrote: > On 09/14/2014 09:52 PM, Sawyer X wrote: > > Hi everyone, again, :) > > I've taken the liberty to start a list of possible articles for the Dancer > Advent Calendar (coming this December to a calendar near you!) and I would > be very happy if you could add your own suggestions. > > Would a comparison between D1 and D2 be a fit item for the calendar. > Recently I've started on such ... > https://github.com/VinceW/Perl-dancer-diff > > Best, > VinceW > > If you want to also indicate that you're going to write it yourself > (whether for sure, or only tentatively), feel free to add that too. > https://github.com/PerlDancer/Dancer2/wiki/Advent-Calendar > > > > _______________________________________________ > dancer-users mailing listdancer-users at dancer.pmhttp://lists.preshweb.co.uk/mailman/listinfo/dancer-users > > > > _______________________________________________ > dancer-users mailing list > dancer-users at dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: