You Are Here: Home » Articles » Setting Up Domains for Local Projects on Windows Apache

Setting Up Domains for Local Projects on Windows Apache

Using the Apache VirtualHost directive and Windows' hosts file to establish domain names for local projects.

Tagged with Domains, Apache, WAMP, Windows and Web Development
Posted on 27/5/07 by Paul Herron

In Apache, the easiest way to set up a project is to declare its directory path as the DocumentRoot in httpd.conf:

 

  1. # DocumentRoot: The directory out of which you will serve your
  2. # documents. By default, all requests are taken from this directory, but
  3. # symbolic links and aliases may be used to point to other locations.
  4. #
  5. DocumentRoot "C:\Design\myproject"

 

That directive, after restarting Apache, would make the contents of myproject available at http://localhost/. This is fine for one project, but accessing the contents of a different project directory - say, C:\Design\myotherproject - as if it were the document root would require changing the config file and restarting Apache.

VirtualHost Saves the Day 

In httpd.conf, we can first use the NameVirtualHost directive to specify the IP to which name-based requests will resolve. As we're working locally, this should be the loopback IP address, 127.0.0.1. We then give a series of VirtualHost directives to specify the domain name and corresponding directory for each project.

  1.  NameVirtualHost 127.0.0.1

  3. <VirtualHost 127.0.0.1>
  4. DocumentRoot "C:/Design/myproject"
  5. ServerName myproject.l
  6. </VirtualHost>

  8. <VirtualHost 127.0.0.1>
  9. DocumentRoot "C:/Design/myotherproject"
  10. ServerName myotherproject.l
  11. </VirtualHost>

We now need to take care of the DNS part of this process. Requests for any of our test domains should map to 127.0.0.1, and this can be enforced in the Windows hosts file, usually available at C:\WINDOWS\system32\drivers\etc\hosts.

  1. # Copyright (c) 1993-1999 Microsoft Corp.
  2. #
  3. # This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
  4. #
  5. # This file contains the mappings of IP addresses to host names. Each
  6. # entry should be kept on an individual line. The IP address should
  7. # be placed in the first column followed by the corresponding host name.
  8. # The IP address and the host name should be separated by at least one
  9. # space.
  10. #
  11. # Additionally, comments (such as these) may be inserted on individual
  12. # lines or following the machine name denoted by a '#' symbol.
  13. #
  14. # For example:
  15. #
  16. #      102.54.94.97     rhino.acme.com          # source server
  17. #       38.25.63.10     x.acme.com              # x client host

  19. 127.0.0.1       localhost
  20. 127.0.0.1       myproject.l
  21. 127.0.0.1       myotherproject.l

All being well, this setup would make the two example projects available at http://myproject.l and http://myotherproject.l.

Apache will need a restart for the changes to take effect. It might also be necessary to restart Windows' DNS Client service, which can be found by right-clicking My Computer, selecting Manage and navigating to the Services section under Services and Applications.

Comments

pierre wrote on 1/6/07:

Thanks Paul, it now works on my local machine !!

cheers 

Leave a Comment

*
CAPTCHA
[I can't read this; give me another]
*
*

« Back to Articles

Article Tags

Show all articles, or just those tagged as:

Apache (1)
CakePHP (5)
Domains (1)
Ethics and That (1)
Freeware (1)
Open Source (1)
Servage (1)
SMS (1)
Software (1)
WAMP (1)
Web Development (6)
Windows (2)

Feed

The articles RSS feed is available here.

Elsewhom

See More…

Back to top.