<quote who="Michael Lake">
> I am quite lost on Virtual Domains, the apache docs do assume you know
> what virtual domains are and are quite familiar with them.
Looks like you're worried about things outside of Apache, which you don't
need to be. :)
It's only Apache that gives a tinker's cuss about this stuff - you're not
going to muss up anything outside your box. With name-based virtual domains,
Apache looks to the host header in the request and decides what to send
back.
NameVirtualHost <IP> tells Apache that you have multiple named virtual
servers sitting on the IP address, so it should look at the host header.
<VirtualHost <IP>> tells Apache, "I'm a virtual server hanging off this IP
address".
ServerName <blah.domain> and ServerAlias <blah.domain> tell Apache the
domains that this block refers to. ServerAlias is good for including the
www, because as we all know, sites that don't work without their www are
crap. ;)
In your /etc/hosts file you should add some names to resolve to your local
IP address. My devel machine just has a bunch of project hostnames resolving
to its IP:
project1 10.0.0.64
project2 10.0.0.64
When I go to http://project1/ in Mozilla, Apache first looks at it and says
"request for 10.0.0.64!" then, "that's a nameserver!" and finally, "it's
requesting the project1 host!"
BindAddress 10.0.0.64
NameVirtualHost 10.0.0.64
<VirtualHost 10.0.0.64>
ServerName project1
ServerAlias www.project1
DocumentRoot /home/jdub/web/project1/root
</VirtualHost>
And so on. :) You can do lots of funky things with different ports and IP
addresses too.
- Jeff
-- [EMAIL PROTECTED] --------------------------------- http://linux.conf.au/ --
ASCII stupid question, get a stupid ANSI.
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug
