I've setup internal DNS servers that just handle the local domains, and put them higher up in preference on the machines. On windows there's a little gui in the networking -> tcp/ip tab, I think you could do the same on mac/linux by editing the resolve.conf file ... been a while though since I did something like this.
On Tue, Aug 24, 2010 at 7:11 AM, Paul <z...@zooluserver.com> wrote: > > On 8/14/2010 10:40 AM, Rob Allen wrote: >> >> On 13 Aug 2010, at 17:55, Paul wrote: >> >>> On 8/13/2010 5:55 AM, Rob Allen wrote: >>>> >>>> On 11 Aug 2010, at 14:32, Paul wrote: >>>> >>>>> I thought about this, and this can be done. But it is also nice to be >>>>> able to help another developer quickly, by actually viewing the site in a >>>>> browser, especially when they are having an issue with frontend code. >>>> >>>> All my devs have their own environments on their own computers. All the >>>> webservers are available via the network, so I can quite easily go to >>>> http://dev1.local/jobnumber and see the current state of the site easily >>>> enough. We do the same when they work at home too. >>> >>> So dev1 corresponds to a one developer? So each developer's local >>> webserver(s) is available via the network. >> > How are you resolving dev1.local to each developers local machine? > >> Yes, that's right. >> >> Regards, >> >> Rob... >> > -- ----------------------------------------- Mark Steudel P: 425.298.7244 F: 206.260.3021 msteu...@gmail.com . : Work : . http://www.mindfulinteractive.com . : Play : . http://www.steudel.org/blog
