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

Form Validation Profantity
by Richard Reina 25 Oct '15

25 Oct '15

I am still working on form validation and figure I need to check for profanity in case some prankster wants to get cute with a form. Was looking at Regexp::Common::profanity but wondering how other dancer programmers have handled this in their own projects. Thanks P.S. I know that some are of the mind that filtering for profanity is not worth the effort. I respect that opinion but still want to try.

2 2

Re: [dancer-users] PONAPI
by Rick Leir 22 Oct '15

22 Oct '15

On Thu, Oct 22, 2015 at 7:00 AM, <dancer-users-request(a)dancer.pm> wrote: > Mickey Nasriachi from > booking.com introduced the audience to PONAPI. PONAPI is a Perl > implementation of the JSON-API spec > Google did not help me with this. Where is there info about this? And I sense the need for a plugin.. Thanks Rick

2 1

Authentication Question
by Richard Reina 22 Oct '15

22 Oct '15

2015-10-21 19:02 GMT-05:00 Richard Reina <gatorreina(a)gmail.com>: > Oops let me try again. So far in my app I have been restricting access to > registered users that have created an account by doing: > > get '/dashboard' => sub { > > if (! defined(session 'username')) { > > redirect '/'; } > > } > > Is this okay? I really don't have any special roles to authenicate just > need to make sure that registered users only get to certain pages -- pages > that would only make sence if you were a registered user in the first > place. Can I forgoe more formal and extensive authentication in my case? > > 2015-10-21 19:00 GMT-05:00 Richard Reina <gatorreina(a)gmail.com>: > >> So far in my app I have been restricting access to registered users that >> have created an account by doing: >> >> get '/dashboard' => sub { >> if (! defined(session 'username')) { redirect '/'; } } Is >> this okay? I really don't have any special roles >> to authenicate just need to make >> sure that registered users only get to certain >> pages -- pages that would only make >> sence if you were a registered user in the first >> place. Can I forgoe more formal >> and extensive authentication in my case? >> >> > > _______________________________________________ > dancer-users mailing list > dancer-users(a)dancer.pm > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users > >

3 3

First day of the Perl Dancer Conference
by Stefan Hornburg (Racke) 22 Oct '15

22 Oct '15

The first day of the Perl Dancer conference summed up by Gert van der Spoel: Day one of the Perl Dancer conference has come to an end. A long day with a many great talks, good food and beer! The conference room at Schani hotel was packed when Stefan (racke) kicked off the conference with a short welcome, after which Sawyer X gave an inspiring talk about the current state of Dancer 2. Very good statistics show that there is an active user base not afraid to create pull requests and fork the project. Further good news about a couple of new features brought the conference to a positive start. Next up, Thomas Klausner added a game to his talk, where each received a 'bingo' card with terms used in his talk about OAuth2, API's and Microservices. It didn't take long before the win was claimed with a loud 'Bullshit!' as tradition prescribes. The talk focused on the mess that large system can become and provided some real life examples on how things could be alleviated. Peter Rabbitson took the audience on a journey through DBIx::Class. While the resulting SQL queries were growing more complex by the minute, the actual Perl code needed to create these queries kept being readable. The advice that existing applications could gradually integrate DBIx::Class, without the need to rewrite complete applications, was met with positive responses. Last before lunch, Andrew Beverly from Ctrl-O gave a hands-on demonstration of the use of Plugin::Auth::Extensible. Using the DBIC provider, he quickly whipped up user authentication and roles based authorization. A plugin of value for Perl projects in need of any kind of authentication. After a, slightly longer than expected, lunch break, Mickey Nasriachi from booking.com introduced the audience to PONAPI. PONAPI is a Perl implementation of the JSON-API spec which enables developers to build REST-API based projects without the redundant discussion about the exchange of information between clients and servers. That lunch had made the group sharp and full of attention was shown through some quite good questions about the handling of sorting and limiting resultsets. Next Gert van der Spoel took the stage, picking up the OAuth2 baton from Thomas, but going more in depth with regard to implementation and implications for use of Social Logins in ecommerce environments. Especially for the conference he wrote extensions to Dancer and Dancer2 Oauth plugins to work with the wyngle.com Social Login provider. Šimun Kodžoman brought the attention to Meteor, an environment for building modern web applications in pure JavaScript, and Materialize, a modern responsive front-end framework which, combined with a Dancer backend, resulted in a state of the art mobile application. In his talk he explained the reasons for the choices made for the combination of Materialize-Meteor-Dancer and it now will need to prove itself in a production environment. The final talk of the day came from one of the long distance travelers to the conference, Sam Batschelet. Starting with some simple, descriptive slides about containers, he shocked the audience with the schematics of a SpaceCamps setup. But after going into each part of the ecosystem, he managed to bring the shock level to acceptable heights. He showed he had done his research and was well prepared answering each question that followed his talk. The official part of the first conference day concluded with a panel discussion. A panel consisting of Dancer(2) core developers Russell Jenkins, Mickey Nasriachi, Alexis Sukrieh, Sawyer X and Stefan Hornburg sat down and had the attendees fire off questions and remarks about various topics related to Dancer 2. Within an hour after the panel discussion the first results were checked into feature branches of Dancer 2 forks, a clear sign that putting the brilliant minds of Dancer(2) together in one place is worth it! After the fruitful first conference day, a large group of conference attendees met up at Deewan to enjoy some good Pakistani food, complemented with big, cool beers, brushing up the vocal chords for conversations, discussions and fun until the late hours. -- Perl and Dancer Development Visit our Perl::Dancer conference 2015. More information on https://www.perl.dance.

1 0

(no subject)
by Richard Reina 22 Oct '15

22 Oct '15

So far in my app I have been restricting access to registered users that have created an account by doing: get '/dashboard' => sub { if (! defined(session 'username')) { redirect '/'; } } Is this okay? I really don't have any special roles to authenicate just need to make sure that registered users only get to certain pages -- pages that would only make sence if you were a registered user in the first place. Can I forgoe more formal and extensive authentication in my case?

1 1

Getting param name of dynamically named <input> tag
by Richard Reina 21 Oct '15

21 Oct '15

I have a input tag in a form: <div class="col-xs-4 col-md-4"> <div id="p_scents"> <p> <label for="p_scnts"><input type="text" id="p_scnt" size="20" name="p_scnt" value="" placeholder="email address" /></label> </p> </div> </div> Which gets it's name from the JS function below. However, that name I can't figure out. I have tried p_scnt_1 but it comes back undefined. Any ideas what the param name would be for each sequentially added item? Here's a working example of the form: http://jsfiddle.net/jaredwilli/tzpg4/4/ $(function() { var scntDiv = $('#p_scents'); var i = $('#p_scents p').size() + 1; $('#addScnt').live('click', function() { $('<p><label for="p_scnts"><input type="text" id="p_scnt" size="20" name="p_scnt_' + i +'" value="" placeholder="Input Value" /></label> <a href="#" id="remScnt">Remove</a></p>').appendTo(scntDiv); i++; return false; }); $('#remScnt').live('click', function() { if( i > 2 ) { $(this).parents('p').remove(); i--; } return false; }); });

4 7

Re: [dancer-users] Delayed template processing
by Joerg Fallmann 16 Oct '15

16 Oct '15

Hi again, Does anybody know if and how it is possible to render a template for the user and then forward to a new route, Something like |get '/routeA/:*?' => sub { my $id = params->{'id'}; my $blub = params->{'blub'}; delayed { my $tt = Template->new( {INCLUDE_PATH => "$path", WRAPPER => 'layout.tt', RELATIVE => 1, }) || die "Template error: $Template::ERROR\n"; $tt->process('view.tt', { 'id' => $id, 'bla' => $blub }; flush; content $tt; done; }; forward '/routeB/',{ | ||'id' => $id, 'bla' => $blub| }; }; ||get '/routeB/:*?' => sub { my $id = params->{'id'}; my $blub = params->{'bla'}; # Do something from here on }; | That would solve the async response troubles for me I guess. @John, I'd rather try to do as much as possible without having to handle JSON additionally, if async streaming is possible the way I like to use it, I will have no other choice anyway I guess. --joerg

3 2

Re: [dancer-users] Delayed template processing
by Joerg Fallmann 14 Oct '15

14 Oct '15

Dear John, what I would like to do is to stay in one route, display whatever information I already have, so that the user can start reading output, while I continue processing until I have everything I need and update what the user can see with the final information. So similar to what delayed does when I use strings as content, with the difference that I would like to use templates filled with the initial content and update that templates content once processing is done. So far I have a myhost/welcomepage where the user can select some stuff and is then redirected to myhost/results. From the user input I can quickly create some content, but some other content takes some time, and I would like to show what I have fast at myhost/results and update myhost/results when the rest is done without redirecting to yet another route, instead of computing everything and then /push/ it to the user after minutes. @Amelia, I was playing around with delayed, and for me it works as expected when I only want to return simple stuff like in the manual, but when I try to use templates as content nothing happens until the very end of the route, so just the final output is created and no in-between output. Hope what I want to do is possible with Dancer2 --joerg On 10/14/2015 01:00 PM, dancer-users-request(a)dancer.pm wrote: > Send dancer-users mailing list submissions to > dancer-users(a)dancer.pm > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users > or, via email, send a message with subject or body 'help' to > dancer-users-request(a)dancer.pm > > You can reach the person managing the list at > dancer-users-owner(a)dancer.pm > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of dancer-users digest..." > > > Today's Topics: > > 1. Re: Recommendation for REST API (Pedro Melo) > 2. Delayed template processing (Joerg Fallmann) > 3. Re: REST plugin (Rick Leir) > 4. Re: Delayed template processing (Amelia Ireland) > 5. Re: Delayed template processing (John J. McDermott, CPLP) > 6. Form Validation Profantity (Richard Reina) > 7. Re: Form Validation Profantity (Andrew Solomon) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 13 Oct 2015 12:03:10 +0100 > From: Pedro Melo <melo(a)simplicidade.org> > To: Nuno Carvalho <smash(a)cpan.org>, Perl Dancer users mailing list > <dancer-users(a)dancer.pm> > Subject: Re: [dancer-users] Recommendation for REST API > Message-ID: > <CACCxPi2dPiiW-U21Wc7u2CeDjt-b=pViQtSTtEt5qGGdNWQJGw(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi, > > On Tue, Oct 13, 2015 at 11:37 AM, Nuno Carvalho <smash(a)cpan.org> wrote: > >> On Mon, Oct 12, 2015 at 8:16 PM, Pedro Melo <melo(a)simplicidade.org> wrote: >>> need to build a REST API with Dancer2. Any recommendations on what >> plugins, >>> if any, to use? >>> >>> I see Dancer2::Plugin::REST, is that the recommended one? It looks good? >> any >>> experiences with it? >> I always end up doing serialization "myself", instead of relying in >> plugins. Because many times there will be some edge cases that using >> the plugin will require a huge workaround. While handling the >> serialization yourself it's always easier to adapt. And even so I >> usually end up with very simple and clean applications like: >> >> sub '/users' => sub { >> to_json MyModel->users; >> }; >> >> If you prefer you can also use the "set serializer" option, to omit >> the to_json parts, or if you intend to have more than one serializer >> possible >> > Yeah? I have a base class for all my models so I'll probably take that > route. > > Thank you all,

2 1

Re: [dancer-users] REST plugin
by Rick Leir 13 Oct '15

13 Oct '15

On Tue, Oct 13, 2015 at 7:00 AM, <dancer-users-request(a)dancer.pm> wrote: > I see Dancer2::Plugin::REST, is that the recommended one? It looks good? > any > experiences with it? > My code serves REST without the use of that plugin. It was good, but it did not seem to help me much. I have been writing a simple decorator plugin to help with JWT JSON Web Tokens. So my route can look like this: check_auth ['post', 'put'] => '/cr_user' => sub { my ($jwt_sub) = @_; my $dir = _connect_dir(); my $role_valid ; my $ret; if( $jwt_sub) { my $admin_user = $dir->get_user({ username => $jwt_sub }); The plugin has this: use Crypt::JWT qw(encode_jwt decode_jwt); ... register 'check_auth' => sub { my ( $dsl, $pattern, @rest ) = @_; my $default_methods = [ 'get', 'post' ]; # If the given pattern is an ArrayRef, we override the defaults # and pass these onto to DSL->any() if( ref($pattern) eq "ARRAY" ) { $default_methods = $pattern; $pattern = shift(@rest); } my $code; for my $e (@rest) { $code = $e if ( ref($e) eq 'CODE' ) } my $content_type = plugin_setting->{content_type} || 'text/xml'; my $authenticated_route = sub { # Default response content type $dsl->response->header('Content-Type') or $dsl->response->content_type( $content_type ); # must be authenticated # get token from header my $jwt_sub; my $token = $dsl->request->header('authorization'); if ( $token) { # check the JWT of this request my $secret = plugin_setting->{'jwt_secret'}; try{ my $data = decode_jwt(token=>$token, key=>$secret); Much of this is copied from Dancer2::Plugin::Auth::Tiny by D.A. Golden. Now I should try Yanick's Plugin2. Cheers -- Rick

1 0

Recommendation for REST API
by Pedro Melo 13 Oct '15

13 Oct '15

Hi, need to build a REST API with Dancer2. Any recommendations on what plugins, if any, to use? I see Dancer2::Plugin::REST, is that the recommended one? It looks good… any experiences with it? Thanks in advance, -- Pedro Melo @pedromelo http://www.simplicidade.org/ xmpp:melo@simplicidade.org mailto:melo@simplicidade.org

3 3