[sf-perl] one install path, multiple repository paths
quinn at fairpath.com
Wed Apr 30 11:35:06 PDT 2008
Hi, David et al.,
My take on this is that you should step back from the problem, try to
make some simplifying assumptions, and take a different tack.
For instance, could you abstract out all (or most of) the differences in
config files into environment variables? For /etc/rc.d/*
scripts, could you make a single file that behaves differently based on
the setting of two variable called MY_ENVIRONMENT and MY_ROLE?
If you deploy the same config file to every machine, then it becomes
harder to mess things up. You don't have to keep track of what goes where.
You can edit a single file to see how things work in every environment
(or change how they work). You have fewer files and directories cluttering
This is just one way to go; TMTOWTDI. But if you're concerned that things
are too complicated already, then simplifying might work well.
Quinn Weaver, independent contractor | President, San Francisco Perl Mongers
http://fairpath.com/quinn/resume/ | http://sf.pm.org/
More information about the SanFrancisco-pm