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

Problem in normalize_path
by Oleg A. Mamontov 07 Sep '11

07 Sep '11

Hello. There is a new bug in &Dancer::FileUtils::normalize_path at 1.3072 :( Sample test: use Dancer::FileUtils 'path'; use Test::More 'no_plan'; is path('a/../b') => 'b'; is path('a/b/../../c') => 'c'; is path('a/b/c/../../../d') => 'd'; Output: ok 1 ok 2 not ok 3 # Failed test at t/q line 8. # got: 'a/b/d' # expected: 'd' There is wrong usage of regex with /g modifier. Simple patch is below: --- Dancer/FileUtils.pm.orig 2011-09-06 01:11:42.000000000 +0400 +++ Dancer/FileUtils.pm 2011-09-06 01:11:49.000000000 +0400 @@ -102,8 +102,7 @@ }x; $path =~ s{/\./}{/}g; - $path =~ s{$seqregex}{}g; - $path =~ s{$seqregex}{}g; + while ( $path =~ s{$seqregex}{} ) {} return $path; } But, imho, it's a bad idea to do any kind of 'universal path normalization'. What's the point? Only desire for aesthetics? Underlying FS is able to do it more reliable any case. POD on &File::Spec::canonpath talks us: "Note that this does *not* collapse x/../y sections into y. This is by design. If /foo on your system is a symlink to /bar/baz, then /foo/../quux is actually /bar/quux, not /quux as a naive ../−removal would give you. If you want to do this kind of processing, you probably want "Cwd"’s "realpath()" function to actually traverse the filesystem cleaning up paths like this." How do you suppose to handle hierarchy with symlinks? And &Cwd::realpath works like (3) realpath: "All components of file_name must exist when realpath() is called." Perhaps the best way is to drop path normalization code from Dancer::FileUtils completely? -- Cheers, Oleg A. Mamontov mailto: oleg(a)mamontov.net jabber: lonerr(a)charla.mamontov.net icq uin: 79-521-617 cell: +7-903-798-1352

2 1

Deploying two dancer apps in same virtual host on apache
by Alex Tang 06 Sep '11

06 Sep '11

Hi folks. I have two dancer apps (a front end UI, and a backend REST server) that i want to have deployed as separate dancer apps. I'd like to do this using apache. i can do it in any way under apache (i have the freedom to configure things most anyway i need). I've successfully deployed two apps using two different virtual hosts, however in this case, the frontend app sends pages back to the browser that contain AJAX requests that want to talk directly to the backend app. I can't do this via two different virtual hosts due to same-origin-policy, so i need to deploy both apps under the same virtual host. Any ideas on how to do this? I've been messing with the config files for a couple of hours, but to no avail. I checked on "the google", and on the dancer website, but the deployment guide only talks about multiple sites on the same host using Plack::Builder and starman, and to be honest, i don't really understand PSGI and Plack. Thanks a bunch. ...alex... PS, the latest version of my apache virtual host config can be found at http://paste.perldancer.org/2298W43paS2hg. It kind of works, but i think it only works because depending on how the apache worker was initialized, it's using one or the other dancer app.

3 3

web_ctl
by Mr. Puneet Kishor 03 Sep '11

03 Sep '11

I have created web_ctl.pl (with associated web_ctl.conf), a simple command line interface to managing Starman-powered Dancer apps. The git repo is at https://github.com/punkish/web_ctl It is nothing fancy, certainly not for you wizards out there, but I am finding it very useful to start/stop and to keep track of my various Dancer apps. Please feel free to suggest improvements. -- Puneet Kishor

1 0

giving the Dancer process via Starman a name
by Mr. Puneet Kishor 02 Sep '11

02 Sep '11

when I run `plackup -s Starman -p 5006 -w 10 -E development --access-log /path/to/app_access.log --error-log /path/to/app_error.log -D --pid /path/to/app.pid -a /path/to/app/bin/app.pl` it shows up in `ps` as 'starman master' and 'starman worker' punkish@Lucknow ~/bin$ps -fax | grep '[s]tarman' 501 4882 1 0 7:54AM ?? 0:00.04 starman master 501 4883 4882 0 7:54AM ?? 0:00.00 starman worker 501 4884 4882 0 7:54AM ?? 0:00.00 starman worker 501 4885 4882 0 7:54AM ?? 0:00.00 starman worker 501 4886 4882 0 7:54AM ?? 0:00.00 starman worker 501 4887 4882 0 7:54AM ?? 0:00.00 starman worker Is there anyway I can make those processes have specific names, for example, 'app master' and 'app worker" in the above instance?

4 3

Perl developer roles with Dancer experience in London / telecommuting
by David Precious 02 Sep '11

02 Sep '11

Just a quick message to say that my employer are looking for talented Perl developers, preferably with some experience with Dancer (although that's not essential), to work either in London or working from home / telecommuting most of the time. with a day a week in the London-based office. Good company, good salary & benefits, a talented team already in place, and free beer :) We're mainly looking for permanent roles, but contract roles may be considered too. If anyone is interested, feel free to contact me for more details! -- David Precious ("bigpresh") http://www.preshweb.co.uk/ "Programming is like sex. One mistake and you have to support it for the rest of your life". (Michael Sinz)

1 0

What about substitutions in config files?
by Oleg A. Mamontov 01 Sep '11

01 Sep '11

Hello! There is one useful feature in Catalyst::Plugin::ConfigLoader - substitutions before parsing config: http://search.cpan.org/~bricas/Catalyst-Plugin-ConfigLoader-0.30/lib/Cataly… Sometimes it's comfortably to use paths relative to 'appdir' or 'public'. Cwd (current working directory) depends on your setup (mod_per,plack,etc.) In my case (plackup under supervise) cwd is under service (daemontools specific) directory. I have adjusted Dancer::Config slightly: --- Dancer/Config.pm.orig 2011-09-01 18:50:30.000000000 +0400 +++ Dancer/Config.pm 2011-09-01 19:00:54.000000000 +0400 @@ -200,7 +200,14 @@ my $config; - eval { $config = YAML::LoadFile($file) }; + my $yaml = do { + open my $fh, $file or + confess "Unable to load the configuration file: $file: $!"; + local $/ = <$fh>; + }; + $yaml =~ s/__setting$(appdir|confdir|public|views)$__/setting($1)/ge; + + eval { $config = YAML::Load($yaml) }; if (my $err = $@ || (!$config)) { confess "Unable to parse the configuration file: $file: $@"; } This little patch allowed me to use relative paths in config.yml without worry about my top-level setup: engines: xslate: cache_dir: '__setting(appdir)__/var/xslate' path: [ '/','__setting(views)__' ] photos: basedir: '__setting(appdir)__/photos' What do you think about inclusion this functionality in Dancer core? -- Cheers, Oleg A. Mamontov mailto: oleg(a)mamontov.net jabber: lonerr(a)charla.mamontov.net icq uin: 79-521-617 cell: +7-903-798-1352

1 0

entering before_template_render hook
by Nick Knutov 30 Aug '11

30 Aug '11

Hello all, use Dancer ':script'; ... my $comment = template ... ... [6703] core @0.000008> entering before_template_render hook in /usr/local/share/perl/5.10.1/Dancer/Hook.pm l. 57 Why this can occurs? How to disable this message? -- Best Regards, Nick Knutov http://knutov.com ICQ: 272873706 Voice: +7-904-84-23-130

2 1

New stable release: 1.3072
by Alexis Sukrieh 23 Aug '11

23 Aug '11

Hey fellow dancers! The Dancer Core Team is happy to announce the release of Dancer 1.3072, codename "Precious David Precious". This release provides more flexibility in send_file (send raw content), minor bug fixes and some documentation improvements. https://metacpan.org/release/XSAWYERX/Dancer-1.3072 This release has been prepared and shipped to CPAN by Sawyer X, it should hit your favorite mirror soon. The changelog delta since 1.3071 follows: [ BUG FIXES ] * Fix prefix behavior with load_app (alexrj) * send_file() shouldn't clobber previously-set response status (David Precious, reported by tylerdu - thanks!) * Depend on URI 1.59 - Fixes problems when redirecting with UTF-8 strings (Alberto Simões) * Fix before_serializer POD fix (Yanick Champoux) [ ENHANCEMENTS ] * send_file can send data (pass a reference to a scalar), and can specify a content-disposition filename. (Alberto Simões) * Set 'Server' HTTP response header as well as 'X-Powered-By'. For cases where Dancer is being accessed directly, or the proxy passes on this header, it's nice to see it. (David Precious) [ DOCUMENTATION ] * Cookbook links to canonical documentation of keywords in Dancer.pm, so readers encountering a new keyword can easily see the docs for it (David Precious) * Docs for debug/warning/error link to Dancer::Logger for details on how to control where logs go (David Precious) * Document import_warnings option, and mention it & link to that documentation in opportune places. * Document that 'get' also creates a route for 'HEAD' requests (David Precious, prompted by Matt S Trout) * Extend request() keyword docs with examples (David Precious) * Correct port in Lighty/FCGI example in Dancer::Deployment (David Precious, thanks to pwfraley in Issue 621) The next stable release will be 1.3080, as always we will first ship at least one RC as a DEVELOPER version (which will be 1.3079_02). Happy dancing! -- Alexis Sukrieh -+- Hackers gonna hack! “The problem with quotes on the Internet is that you can't always be sure of their authenticity.” -- Abraham Lincoln http://sukria.net http://twitter.com/sukria

2 1

Rejoindre mon réseau sur LinkedIn
by woosley xu via LinkedIn 22 Aug '11

22 Aug '11

LinkedIn ------------ woosley xu souhaite se connecter à vous sur LinkedIn : ------------------------------------------ Je vous invite à faire partie de mon réseau professionnel en ligne sur le site LinkedIn. Accepter l'invitation de woosley xu http://www.linkedin.com/e/-dmhwk6-grmsa8qq-8/XDTwb9U_Go0kODHjgNTbVSU_GX14lx… Voir l'invitation de woosley xu http://www.linkedin.com/e/-dmhwk6-grmsa8qq-8/XDTwb9U_Go0kODHjgNTbVSU_GX14lx… -- (c) 2011, LinkedIn Corporation

1 0

Feedback requested: streaming support
by sawyer x 20 Aug '11

20 Aug '11

Hey everyone, I've been working on a nice feature and I wanted to get some feedback from the community before it's merged. We want to merge this by the beginning of next week and release it, so *early feedback is important*. Don't let this linger for long. In short: skim though the email, check the examples, let me know if it makes sense. That is all. We've been asked several times for streaming support. While we're built on PSGI and that allows you to separate that part into another layer (outside of Dancer, but within the same server instance), people wanted to be able to do streaming from inside Dancer - which makes sense, obviously. Recently I've hacked on this and set up a new branch on the Dancer github repo: "feature/send_data_streaming". Right now it adds support for send_file() but I intend to refactor this out to another keyword. I have a few bells and whistles here but before I show it, I want to explain the type of feedback I'm interested in: 1. Is it useful for you? 2. Are the examples here helpful? Is the syntax understandable? 3. If not, what would be a more suitable syntax, in your opinion? 4. Are there enough features? Do you need more power, more options? 5. How are you doing today? Feel free to share. :) *The basics:* Basically I've added the ability to ask send_file() to send the file (or straight content, as send_file() supports a scalar ref as pure data to send to the user) streamingly. It uses the PSGI spec for this, so it's 100% compatible, no magic of any kind. You can ask it to be streamed using a simple flag: send_file( 'log.txt', streaming => 1 ); This will send the file one line at a time. This also works on scalar refs: send_file( \'my string to stream back', streaming => 1, ... ); *Method callbacks:* I wanted users to be able to control what happens before each line and after each line streamed. You can do that using method callbacks. These callbacks also get the line as a parameter so you can do stuff with it. send_file( 'log.txt', streaming => 1, before_cb => sub { my $line = shift; say "About to send a line: $line" }, after_cb => sub { my $line = shift; say "Just sent the line: $line" }, ); However, this wasn't enough for me. What if I don't want to stream one line at a time. What if it's a binary and I want to stream it 512K at a time? You're able to do that too. You can override the method that gets the content's file handle and you can control what happens: send_file( $binfile, streaming => 1, around_cb => sub { my $content_fh = shift; # now I can do whatever I want with it }, ); *Complete control:* Here's another thought. While we're at it, how about we allow people to take over the ENTIRE operation? We can do that, using a method override. Take into account you should understand how PSGI streaming works, but this means you can really go all out. send_file( $binfile, streaming => 1, override_cb => sub { my ( $respond, $response ) = @_; my $writer = $respond->( [ $newstatus, $newheaders ] ); $writer->write('some line'); }, ); This might seem scary. It is, a bit. Like I said, you should know what you're doing. And if you do - hell - you get ALL the control right there. Things to note: 1. I want to refactor out the logic so it will be available in another keyword, like "send_streaming(...)". Will that be useful for anyone? 2. This might mean that you won't need to use "override_cb". 3. Do the callback names make sense? 4. Would you prefer getting the original method inside the "around_cb"? Should an around_cb with the content be named differently? What do you suggest? 5. I intend to add nonblocking streaming which will allow to run a request, answer it and run other stuff at the same request call. 6. "Blocking streaming" doesn't block the server, just the specific request. Other requests aren't blocked. Apologies for a long mail and thanks in advanced to anyone answering. :) Have a great weekend, Sawyer.

4 7