Topic: Setting up more than 1 version of Apache?

[mrcullers]

These questions are probably quite advanced and looking for help from well seasoned experts. These questions are not for the intermediate or new comers to attempt to answer though all support is greatly appreciated.

Considering conf has "Listen" I would assume I could run more than one version of Apache on the same machine. I have heard of using a smaller simpler server to direct or redirect to other Apache servers in large setups.

Ok, basically what I want to be able to do is run both x64 and x32 Apache servers. Both with the option of running x64 & x32 PHP as well as the ability to switch between different versions of PHP 5.x.x as well.

Obviously this is a 100% pure development server for programming only. Serves no "Real" web sites, only things in development. So that will answer your question on why would I even want to do this? It is all about being able to test and prove software packages will/will not work under different environments. And to be able to produce adequate results in software setup packages when the environment is not adequate for the given package.

The Question:
Does anyone have any tips on how to setup an easy way to switch between different environments?

The only thing I can think of is setting up different configs where the main config is like so...

httpd.conf

[glsmith]

I have this, they're live though. Because I only have 1 IP outbound I have to do it with ports.

Apache 2.4.2: https://www.apachehaus.net/
Apache 2.2.22: http://www.apachehaus.net:85/

But you say this "no real websites" so if you have two internal IPs it shouldn't be hard. Everyone has 2 pretty much these days, 127.0.0.1 & 192.168.xxx.xxx

Set one to listen to 127.0.0.1 and another to listen to 192.168.xxx.xxx

If no real websites, and no real domains, using the hosts file just point

127.0.0.1 domain.com
192.168.xxx.xxx someother.com

I do not see how having the different confs would help when it comes to one x64 and one x86, but having different configs for one Apache, you could also use <IfDefine> and not have to even comment and uncomment

<IfDefine Setup1>
Include ServerSetup1.conf
</IfDefine>
<IfDefine Setup2>
Include ServerSetup2.conf
</IfDefine>
<IfDefine SetupN>
Include ServerSetupN.conf
</IfDefine>

Then just start Apache with
httpd -DSetup1
see http://httpd.apache.org/docs/2.2/mod/core.html#ifdefine

More than one actual instance require more than one IP or Port since only one thing can listen on any one port/IP combo

[mrcullers]

Awesome, someone with experience and understands exactly my intentions. Thank you for answering. I have only read your answer 1 time and it has not sunk in yet, but let me reply with, if it helps you answer further, with...

I am running this server on virtualbox on win7 x64 using the bridged networking adapter. I have 1 IP (local ip) under the NIC and 1 IP via a wireless card. So I have 2 IP's along with the 127.0.0.1.

I am also running with reserved IP's under port forwarding via the router.

UPDATE:

Ok, the ports sound like a very good solution. I do have .com's pointing my way via changeip.com dns sub domains. So not sure how the host file can help. I do have about 30 different domains pointing to my server.

[mrcullers]

Another question that has been on my mind for over 2 years now....

When I setup my virtual hosts file, I always setup the first virtual host as the "Titled as Default" account on the server. Simply because a long time ago I caught on to the fact that any unknown domains pointing to my server always default to the first account listed under virtual hosts.

The question is, is there any more to this theory I should know about? Is this really what is going on? Or is the effect to something else going on I am not aware of?

[glsmith]

No, that is the default host, anything to your IP with a hostname not configured will fall there as well as http://IPaddress

I used to keep script that would produce a big fat red GO AWAY! there when someone went to http://myIPaddress.

Different real domains to different Apache's:
Unless you have a router that supports it(are there any?), you need more than 1 IP out into the world so you can point the DNS to different IP addresses.