% include( '/elements/header.html', 'Developer Documentation' ) %> <& /elements/menubar.html, 'Freeside Perl Modules' => $fsurl.'docs/library/FS.html', 'Complete Index' => $fsurl.'docs/library/index.html', &>
FS::Conf - Freeside configuration values
use FS::Conf;
$conf = new FS::Conf "/config/directory";
$FS::Conf::default_dir = "/config/directory";
$conf = new FS::Conf;
$dir = $conf->dir;
$value = $conf->config('key');
@list = $conf->config('key');
$bool = $conf->exists('key');
$conf->touch('key');
$conf->set('key' => 'value');
$conf->delete('key');
@config_items = $conf->config_items;
Read and write Freeside configuration values. Keys currently map to filenames, but this may change in the future.
Create a new configuration object. A directory arguement is required if $FS::Conf::default_dir has not been set.
Returns the conf directory.
Returns the base directory. By default this is /usr/local/etc/freeside.
Returns the configuration value or values (depending on context) for key.
Returns the exact scalar value for key.
Returns true if the specified key exists, even if the corresponding value is undefined.
Returns the configuration value or values (depending on context) for KEY_SUFFIX, if it exists, otherwise for KEY
Creates the specified configuration key if it does not exist.
Sets the specified configuration key to the given value.
Deletes the specified configuration key.
Returns all of the possible configuration items as FS::ConfItem objects. See FS::ConfItem.
If this was more than just crud that will never be useful outside Freeside I'd worry that config_items is freeside-specific and icky.
"Configuration" in the web interface (config/config.cgi).
httemplate/docs/config.html