- 1 VMware Takes the Wraps Off vRealize Automation and vRealize Business
- 2 Microsoft Previews Hyper-V Containers for Windows Server 2016
- 3 Mirantis Led FUEL Project Gets Installed Under OpenStack Big Tent
- 4 Red Hat Enterprise Linux 7.2 Adds Security, DR Features
- 5 Docker Reaches Across Universes at Dockercon EU
Getting Started with Apache 1.3
Copyright 2000 by Ken Coar. All rights reserved. Limited rights granted to Internet.Com.
Hopefully you know something about Web servers in general, and the Apache Web server in particular, or else you wouldn't be reading this page. This article isn't intended to give background on what Apache is nor why you should use it, but how to get going with it once the decision has been made. In other words, simply how to download it, and install it, and turn it on.
I should make it very clear right away that this article is about
the latest released version of the server, Apache 1.3.
It is not about the still-under-development 2.0 version. You'll have to
wait for another article for that.
The setting up of an Apache Web server falls naturally into a number of steps. Unfortunately, the steps differ slightly depending upon whether you're going to be using a binary distribution or if you're using Windows; the steps that may not apply are marked as 'optional' below.
- Download the software
- [optional] Build the software (unless you downloaded a binary distribution)
- Stop any currently-running Apache server
- [optional] De-install any existing Apache package (Windows only)
- Install the new Apache software
- Make sure the configuration is correct
- Start the Web server
- Customise your content
Before getting into the nitty-gritty, let's set up a little background. A lot of what follows is going to refer to files and directories and commands and locations and things like that, so let us be sure we both understand them to mean the same things.
An Apache server has at least two important directory trees, and possibly three. The first is where the server software lives (called the ServerRoot), the second is where the documents that get served to network visitors live (called the DocumentRoot), and the third is the home of the software sources (called the source tree). In many cases these all live in close proximity; if you install Apache from a package, the DocumentRoot might actually be a subdirectory under the ServerRoot, for instance.
For the sake of clarity, the rest of this article makes the following assaumptions about where things are on your system:
|Directory tree||Unix location||Windows location|