ebackhus, pay for my flight, hotel and my time, and I'll teach you. :grin: :wink:
However, since you're doing directly by IP, it's not as simple. You can do something like "1.2.3.4/~username", but that's kind of ugly. Otherwise, you'll need to point 3 domains to your server if you want to do the VirtualHost method I describe below.
warlocke, the reason I mentioned port 80 is because I assumed the domain you listed was where the site was located on your computer. Sorry for misunderstanding.
Here's an example VirtualHost:
Code:
<VirtualHost 1.2.3.4>
ServerAlias example.com
ServerAdmin [email protected]
DocumentRoot /home/username/public_html
BytesLog domlogs/example.com-bytes_log
ServerName www.example.com
User username
Group groupname
CustomLog /usr/local/apache/domlogs/example.com combined
ScriptAlias /cgi-bin/ /home/username/public_html/cgi-bin/
</VirtualHost>
For each domain that you wish to host, you'll need the above block of config lines. The first line where the 1.2.3.4 is located, that's your IP address. It can be the same for each block of lines. Everywhere that I have "example.com", put the domain name that you're defining. The DocumentRoot line is where you specify where the HTML/PHP files are located for that domain name. Please use the proper path for your environment.
The User and Group lines are the username and group for the user that will own these files. In my envorionment, since each user account has its own public_html within their home directory, I use that users username/group so that no 2 users have access to each others files. Obviously, there are other security issues to consider, but this is just one of the basic ideas to implement if this is a concern. If you're the only user, then this isn't as big of an issue.
Set the CustomLog and BytesLog paths as appropriate for your environment if you wish to have log files that you can run through Awstats or Webalizer. The ScriptAlias line defines where the cgi-bin will be located so that any CGI scripts will be treated as such. This will also benefit from the User/Group lines.
Keep in mind that every invironment is slightly different, so edit the above lines as appropriate for yours. Just copy/pasting those lines won't work otherwise. You can have as many VirtualHost blocks as needed. I've had several hundred without issues. If you have multiple IP's to use, you can define an IP for each VirtualHost. Also, for different ports, you can use the following: <VirtualHost 1.2.3.4:8080>
Since you already have a site up and running, locate the existing VirtualHost and copy that block and modify it as needed.