On Thu, Feb 19, 2015 at 10:30 AM, Jochen Lutz <jlu@gmx.de> wrote:

Am 19.02.15 um 17:21 schrieb Mike South:

On Thu, Feb 19, 2015 at 9:05 AM, Zahir Lalani <
ZahirLalani@oliver-marketing.com> wrote:

Perfect - amazed that its so sensitive to indentation! Very pythony :-)

[...]

A simple route that prints a Dumper of your config can be a useful thing in
debugging this sort of issue. (Or just a debug line like

debug Dumper(scalar config );

) can help with debugging this sort of thing.

You don't need routes or debug statements to do this, "x config" in the perl debugger just before executing "dance()" is enough.

Yes, there is more than one way to do it. If you throw a debug in somewhere or put a route in, you can just hit that route or look in the log at any point when you're doing whatever you're doing and you wonder if the config is structured the way you think or if you started it with the right config.

It should be said, though, that if you put it in a route, you should make sure you only let it run when the config is development (or some other similar safeguard) so you don't expose things like database passwords when you take it live.

mike