|
From: David G. <da...@co...> - 2008-09-04 06:07:11
|
> > > > @Gingerdog: Please see also my comment below. I think there's a better > > solution than having the configuration inside the script... > > I think it's best to use something like vacation.conf as filename so > it's more clear it's a file you can edit. Yes; I'd agree. (yeah, I realised I'd committed my u/p in the vacation.pl script, but once it was done I didn't see much point in undoing it) The below is fine by me... David. > > > > a) in vacation.pl, change the "my $whatever" lines to something like > > > > our $db_username = 'your_username'; > > our $db_password = 'your_password'; > > > > b) We can then advise users to put their config to /etc/postfixadmin/vacation > > which could read like > > > > $db_username = 'cboltz'; > > $db_password = 'topsecret'; > > 1; # must return true, see perldoc -f require > > > > c) In vacation.pl, add (below the "our $whatever" lines) > > > > $configfile = "/etc/postfixadmin/vacation"; > > if (-f $configfile) require "$configfile"; > > > > -- David Goodwin [ david at codepoets dot co dot uk ] [ http://www.codepoets.co.uk ] |
