To create a new website:
1. In the Websites Tab, click button: Create New Website.
2. Enter into the “Primary Domain Name” field the domain-name you would like to use:
In the “Domain Aliases” field enter any other domain aliases for your website:
example.com, www.example.org, example.org, www.example.net, example.net
It is perfectly okay to use an un-registered, fake, or an already taken (registered) domain-name. The LocalDNS feature of Wamp-Developer Pro will enable this domain-name to work (…to resolve to the local IP 127.0.0.1) immediately in the Browser of your local system.
You may also add an IP address into the Domain Aliases field to be able to access this website directly via an IP address URL (such as http://127.0.0.1/). You can locate your system’s local LAN IP, public IP, and also the system’s host-name (LAN’s “domain-name” for your system) in Wamp-Developer’s System Tab.
Unless you de-select “Forward to Primary Domain: All Aliases”, all domain aliases requests that reach this website will be re-directed automatically to the Primary Domain Name in the user’s Browser.
Unless you de-select “Forward to Primary Domain: SSL”, all HTTPS (SSL) requests that reach this website will be re-directed automatically to the HTTP (non-SSL) URL in the user’s Browser.
3. Click Continue.
A few seconds later, your Website should show up in the Websites list, and its State should be listed as: Added.
Selecting the new website in the list and clicking the DocumentRoot button will open this website’s folder (the DocumentRoot folder). File index.php (or index.html) is the file displayed by default when going to the website’s URL (address).
Double-clicking the website entry or clicking the Website button will open this website in your default Browser.
Folder C:\WampDeveloper\Websites\domain.name\certs\ holds the website’s SSL Private Key (private.key) and Public Certificate (public.crt) files. The initial files placed here (when adding a website) are self-signed placeholder files that will result in Browser warnings. These placeholders will eventually need to be replaced with a legitimate key and certificate file.