[support] Accessing multiple virtual sites on a development machine

[John Summerfield]

Alison wrote:
>
> Hey it works. Thanks guys.
>
> By setting httpd.conf virtuals in my development machine to dev.xxxxx.com, etc,
> and including a hosts file in my Windows box I can access both my development
> and production sites concurrently.

I'd not use names from the .com namespace, lest there be (or become) a 
legitimate owner. You don't need a public namespace for private purposes.

.lan and .dev both have some risk (it seems the AFL wants .afl), but 
less than .com. Probably, .local is best, but I used .lan before I ever 
heard of .local. I used to use .networking back when I wrote this, 
http://www.eracc.com/content/john-summerfield-setting-home-lan but I 
decided it's too long.


>
> Thanks again
>
> Alison
>
>
> At 04:29 PM 6/02/2012, you wrote:
>>  What Earnie described is totally the simplest and easiest way to handle this:
>>
>>  In both machines' /etc/hosts
>>
>>  127.0.0.1 localhost whatever
>>  192.168.1.1 prod server1.prod server2.prod server3
>>  192.168.1.3 dev server1.dev server2.dev server4
>>
>>  ... etc.
>>
>>
>>
>>
>>      ----- Original Message -----
>>      From: Alison<mailto:alison at ssrv.org.au>
>>      To: support at drupal.org<mailto:support at drupal.org>
>>      Sent: Sunday, February 05, 2012 10:23 PM
>>      Subject: Re: [support] Accessing multiple virtual sites on a development
>>      machine
>>
>>
>>      My old server was running Centos 5.7, which didn't support the latest
>>      Intel Express chipset very well, hence the upgrade to Centos 6.2. Have now
>>      upgraded the development machine also to Centos 6.2 as well.
>>
>>      So I have 2 machines on the same network, both running Linux and both
>>      having five virtual Apache based Drupal websites, with the development
>>      machines replicating the production one in every respect. Use static IP's
>>      for both - production on 192.168.1.1 and development on 192.168.1.3. With
>>      a Windows 7 machine at 192.168.1.2, which I use for access. What I would
>>      like to do is make changes to the development systems, and when I'm happy
>>      migrate the changes to the production machine.
>>
>>      Alison
>>
>>
>>
>>
>>      At 03:09 AM 6/02/2012, you wrote:
>>>          For Windows machines, I suggest using Acrylic DNS proxy to handle the
>>>          DNS for multiple sites. I've got info on it here:
>>>
>>>          http://drupal.org/node/32715#comment-2579138
>>>
>>>          Basically all my client sites on the devel machine get the TLD .dev
>>>          (ie: mysite.dev) . I've been doing this for a few years now and love it.
>>>
>>>
>>>
>>>          Jamie Holly
>>>
>>>              http://www.intoxination.net
>>>
>>>
>>>
>>>              http://www.hollyit.net<http://www.hollyit.net/>
>>>
>>>          On 2/5/2012 11:04 AM, L.J.Bos wrote:
>>>>              You can download MAMP / XAMPP or WAMP for free. Follow the
>>>>              instructions and you can access any (dev) site. Will take you
>>>>              about 15 minutes.
>>>>
>>>>              Regards,
>>>>
>>>>              Eljay
>>>>
>>>>              On Sun, Feb 5, 2012 at 2:46 AM, Earnie Boyd<
>>>>              earnie at users.sourceforge.net
>>>>              <mailto:earnie at users.sourceforge.net>>  wrote:
>>>>
>>>>                  On Sat, Feb 4, 2012 at 5:26 PM, Alison<alison at ssrv.org.au
>>>>                  <mailto:alison at ssrv.org.au>>  wrote:
>>>>                  >  Hi, having spent the last few days building a new Centos
>>>>                  6.2 (RHEL 6) webserver and migrating 5 low-traffic Drupal
>>>>                  virtual sites to it - successfully, now looking to use the
>>>>                  old server as a development machine. Brain is a bit worn out
>>>>                  so this may seem a silly question, but how can I access the
>>>>                  development machine sites? Localhost just gives me the first
>>>>                  Apache default listed site, and using the domain names takes
>>>>                  me to the new server. Tried listening on a different port,
>>>>                  didn't help, nor did using 127.0.0.1 - loopback. Must be an
>>>>                  easier way than setting up a local DNS server and changing
>>>>                  development machine domain names.
>>>>                  >
>>>>                  >  Suggestions please.
>>>>                  >
>>>>                  Add your dev sites to the /etc/hosts file.
>>>>                  127.0.0.1 dev.site1.com<http://dev.site1.com>
>>>>                  127.0.0.1 dev.site2.com<http://dev.site2.com>
>>>>                  etc.
>>>>                  How are you accessing the dev sites? I mean are you using a
>>>>                  browser
>>>>                  housed on the same host as the server or are you accessing
>>>>                  from a
>>>>                  different client? You'll need to add the same entries in the
>>>>                  client
>>>>                  hosts file, if that is a windows PC it will be something like
>>>>                  c:\windows\system32\drivers\etc\hosts.
>>>>                  --
>>>>                  Earnie
>>>>                  -- https://sites.google.com/site/earnieboyd
>>>>                  --
>>>>                  [ Drupal support list | http://lists.drupal.org/ ]
>>>>
>>>>
>>>>
>>>>
>>>>              --
>>>>              Eljay Bos
>>>>              Mobile Italy:+39 3392403630
>>>>              Mobile Kenya: +254 0706758499
>>>>
>>>>
>>>          --
>>>          [ Drupal support list | http://lists.drupal.org/ ]
>>
>>      --------------------------------------------------------------------------------
>>      --
>>      [ Drupal support list | http://lists.drupal.org/ ]
>>
>>  --
>>  [ Drupal support list | http://lists.drupal.org/ ]
>