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

RESOLUTION: Dancer2::Plugin::LogReport - basic setup
by Nathan Bailey 09 Feb '17

09 Feb '17

Hi all, For the archive/record, see below - all working now. I'd mis-indented the yml config. cheers, Nathan ---------- Forwarded message ---------- Date: 4 January 2017 at 21:18 Subject: Re: [dancer-users] Dancer2::Plugin::LogReport - basic setup Nevermind, I see I indented the yml incorrectly: logger: "LogReport" engines: logger: LogReport: log_format: %a%i%m app_name: AppName dispatchers: logfile: # "default" dispatcher stays open as well type: FILE to: /path/filename.log charset: utf-8 mode: DEBUG now works! And I see that adding the dispatcher line in a test harness lets me write errors to a file rather than stderr too. Brilliant! thanks, Nathan On 4 January 2017 at 19:51, Nathan Bailey <web@ <web(a)polynate.net>...> wrote: > On 4 January 2017 at 19:12, Andrew Beverley <andy@ <andy(a)andybev.com>...> > wrote: > >> On Wed, 4 Jan 2017 Nathan Bailey wrote: >> > 1. Add logging information to my yml >> >> Yes, although if you just want to test it initially, then you don't >> need any config and any messages will go to STDERR (I think). >> > > They happily print to STDERR, they just don't print to the log file :-) > > I have: > # The log level for this environment. Log warning and error messages* [ > presumably this doesn't conflict with the LogReport log levels? ]* > log: 'info' > > logger: "LogReport" > > engines: > logger: > LogReport: > log_format: %a%i%m > app_name: AppName > dispatchers: > logfile: # "default" dispatcher stays open as well > type: FILE > to: /path/filename.log > charset: utf-8 > mode: DEBUG > > >> > 2. Add use Log::Report (); >> >> This is no longer needed (sorry, I thought the docs had been updated). >> > > Okay, so I just have: > use Dancer2; > ... > use Dancer2::Plugin::LogReport mode => 'DEBUG'; # '3' or 'DEBUG' > > in my main route handler module. > > With this config, nothing is being written to my log file (ie. normal > 'info' messages that were getting written with: > logger: "File" > > engines: > logger: > File: > log_dir: "/path" > file_name: "filename.log" > (now removed and replaced with above) are no longer getting written. I > have a 'trace' and 'info' in a non-Dancer module that is writing to stderr. > > Log::Report maintains some global space that all messages go to. When a >> message is logged (regardless of where it is logged from) that will >> trigger the logging code in the Dancer plugin. The Dancer plugin knows >> your config, so it all Just Works. >> > > Nifty! Presumably module-based unit tests need to include Log::Report with > some suitable config/dispatcher? > > thanks, > Nathan >

2 4

Dancer2 app deployment
by Matthew Mallard 31 Jan '17

31 Jan '17

I’m not sure if anyone else is using Puppet to manage their systems, but if you do, this may be of interest to you. I’ve written a Puppet module that installs a systemd service for Dancer2 apps (other PSGI apps should work too): https://forge.puppet.com/qtechnologies/psgi I generally deploy my code with rsync and was using a script to start the apps, but it was starting to get messy as the number of apps grew. This way I know the service files will be installed consistently and the app will run automatically when it’s in production. It also fits in well my Nginx module, so a little bit of hiera data sets up Nginx proxying Dancer and using Let’s Encrypt certs. See here if that grabs your interest too: https://forge.puppet.com/qtechnologies/nginx Cheers, Matt

1 0

Dancer2 0.204003 fixes missing dependencies, improves error handling
by Jason A. Crome 25 Jan '17

25 Jan '17

>From http://blogs.perl.org/users/jason_a_crome/2017/01/dancer2-0204003-fixes-mis…: Dancer2 0.204003 is on its way to CPAN now, and provides the following changes: - The CPANTS testing service reported that some dependencies for Dancer2 were not specified in the distribution. This has been corrected, and we apologize for any issues this may have caused. - When a route exception occurred, Dancer2 would catch the error first, and would prevent any custom exception handling from trapping the exception. There were some ugly hacks for working around this, but this fix puts things right, and lets the exception hook fire first, and then will trap the error. - Several changes were made to Dancer2's Template Toolkit integration, the most significant of which being the removal of the ANYCASE option. - Various documentation improvements. A big thank you to those who contributed to this release and helped get it out the door. The full changelog is as follows: 0.204003 2017-01-25 15:21:40-06:00 America/Chicago [ BUG FIXES ] * GH #1299: Fix missing CPANTS prereqs (Mohammad S. Anwar) [ ENHANCEMENTS ] * GH #1249: Improve consistency with Template::Toolkit, using correct case for 'include_path', 'stop_tag', 'end_tag', and 'start_tag', removing ANYCASE option. (Klaus Ita) * Call route exception hook before logging an error, allowing devs to raise their own errors bedore D2 logging takes over. (Andy Beverley) [ DOCUMENTATION ] * Add another example of the delayed asynchronous mechanism (Ed @mohawk2 J., Sawyer X) * GH #1291: Document 'change_session_id' in Dancer2::Core::App. (Peter SysPete Mottram) * Fix typo in Dancer2::Core::Response (Gregorr Herrmann) * Document Dancer2::Plugin::RootURIFor (Mario Zieschang) Happy Dancing! Jason A. Crome / CromeDome On behalf of the Dancer Core Team

1 0

Dancer2::Plugin question
by Andrew Solomon 23 Jan '17

23 Jan '17

Hello People, I'm just catching up with the new and funky Dancer2::Plugin and I want to make sure I've understood the rationale of why it doesn't load 'strict' and 'warnings' for you like Dancer2 does. Is this because when you're writing a plugin, you're writing Perl rather than an application in the Dancer domain specific language? Andrew -- Andrew Solomon Mentor@Geekuni http://geekuni.com/ http://www.linkedin.com/in/asolomon

2 1

Updating to the new Dancer2 plugin system
by Amelia Ireland 13 Jan '17

13 Jan '17

Hello Dancers, What's the recommended procedure for converting a plugin that may import an unspecified number of keywords into the app? I use Dancer2::Plugin::LogContextual <https://github.com/wchristian/Dancer2-Plugin-LogContextual>, which imports a set of keywords via use Log::Contextual ':log' and redefines $SIG{__WARN__} for the application by adding an around method modifier to to_app. I'm unsure of the best way to handle this with the new plugin system (I am not the plugin author). A sample of the plugin code: around to_app => sub { my ( $attr, $self, @args ) = @_; my $app = $self->$attr( @args ); return sub { local $SIG{__WARN__} = sub { my @args = @_; log_warn { @args }; }; return $app->( @_ ); }; }; Any hints gratefully received. Thanks!

2 1

Dancer2::Plugin::LogReport - basic setup
by Nathan Bailey 04 Jan '17

04 Jan '17

Hi all, I'm endeavouring to use Dancer2::Plugin::LogReport so that all our errors go to one log file. As I understand the documentation (POD in Dancer2::Plugin::LogReport), I need to: 1. Add logging information to my yml 2. Add use Log::Report (); and use Dancer2::Plugin::LogReport mode => DEBUG; to my main route handler module 3. use Log::Report; in my modules Presumably, however, I need to tell the modules about my Log::Report configuration. Does this mean I need a: dispatcher 'FILE', 'log', mode => 'DEBUG', to => '/path/mylogfile.log'; in every method/subroutine? I assume not, but I can't see how the non-Dancer2 modules are getting the config information since they are ignorant of the .yml file. thanks, Nathan

2 1

Upgrade issue (maybe)
by Clive Eisen 04 Jan '17

04 Jan '17

I am moving a working Dancer2 app from centos6 to 7 When running it I get Class::XSAccessor: invalid instance method invocant: no hash ref supplied at /usr/local/share/perl5/Dancer2/Core/Role/Serializer.pm line 71. I have narrowed it down to a single line - if I comment this out the app starts fine - albeit with the data from $file_string missing and therefore useless $sql_config = from_yaml($file_string); But why on earth is it failing at compile time? Working on 6 - Dancer2 0.160003 Not working on 7 - Dancer2 0.204002 Downgraded 7 to 0.160003 - works have I missed something that changed between versions of Dancer2? TIA — Clive Eisen GPG: 75056DD0

2 1