Davide Bianchi wrote:
> On 2004-11-02, Matthias Pospiech <matthiasPUNKTpospiech@gmx.de> wrote:
>
>>What is necessary to do that ?
>
>
> Read the documentation related to Virtual Hosts.
> Davide
>
The original poster said "This webs shall only be accesible from my own
machine". Does that fit in well with virtual hosts?

I run name-based virtual hosts on an apache server, and it works fine
for others on the internet. But when I want to view the sites myself on
a *test server* (unconnected to the internet), I can't get to any
particular domain, without a lot of messing about.


I have 3 computers

localhost - A fastish machine where I want to look at the files
webserver - actually on the internet, using virtual hosts.
webserver2 - configured like 'webserver', but only for test purposes.

The only thing I do is edit httpd.conf on 'webserver2' and put whatever
domain I want to see as the first virtual host. Then going to
http://local-machines-ip will bring up that domain, since apache
defaults to showing the first domain if there is no match on the name.
If I want to look at another domain, I have to edit httpd.conf again and
restart apache. There must be a way around this, but I have never found it.

Since my test server is not on the local host, I can't actually go to
the top level directory and just look at the files.

BTW, the original poster said he wanted 3 independant servers. I'm not
sure if he meant 3 physical computers, or 3 copies of the apache server
running. But neither are probably necessary. Certainoly once he gets
them on the internet there is no need for more than one computer or one
copy of apache running. But when they are local, I am almost as confused
as the original poster.