[boulder.pm] config modules?
KSmith at netLibrary.com
Fri Aug 23 11:21:24 CDT 2002
Well, personally, I don't like giving my non-programmer users the ability to
edit their configuration in any way except through an Interface I give them,
but I'm paranoid like that. *grin*
Probably an XML would work the best for a config file of the sort you're
Data::Dumper (freeze/thaw) should work quite nicely for storing some amount
of data, but isn't particularly editable.
Depends on how complicated you want to get, you could just have it be a
plain old text file, and regexp all your configs out.
From: Walter Pienciak [mailto:walter at frii.com]
Sent: Friday, August 23, 2002 9:33 AM
To: boulder-pm-list at happyfunball.pm.org
Subject: [boulder.pm] config modules?
I'm needing to separate out some config information into a separate
file, and traditionally I've always just done a Perlish thing like
%owners = (
'someresource' => 'somebody at mycompany',
'somethingelse' => 'someoneelse',
but this time nonprogrammer types will be using it, so . . .
There seem to ba about a half-zillion config modules out there
now. Anyone have any favorites? I can dig around, but this list
has been so quiet . . . I thought I'd poke it ;^)
More information about the Boulder-pm