virtual hosts in 10.5.5
I just started to look at setting up some name based virtual hosts on my os x server w/apache2 and have some questions. Most of the notes I can find through Google refer to manual editing of files rather than using server admin. The questions I have are:
1) Is there a differences in how virtual hosting might be done in the different versions of leopard server; standard, workgroup, and advanced?
2) So far, all the instr on the web I have seen require modification of etc/hosts, apache2/http.conf, and apace2/extra/httpd-vhosts.conf. On my install(advanced) httpd-vhosts.conf sits in apache2/sites but there is an apache2/origibnal/extra/httpd-vhosts.conf file. However, httpd.conf INCLUDEs sites/*.conf, not apache2/extra/*.conf. I just want to know if this is the new standard and Apple left some crumbs for existing installations or if Apple will always do this a little different from other unix?
3) Why not use server admin to set up virtual sites? I can see that etc/hosts might still have to be modified if there were no dns entries for the web sites but are there other issues?
1) Is there a differences in how virtual hosting might be done in the different versions of leopard server; standard, workgroup, and advanced?
2) So far, all the instr on the web I have seen require modification of etc/hosts, apache2/http.conf, and apace2/extra/httpd-vhosts.conf. On my install(advanced) httpd-vhosts.conf sits in apache2/sites but there is an apache2/origibnal/extra/httpd-vhosts.conf file. However, httpd.conf INCLUDEs sites/*.conf, not apache2/extra/*.conf. I just want to know if this is the new standard and Apple left some crumbs for existing installations or if Apple will always do this a little different from other unix?
3) Why not use server admin to set up virtual sites? I can see that etc/hosts might still have to be modified if there were no dns entries for the web sites but are there other issues?
Comments
In the conf directory under the Apache folder, there're some files that are just for reference, but will have no effect on your Apache installation, so you don't need to edit every single .conf files inside the conf directory.
The only configuration file Apache use by default when you startup Apache is httpd.conf. If you don't host many many sites, I suggest you to remove all include entries in httpd.conf, and put all of your settings in httpd.conf instead.
In this case, you won't need to worry about accidentally enabling settings that you probably will never use, but may cause you security problems when configured incorrectly. I wish you good luck.
http://clickontyler.com/virtualhostx/
That seems cool. I haven't tried it myself but I use server admin.
Laters...