I look after the intranet in our office, running Mac OS X Server 10.5.8. We have several applications running on the intranet - Bugzilla, TWiki, a few home grown apps and some static pages. (Don't use the OS X collaboration tools - we were using TWiki before they were available.)
There is one host set up, and all the apps run under that -
I've just read the chapter in Apache docs on virtual named hosts and I'm keen to try them. If I'm right, I'll end up with URLs like
http://twiki/, etc.? I know I also have to manage the DNS zone as well to add these names as aliases.
The advantages I can see are that it would make it easier to relocate an app to a different physical host should the need ever arise. We do have a dev set up for our public website, so having a virtual named host there makes it easier to test.
On the down side, I do have to manage DNS settings as well, whereas with a single host there is only one name to worry about.
What's the perceived wisdom here? Is this a good way to proceed?
Are there other advantages and disadvantages anyone would like to share before I make the leap. Or not.