I have used Apache for serving websites on our servers for several years now, with a single public IP address.
To achieve this, I have always modified the HTTPD-VHOSTS.CONF file similar to below:-
For Domain 1:-
For Domain 2:-
The DNS for each domain was set to the single public IP address.
Then whenever you typed www.domain1.com it would serve the files in d:\htdocs\domain1 and if you typed www.domain2.com it would serve the files in d:\htdocs\domain2 etc.
I have now setup AMPPS and added the domains but it appears that the only way to get the files served would be to type:-
When I open the HTTPD-VHOSTS.CONF file it shows what I would expect:-
Options FollowSymLinks Indexes
allow from All
ScriptAlias /cgi-bin/ "d:/ampps/www/domain1/cgi-bin/"
CustomLog "D:/Ampps/apache/logs/www.domain1.com.log" combined
But if I type www.domain1.com I get the files in the root of www and NOT the files in the folder domain1.
The current version of Ampps hosts domains exactly as programmed.
I am able to host domains perfectly just using the control panel forms (click the Add Domain button and follow the prompts).
This posting thread is actually confusing because whatever problem the Original Poster was experiencing has been resolved now.
The key piece of information in this thread which is quite valid is this:
Note: Don't do anything manually in httpd-vhosts.conf file as AMPPS would change it according to domains added by ampps.
Of course, you must first have your domain name directed at your registrar to a nameserver, which you set up to so internet requests for that domain go to the ip address for your web server (I use zoneedit,com for my nameserver service)
Also, your website files (docs) must be placed in the directory for your domain name which was auto-created by Ampps inside the www directory.
The solution: I followed exactly the recommendations in the posting from Tidus above (creating a new custom extra conf file for the "extra" directory and then in httpd.conf, adding the new while commenting out the standard one). Evidently, the custom extra file is respected while the conventional extra file as supplied isn't. So I now have my domain name going directly to its "doc" directory and the website showing properly.