Archive for May, 2009

Autovivification bit me today

Tuesday, May 26th, 2009

For the first time in more than five years, I got bit by autovivification.  It’s one of those odd quirks of Perl that I’d read about, and heard the problems with but never bumped in to them.


Perl People are Great!

Friday, May 15th, 2009

I have been reading the Catalyst mailing list for a while.  I’m also subscribed to the DBIx::Class mailing list.  These are reasonably busy lists where converstations range from incredibly techincal arguments about ways to refactor the cor to new and confused people sticking their head in and asking questions.  Usually they’re polite and well thought posts from intelligent people.

This is a little different from a lot of Open Source projects!  (more…)

Debugging Catalyst

Saturday, May 9th, 2009

My last post discussed figuring out how part of Catalyst worked.  I had to put debug code in to a library and watch it run. How do you do tht?

It’s actually pretty easy, but it wasn’t obvious, at least to me.  It is on the debugging page of the Catalyst tutorial, but I missed it the first dozen times I read the page.


Catalyst and local configuration files

Saturday, May 2nd, 2009

This just took me two hours to debug, so I thought I’d go ahead and turn it in to a post…


Catalyst supports reading a config file. usually called myapp.conf.  You can also add extra configuration, but figuring out where it goes took me ages.

In a nutshell, Catalyst will read myapp.conf and myapp_local.conf.

You can change what the ‘local’ part in that is by setting an environment variable called MYAPP_CONFIG_LOCAL_SUFFIX or one called CATALYST_CONFIG_LOCAL_SUFFIX.

If MYAPP_CONFIG_LOCAL_SUFFIX is set, CATALYST_CONFIG_LOCAL_SUFFIX is apparently ignored.  (You don’t get two additional config files, just the one.)

MYAPP_CONFIG_LOCAL_SUFFIX applies only to MyApp, where CATALYST_CONFIG_LOCAL_SUFFIX will be applied to any Catalyst app.  Be careful with it. (more…)