Re^2: Placing Catalyst Database Connections Settings Outside .conf File

Certainly a reasonable request.

I'll post the detailed errors. Coming up with simple instances that reproduce the problem is tough because, at least for me, Catalyst can be impenetrable.

Probably what I'll end up doing is creating two config files -- one to be read by Catalyst and one by the scripts, at least until I can figure out a better solution.

Comment on Re^2: Placing Catalyst Database Connections Settings Outside .conf File

Replies are listed 'Best First'.
Re^3: Placing Catalyst Database Connections Settings Outside .conf File by varanasi (Scribe) on Sep 08, 2016 at 22:26 UTC
I am a fool. When I set out to copy the exact language of the error I was getting with one of the options, I realized I was using the built-in server incorrectly -- if it is not run from the directory containing the catalyst app, it will load the app, report no errors but break when it cannot locate the database because of a path problem. Thanks for the advice and forbearance.	[reply]
Re^4: Placing Catalyst Database Connections Settings Outside .conf File by Your Mother (Archbishop) on Sep 09, 2016 at 13:56 UTC
This might be what you're after. `dsn => 'dbi:SQLite:' . SamPool->path_to('/data/SamPool.db'),` If not, check out Config::JFDI. Many Cat devs use this to consume the application's configuration in different contexts.	[reply] [d/l]