> On Tue, Dec 1, 2009 at 3:48 PM, Sheryl <gubydala@xxxxxxx> wrote: > >> To back up a moment, though -- another way to do this is to define >> multiple IPs on the network card and run multiple instances of apache, >> each with different config files. We run 20 or more on some of our >> production servers. > > You could run one instance of apache and configure each VH to listen > in a different IP. At least that how I had it understood. Certainly. But whether or not that is desirable depends upon the environment. When I first started my current job we had a number of sites (in some cases 20 or more) running from one instance of apache. As I think I said elsewhere in the post you quoted, the problem with doing it that way is that you have to upgrade all sites at the same time, take down or restart all sites at one time when you have a configuration change for one site. If you're trying to run one instance of apache to serve several different organizations that can be a problem. One might resist change while another wants to be "bleeding edge". In the past couple of years we have separated each of our web sites into a separate "stack" with its own apache, mysql, tomcat, etc. Now if one customer organization wants a change we don't have to try and get 20 web site managers in 4 organizations to coordinate down time and acceptance testing. Having separate stacks also helps us prepare for making every site a VM eventually. Running everything from one instance uses a smaller footprint than running one instance per site, but "hardware is cheap" these days. Sheryl --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|