SYNOPSIS

use Config::Any;
my $cfg = Config::Any->load_stems({stems => \@filepath_stems, ... });
# or
my $cfg = Config::Any->load_files({files => \@filepaths, ... });
for (@$cfg) {
my ($filename, $config) = %$_;
$class->config($config);
warn "loaded config from file: $filename";
}

DESCRIPTION

Config::Any provides a facility for Perl applications and libraries to load configuration data from multiple different file formats. It supports Apache-style configuration, Windows files, and even Perl code.

The rationale for this module is as follows: Perl programs are deployed on many different platforms and integrated with many different systems. Systems administrators and end users may prefer different configuration formats than the developers. The flexibility inherent in a multiple format configuration loader allows different users to make different choices, without generating extra work for the developers. As a developer you only need to learn a single interface to be able to use the power of different configuration formats.

INTERFACE

load_files( \%args )

 Config::Any->load_files( { files => \@files } );
 Config::Any->load_files( { files => \@files, filter => \&filter } );
 Config::Any->load_files( { files => \@files, use_ext => 1 } );
 Config::Any->load_files( { files => \@files, flatten_to_hash => 1 } );

attempts to load configuration from the list of files passed in the parameter, if the file exists.

If the parameter is set, it is used as a callback to modify the configuration data before it is returned. It will be passed a single hash-reference parameter which it should modify in-place.

If the parameter is defined, the loader will attempt to parse the file extension from each filename and will skip the file unless it matches a standard extension for the loading plugins. Only plugins whose standard extensions match the file extension will be used. For efficiency reasons, its use is encouraged, but be aware that you will lose flexibility --- for example, a file called containing data will not be offered to the plugin, whereas or would be.

When the parameter is defined, the loader will return a hash keyed on the file names, as opposed to the usual list of single-key hashes.

also supports a 'force_plugins' parameter, whose value should be an arrayref of plugin names like . Its intended use is to allow the use of a non-standard file extension while forcing it to be offered to a particular parser. It is not compatible with 'use_ext'.

You can supply a hashref to pass special options to a particular parser object. Example:

 Config::Any->load_files( { files => \@files, driver_args => {
 General => { -LowerCaseNames => 1 }
 } )

load_stems( \%args )

 Config::Any->load_stems( { stems => \@stems } );
 Config::Any->load_stems( { stems => \@stems, filter => \&filter } );
 Config::Any->load_stems( { stems => \@stems, use_ext => 1 } );
 Config::Any->load_stems( { stems => \@stems, flatten_to_hash => 1 } );

attempts to load configuration from a list of files which it generates by combining the filename stems list passed in the parameter with the potential filename extensions from each loader, which you can check with the classmethod described below. Once this list of possible filenames is built it is treated exactly as in above, as which it takes the same parameters. Please read the documentation before using this method.

finder( )

The classmethod returns the Module::Pluggable::Object object which is used to load the plugins. See the documentation for that module for more information.

plugins( )

The classmethod returns the names of configuration loading plugins as found by Module::Pluggable::Object.

extensions( )

The classmethod returns the possible file extensions which can be loaded by and . This may be useful if you set the parameter to those methods.

DIAGNOSTICS

"No files specified!" or "No stems specified!"

The and methods will issue this warning if called with an empty list of files/stems to load.

"_load requires a arrayref of file paths"

This fatal error will be thrown by the internal method. It should not occur but is specified here for completeness. If your code dies with this error, please email a failing test case to the authors below.

CONFIGURATION AND ENVIRONMENT

Config::Any requires no configuration files or environment variables.

DEPENDENCIES

Module::Pluggable::Object

And at least one of the following: Config::General Config::Tiny JSON::Syck YAML::Syck XML::Simple

INCOMPATIBILITIES

None reported.

BUGS AND LIMITATIONS

No bugs have been reported.

Please report any bugs or feature requests to , or through the web interface at <http://rt.cpan.org>.

AUTHOR

Joel Bernstein <[email protected]>

CONTRIBUTORS

This module was based on the original Catalyst::Plugin::ConfigLoader module by Brian Cassidy .

With ideas and support from Matt S Trout .

Further enhancements suggested by Evan Kaufman .

LICENCE AND COPYRIGHT

Copyright (c) 2006, Portugal Telecom . All rights reserved. Portions copyright 2007, Joel Bernstein .

This module is free software; you can redistribute it and/or modify it under the same terms as Perl itself. See perlartistic.

DISCLAIMER OF WARRANTY

(),