I'm using a config file as I work through the tutorial. This is an obvious thing to do and I completely agree with it. However, when I introduce this structure, I don't really want it to 'over-ride' existing values - I want to delete all the values which are now to be stored only in the config file.
I had to play around a bit. My model previously contained database connection information. When I introduce the config file, the values were taken from the file. However, when I deleted all of the relevant section from the Model, it broke the app. I needed to leave in a minimal stub:
schema_class => 'AddressBook::Schema::AddressDB');
PGConf 2017 - PostgreSQL High Availability in a Containerized World - My slides from today's presentation at #PGConfUS 2017 in Jersey City. * PostgreSQL High Availability in a Containerized World * from *Jignesh Shah*
4 weeks ago