{=
  include("docs.util");
  start_docs_page(docs.technical_manual.page_titles.sdinfo);
=}

The most difficult part of the CGI-mode $PRODUCT_NAME installation
is choosing the correct
Temporary {=capitalize(lang_stats.directory)=} and Temporary {=capitalize(lang_stats.directory)=} URL.
When you run $PRODUCT_NAME in web server mode (with $PRODUCT_NAME running its own internal web server,
and serving its pages via HTTP), this step is not necessary, which is one of the
advantages of web server mode.
However, if you prefer to run $PRODUCT_NAME in
CGI mode, you will have to choose the Temporary {=capitalize(lang_stats.directory)=} and URL.<p>

$PRODUCT_NAME includes images as part of its output, including
pie charts, line graphs, bar charts, and icons.
To display these images, it first creates GIF image files in the Temporary {=capitalize(lang_stats.directory)=},
and then embeds the URLs of those images in the HTML of the pages it generates,
using the Temporary {=capitalize(lang_stats.directory)=} URL as the basis for choosing the correct URL.<p>

The Temporary {=capitalize(lang_stats.directory)=} and the Temporary {=capitalize(lang_stats.directory)=} URL are two different ways
of describing the <i>same</i> $(lang_stats.directory).  They must point to the same
$lang_stats.directory for $PRODUCT_NAME's output to look correct.  The temporary $lang_stats.directory:
<ul> 

  <li> must be within the HTML pages $lang_stats.directory of the web server which is
       serving $(PRODUCT_NAME).  Web servers serve all their pages from a particular
       $lang_stats.directory on the hard drive; the Temporary {=capitalize(lang_stats.directory)=} must be somewhere
       within this $(lang_stats.directory).  This $lang_stats.directory is called different things by
       different web servers, but some common names are %22htdocs%22, %22html%22,
       %22data%22, %22wwwroot%22, and %22Web Pages.%22  If you do not know where this
       $lang_stats.directory is for your web server, you can find out in your web server's
       documentation.  See {=docs_chapter_link('webservers')=} for a list of web servers,
       and where the HTML pages $lang_stats.directory is for them.<p>

  <li> must either exist and be writable by $PRODUCT_NAME (running as a CGI program),
       or it must be possible for $PRODUCT_NAME to create it.  UNIX users
       may need to use the <code>chmod</code> command to set permissions correctly.<p>
</ul>

The Temporary {=capitalize(lang_stats.directory)=} should be described using
your platform's standard pathname format (see {=docs_chapter_link('pathnames')=}).
The Temporary {=capitalize(lang_stats.directory)=} URL should describe the same $lang_stats.directory as
the Temporary {=capitalize(lang_stats.directory)=}, but as a URL (as it might be accessed using
a web browser, by browsing the server $PRODUCT_NAME is running under).  The
following examples illustrate how it might be set for various platforms; see
{=docs_chapter_link('webservers')=} for more specific information.<p>

As the hostname part of the URL, you will need to specify the machine
$PRODUCT_NAME is running on.  In the examples below, this is chosen to be www.mysys.com;
you will need to replace this part of the URL with your machine's actual hostname.<p>

<b>Example 1</b>: For <b>MacOS</b>,
if the root of your web server's HTML pages is at /Library/WebServer/Documents
(i.e. the Documents $lang_stats.directory, which is in the WebServer $lang_stats.directory, which is in the Library folder),
and this is accessible from your web browser
as http://www.mysys.com/, then you could enter /Library/WebServer/Documents/$PRODUCT_EXECUTABLE_DOCS/
as the Temporary {=capitalize(lang_stats.directory)=}
and http://www.mydomain.com/$PRODUCT_EXECUTABLE_DOCS/ as the Temporary {=capitalize(lang_stats.directory)=} URL.<p>

<b>Example 2</b>: For <b>Windows</b>,
if the root of your web server is at C:\inetpub\wwwroot\
(i.e. the wwwroot $lang_stats.directory, which is in the inetpub $lang_stats.directory, which is on the C drive),
and this is accessible from your web browser
as http://www.mysys.com/, then you could enter
C:\\inetpub\\wwwroot\\ $PRODUCT_EXECUTABLE_DOCS\\ as the Temporary {=capitalize(lang_stats.directory)=}
and http://www.mydomain.com/$PRODUCT_EXECUTABLE_DOCS/ as the Temporary {=capitalize(lang_stats.directory)=} URL.<p>

<b>Example 3</b>: For <b>UNIX</b>,
if the root of your web server is at /home/httpd/html/,
and this is accessible from your web browser
as http://www.mydomain.com/, then you could enter /home/httpd/html/$PRODUCT_EXECUTABLE_DOCS/
as the Temporary {=capitalize(lang_stats.directory)=}
and http://www.mysys.com/$PRODUCT_EXECUTABLE_DOCS/ as the Temporary {=capitalize(lang_stats.directory)=} URL.<p>

<p>It is also possible to use relative pathnames, which sometimes makes it easier; e.g. on UNIX if both the
cgi-bin directory and the html directory are in the same directory, you can use ../html/$PRODUCT_EXECUTABLE_DOCS
as the temporary directory, without having to specify the full pathname.</p>

See {=docs_chapter_link('webservers')=} for more information.

{= end_docs_page() =}