Re: trying to isolate VirtualHosts running identical .pm's
I'm trying to configure a single box to host completely separate instances of development and test versions of the same code base (currently 49 modules). Right now I have 2 virtual hosts configured on the same IP and servername, but use different ports, i.e., 80 and 82. The only way I know to achieve what you want is to run two httpds with different configs. This has the added advantage that your developers can stop/start their server without impacting your testers. HTH, Simon. __ This email contains proprietary information some or all of which may be legally privileged. It is for the intended recipient only. If an addressing or transmission error has misdirected this email, please notify the author by replying to this email. If you are not the intended recipient you must not use, disclose, distribute, copy, print, or reply on this email. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: trying to isolate VirtualHosts running identical .pm's
This is what we do. Except we use the SAME config file, but we just have some conditionals that depend on which port number is being started up. -c At 3:47 PM + 11/17/00, [EMAIL PROTECTED] wrote: I'm trying to configure a single box to host completely separate instances of development and test versions of the same code base (currently 49 modules). Right now I have 2 virtual hosts configured on the same IP and servername, but use different ports, i.e., 80 and 82. The only way I know to achieve what you want is to run two httpds with different configs. This has the added advantage that your developers can stop/start their server without impacting your testers. HTH, Simon. __ This email contains proprietary information some or all of which may be legally privileged. It is for the intended recipient only. If an addressing or transmission error has misdirected this email, please notify the author by replying to this email. If you are not the intended recipient you must not use, disclose, distribute, copy, print, or reply on this email. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Chris Thorman (413) 473-0853 e-fax - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: trying to isolate VirtualHosts running identical .pm's
Scott Dayberry ([EMAIL PROTECTED]) said something to this effect: I'm trying to configure a single box to host completely separate instances of development and test versions of the same code base (currently 49 modules). Right now I have 2 virtual hosts configured on the same IP and servername, but use different ports, i.e., 80 and 82. Hey Scott, Try something like this: 1. Bind some addresses in the 192.168.0.x range to your main NIC, like hme0:1 bound to 192.168.0.1, hme0:2 bound to 192.168.0.2, etc. 2. Have each developer run their httpd process on one of the virtual addresses, bound to a high port (so they can restart the server without having root access). 3. Run a lightweight proxying front end (pretend the real address is 1.2.3.4): # # This is its httpd.conf # NameVirtualHost1.2.3.4:80 Location 1.2.3.4:80 ServerName dev-1.example.tld ProxyPass/ http://192.168.0.1:8000/ ProxyPassReverse / http://192.168.0.1:8000/ /Location Location 1.2.3.4:80 ServerName dev-2.example.tld ProxyPass/ http://192.168.0.2:8000/ ProxyPassReverse / http://192.168.0.2:8000/ /Location #...etc... All the development servers would point to the proxy's address in DNS, by the way, and its (the proxy's) virtual host configuration would take care of pushing the requests to the correct host. Make sure the front end has mod_proxy, of course. 4. Provided the front end server doesn't die or do something strange, it will faithfully proxy other servers back and forth. Hope this helps! (darren) -- Freedom is nothing else but the chance to do better. -- Camus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
