Ports Search

This module provides an API for loading and saving of simple configuration file records. Entries in the configuration file are essentially key,value pairs, with the key and values separated by a single equals symbol. The key consists only of alphanumeric characters. There are three types of values, scalar values can contain anything except newlines. Trailing whitespace will be trimmed unless the value is surrounded in double quotes.

A perl module that is designed to provide easy to use settings files for your project. You subclass the basic Config::Setting class in one of your own modules, and then provide an interface to your code using it. When set up, you can then override the settings on a per-host basis, or even using an environment variable. By default a win.ini style of configuration is used, but this can be overridden and an XML based configuration is also included. The access mechanism can also be overridden, the setting don't have to come from a file, but (maybe) from a web site. You'll have to write your own there, though.

This module implements yet another damn configuration-file system. The configuration language is deliberately simple and limited, and the module works hard to preserve as much information (section order, comments, etc.) as possible when a configuration file is updated. See Chapter 19 of "Perl Best Practices" (O'Reilly, 2005) for the rationale for this approach. The configuration language is a slight extension of the Windows INI format.

Config::Tiny is a perl class to read and write .ini style configuration files with as little code as possible, reducing load time and memory overhead. Memory usage is normally scoffed at in Perl, but in my opinion should be at least kept in mind. This module is primarily for reading human written files, and anything we write shouldn't need to have documentation/comments. If you need something with more power, move up to Config::Simple, Config::General or one of the many other Config:: modules.

This module allows to perform schema based configuration validation. The idea is to define in a schema what valid data is. This schema can be used to create a validator object that can in turn be used to make sure that some data indeed conforms to the schema. Although the primary focus is on "configuration" (for instance as provided by modules like Config::General) and, to a lesser extent, "options" (for instance as provided by modules like Getopt::Long), this module can in fact validate any data structure.

Daemon::Control provides a library for creating init scripts in perl. Your perl script just needs to set the accessors for what and how you want something to run and the library takes care of the rest. You can launch programs through the shell (/usr/sbin/my_program) or launch Perl code itself into a daemon mode. Single and double fork methods are supported and in double-fork mode all the things you would expect like reopening STDOUT/STDERR, switching UID/GID are supported.

Config::Versioned allows an application to access configuration parameters not only by parameter name, but also by version number. This allows for the configuration subsystem to store previous versions of the configuration parameters. When requesting the value for a specific attribute, the programmer specifies whether to fetch the most recent value or a previous value.

This module allows you to read configuration data written in a human-readable and easily-editable text format and access it as a perl data structure. It also allows you to write configuration data from perl back to this format. The data format allows key/value pairs, comments, escaping of unprintable or problematic characters, sensible whitespace handling, support for Unicode data, nested sections, or blocks, of configuration data.

Enlightenment Foundation Libraries is a set of libraries each providing a great deal of functionality.

Config::YAML is a somewhat object-oriented wrapper around the YAML module which makes reading and writing configuration files simple.