cgi-bin per site (i.e virtual host)

[pva]

Any of you who are running multiple domains with OSX Server web serving may have noticed that there is no way in the GUI to set the CGI directory differently for each virtual host (the same way we can set the document directory). If anyone from Apple is listening, Please add this feature!

More generally, has anyone found a clean way to add Apache directives to specific domains (really virtual hosts) without screwing up the GUI interface to the httpd_macosxserver.conf file?

This would be another nice feature Apple could add. I.e. a standard interface for adding custom Apache directives to each virtual host, since the GUI will never cover all possible situations.

.phil

[meancode]

what i would suggest is make a new conf file call it virtualdomain_cgi.conf and write an include into your httpd.conf file. the directives found in the httpd_macosxserver.conf file are included in the main httpd.conf file as well. yes it is annoying, isnt it. im not sure if Tennon's iTools would help out in the reguard. i have not had a chance to check them out. but i have had great reviews about it. but i just write seperate .conf files and include them into the main one just for my sanity, so i can find and modify exactly the directives per use (ie adding a new cgi bin, or adding a password protected folder outside of the document root - something you cannot do with Reams in the Server Admin GUI - but can do with apache). i find myself reading what is the the httpd_macosxserver.conf file and then adding to it in my own file since if you edit that file Server Admin wont work (another anoyence). hope this helps.

[pva]

The question I have is if I create an additional VirtualHost directive for the same site, will it add onto, or replace the one created by Server Admin?

Something like:

<VirtualHost 123.45.678.999>
ServerName www.site.com
ScriptAlias /cgi-bin/ "/Library/WebServer/site/cgi-bin/"
</Virtualhost>

In other words, will the many other directives specified in httpd_macosxserver.conf stay active for www.site.com in its VirtualHost block, or will I have to repeat them all?