> What do people do to override configuration setting. Again, I use ttree to > generate the site, and ttree does a pre_process = config. I want "config" > to contain the settings where the real live site is, but I want an easy way > to override these when developing on a different machine. > > All I can think of is in config do a [% PROCESS myconfig %] after setting > my standard paths, and then have a blank myconfig file in the live site, > and do *not* place myconfig under CVS. Then when the site is checked out > by someone they just need to create their own "myconfig" file.
I was thinking it would be nice if AppConfig (this uses AppConfig, right?) could support layered configuration files, so you could override general setting in some kind of config equivalent of the site_perl directory or even a personal config path. That would solve this sort of problem pretty well. - Perrin
