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

2016-09-16 Thread Stefan Hornburg (Racke)
On 09/16/2016 12:38 PM, Nik Mitev wrote: > On 16/09/16 11:27, Stefan Hornburg (Racke) wrote: >>> I was after the db_info key however, and was getting the plugin settings >>> instead. This gets resolved if I ask for >>> $dsl->app->config->{'db_info'} >>> instead of >>> $dsl->config->{'db_info'} >>>

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

2016-09-16 Thread Nik Mitev
On 16/09/16 11:27, Stefan Hornburg (Racke) wrote: >> I was after the db_info key however, and was getting the plugin settings >> instead. This gets resolved if I ask for >> $dsl->app->config->{'db_info'} >> instead of >> $dsl->config->{'db_info'} >> >> Still not sure why $dsl->config->{'db_info'} r

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

2016-09-16 Thread Stefan Hornburg (Racke)
On 09/16/2016 12:21 PM, Nik Mitev wrote: > 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,

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

2016-09-16 Thread Nik Mitev
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

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

2016-09-16 Thread Stefan Hornburg (Racke)
On 09/16/2016 11:56 AM, Nik Mitev wrote: > On 16/09/16 10:31, Stefan Hornburg (Racke) wrote: >> On 09/16/2016 11:27 AM, Nik Mitev wrote: >>> Hi, >>> >>> A quick update, to make sure no one wastes time answering my initial >>> question... >>> Location of the config file is not the issue - within my

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

2016-09-16 Thread Nik Mitev
On 16/09/16 10:31, Stefan Hornburg (Racke) wrote: > On 09/16/2016 11:27 AM, Nik Mitev wrote: >> Hi, >> >> A quick update, to make sure no one wastes time answering my initial >> question... >> Location of the config file is not the issue - within my main app file >> (where the routes are defined)

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

2016-09-16 Thread Stefan Hornburg (Racke)
On 09/16/2016 11:27 AM, Nik Mitev wrote: > Hi, > > A quick update, to make sure no one wastes time answering my initial > question... > Location of the config file is not the issue - within my main app file (where > the routes are defined), the config hash > contains all of the configuration, an

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

2016-09-16 Thread Nik Mitev
Hi, A quick update, to make sure no one wastes time answering my initial question... Location of the config file is not the issue - within my main app file (where the routes are defined), the config hash contains all of the configuration, and the config.yml location. In a plugin I wrote however a