After I wrote that big 5-part article on WWW::LastFM / XML::Rabbit I noticed several things that could be improved. One of them was the fact that loading configuration information from a file in the home directory was a pretty generic thing to do. I decided to factor that code out and release it as a separate CPAN module that can be used by any Moose class.

If you look at the code used to read the configuration information in the article mentioned above you'll see that it has improved quite a bit. The code below is shorter, but does the same thing as the old code.

package WWW::LastFM; use Moose; use namespace::autoclean; # Read configuration from ~/.lastfm.ini, # available in $self->config has 'config_filename' => ( is => 'ro', isa => 'Str', lazy_build => 1, ); sub _build_config_filename { '.lastfm.ini' } with 'Config::Role'; # And here we have our api key and secret has 'api_key' => ( is => 'ro', isa => 'Str', lazy_build => 1, ); sub _build_api_key { return (shift)->config->{'API'}->{'key'}; } has 'api_secret' => ( is => 'ro', isa => 'Str', lazy_build => 1, ); sub _build_api_secret { return (shift)->config->{'API'}->{'secret'}; } ...

The reason this approach is quite nice, is because it allows you to load e.g. username and password from a configuration file with the ability to override it in the constructor. You can also quite easily override the location to search for the configuration file in your tests by mocking the location returned by File::HomeDir->my_data() . Alternatively, you can specify either the config_file or config_files constructor parameters to explicitly specify the path to your configuration file (or an array reference of them).

I usually start my test case with code like this to override where to look for the configuration file for the test environment. Then I just put a copy of my configuration file inside the t folder with the same file name as usual.

# Mock home/config dir location { use File::HomeDir; no warnings 'redefine'; sub File::HomeDir::my_data { return 't'; } }

The configuration file is loaded via Config::Any->load_files() , so you can use any format supported by that module. Your config attribute will always be represented as a hash reference.

If you find this article or the CPAN module Config::Role useful I'd be very happy if you share it with your friends on Facebook, Google+, Twitter or other service you use. If you like what you see, follow me on any of the networks at the top of the page of my blog and subscribe to my feed to keep informed on when I post something new.