Ok, here's another suggestion: make several levels of config files; one file at the global level, one per v.server at the server level, and possibly a third file local on the v.server's directory for local changes. The order that you'd search these is up to you; if none of the configuration settings are security related parameters, I'd first search user, then v.server, then global; otherwise, you could play around with flagging certain configuration variables that can only be set in the global or v.server files.

This would allow changing one config parameters across a site at one file, while also allowing the end user some ability to configure their site as well.

-----------------------------------------------------
Dr. Michael K. Neylon - mneylon-pm@masemware.com || "You've left the lens cap of your mind on again, Pinky" - The Brain
It's not what you know, but knowing how to find it if you don't know that's important