From 4235e044d2137854fe6679112181b2140d006ec6 Mon Sep 17 00:00:00 2001 From: Rich Bowen Date: Fri, 20 Apr 2012 00:54:51 +0000 Subject: [PATCH] Here's a little more of it. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1328161 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/getting-started.xml | 81 +++++++++++++++++++++++++++++++++ 1 file changed, 81 insertions(+) diff --git a/docs/manual/getting-started.xml b/docs/manual/getting-started.xml index da26e564a0..ff2671aa1d 100644 --- a/docs/manual/getting-started.xml +++ b/docs/manual/getting-started.xml @@ -75,6 +75,11 @@ the servername to an IP address - the location on the Internet where the server resides. Thus, in order for your web server to be reachable, it is necessary that the servername be in DNS.

+

More than one hostname may point to the same IP address, and more +than one IP address can be attached to the same physical server. Thus, you +can run more than one web site on the same physical server, using a +feature called virtual hosts.

+

If you don't know how to do this, you'll need to contact your network administrator, or Internet service provider, to perform this step for you.

@@ -100,10 +105,86 @@ href="http://en.wikipedia.org/wiki/Domain_Name_System">Wikipedia.org/wiki/Domain
Configuration Files and Directives + +

The Apache HTTP Server is configured via simple text files. +These files may be located any of a variety of places, depending on how +exactly you installed the server. Common locations for these files may +be found in +the httpd wiki. If you installed httpd from source, the default +location of the configuration files is +/usr/local/apache2/conf. The default configuration file is +usually called httpd.conf. This, too, can vary in +third-party distributions of the server.

+ +

The configuration is frequently broken into multiple smaller files, +for ease of management. These files are loaded via the Include directive. The names or locations of +these sub-files are not magical, and may vary greatly from one +installation to another. Arrange and subdivide these files as +makes the most sense to you. If the file arrangement +you have by default doesn't make sense to you, feel free to rerrange it.

+ +

The server is configured by placing configuration directives in these +configuration files. A directive is a keyword followed by one or more +arguments that set its value.

+ +

The question of "Where should I put that +directive?" is generally answered by considering where you want a +directive to be effective. If it is a global setting, it should appear +in the configuration file, outside of any Directory, Location, VirtualHost, or other section. If it is to +apply only to a particular directory, then it should go inside a +Directory section referring to +that directory, and so on. See the Configuration +Sections document for further discussion of these sections.

+ +

In addition to the main configuration files, certain directives may go in +.htaccess files located in the content directories. +.htaccess files are primarily for people who do not have +access to the main server configuration file(s). You can read more about +.htaccess files in the .htaccess howto.

+
Web Site Content + +

Web site content can take many different forms, but may be broadly +divided into static and dynamic content.

+ +

Static content is things like HTML files, image files, CSS files, +and other files that reside in the filesystem. The DocumentRoot directive specifies where in your +filesystem you should place these files. This directive is either set +globally, or per virual host. Look in your configuration file(s) to +determine how this is set for your server.

+ +

Typically, a document called index.html will be served +when a directory is requested without a file name being specified. For +example, if DocumentRoot is set to +/var/www/html and a request is made for +http://www.example.com/work/, the file +/var/www/html/work/index.html will be served to the +client.

+ +

Dynamic content is anything that is generated at request +time, and may change from one request to another. There are numerous +ways that dynamic content may be generated. Various handlers are available to generate content. CGI programs may be written to generate +content for your site.

+ +

Third-party modules like mod_php may be used to write code that does a +variety of things. Many third-party applications, written using a +variety of languages and tools, are available for download and +installation on your Apache HTTP Server. Support of these third-party +things is beyond the scope of this documentation, and you should find +their documentation or other support forums to answer your questions +about them.

-- 2.40.0