[dancer-users] Explicitly defining location of config.yml (current hitch on path to running Dancer as a service)

Nik Mitev nik at mitev.eu
Fri Sep 16 11:21:46 BST 2016

On 16/09/16 11:04, Stefan Hornburg (Racke) wrote:
> You need to ask for the plugin config, e.g. with plugin_setting keyword.
That is indeed a shorter way of getting the settings for the plugin,
which I will use.
I was after the db_info key however, and was getting the plugin settings
instead. This gets resolved if I ask for
instead of

Still not sure why $dsl->config->{'db_info'} returns the data for
> A nicer way is to use an accessor in your plugin:
> https://metacpan.org/pod/Dancer2::Plugin#Getting-default-values-from-config-file
I don't consider myself a perl pro and frankly don't quite understand
the object-oriented side of it... still hoping I will not need to dig
into it :) Is it unreasonable to think I can maintain a Dancer2 app well
without learning object oriented perl?


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://lists.preshweb.co.uk/pipermail/dancer-users/attachments/20160916/4ddbe683/attachment.sig>

More information about the dancer-users mailing list