>> > > Yes, you can, but: > > 1. When you edit the file you risk messing up everything else.
There are risks everywhere. From a Leslie Nielsen movie (they're all alike): "Do you gamble?" "Every time I eat my wife's cooking." > 2. It can be harder to diff your changes into an updated version. One must apply rigor and do things in a standard fashion. Then the changes all show up where they should. No putting virtuals up in the middle of some place where they don't belong! > 3. Having a bunch of little files in the conf.d is the way they intended it. If I wanted lots of twisty little passages, I'd be writing .NET. But I prefer monolithic. That's why I'm a Fox guy. > 4. It's really handy if you're managing 100 domains; you just have to > edit the one you need to change. Fortunately, I'm just managing 99 domains. 99 domains in the Apache conf file 99 domains in the file Take one (site) offline, update a single line, 98 domains in the Apache conf file.... > 5. You can also grant permissions to change individual files to > different individuals. I do not have a snappy comeback to this one. Seriously, these are good points. I just wanted to point out that you didn't HAVE to use separate files if you just had a couple of virtuals to play around with. I'll have to try the separate file INCLUDES to see what's underneath. Whil _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
