From 393f13a4022de3eb44228bc75391733abec49054 Mon Sep 17 00:00:00 2001 From: "jake%bugzilla.org" <> Date: Sat, 1 Feb 2003 12:56:16 +0000 Subject: Recompiling the docs because of the large change to the installation section just checked in. --- docs/html/stepbystep.html | 199 +++++++++------------------------------------- 1 file changed, 37 insertions(+), 162 deletions(-) (limited to 'docs/html/stepbystep.html') diff --git a/docs/html/stepbystep.html b/docs/html/stepbystep.html index 27870e9ae..d925b25cb 100644 --- a/docs/html/stepbystep.html +++ b/docs/html/stepbystep.html @@ -81,17 +81,17 @@ CLASS="section" >

4.1.1. Introduction

Bugzilla has been successfully installed under Solaris, Linux, and Win32. Win32 is not yet officially supported, but many people have got it working fine. - Please see the + Please see Win32 Installation NotesSection 4.3.1 for further advice on getting Bugzilla to work on Microsoft Windows.

4.1.2. Package List

DBD::mysql - (1.2209) + (2.1010)

  • DBI - (1.13) + (1.32)

  • 4.1.5.1. DBI

    4.1.5.2. Data::Dumper

    4.1.5.3. MySQL-related modules

    4.1.5.4. TimeDate modules

    4.1.5.5. GD (optional)

    The GD library was written by Thomas Boutell a long while ago to programatically generate images in C. Since then it's become the - defacto standard for programatic image construction. The Perl bindings + defacto standard for programmatic image construction. The Perl bindings to it found in the GD library are used on millions of web pages to generate graphs on the fly. That's what Bugzilla will be using it for so you must install it if you want any of the graphing to work.

    4.1.5.6. Chart::Base (optional)

    4.1.5.7. Template Toolkit

    4.1.6. HTTP Server

    You have a freedom of choice here - Apache, Netscape or any other - server on UNIX would do. You can run the web server on a - different machine than MySQL, but need to adjust the MySQL - "bugs"You have freedom of choice here, pretty much any web server that + is capable of running CGI - user permissions accordingly. -

    Section 4.4 has more information about + configuring web servers to work with Bugzilla. +

    -

    You'll want to make sure that your web server will run - any file - with the .cgi extension as a CGI program and not simply display the source - code. If you're - using Apache that means uncommenting the following line in the httpd.conf - file: - 
    
AddHandler cgi-script .cgi
-
    -

    With Apache you'll also want to make sure that within the - httpd.conf file these lines: - 
    
Options +ExecCGI 
-AllowOverride Limit
-
    - - are in the stanza that covers the directories into which you intend to - put the bugzilla .html and .cgi files. - -

    AllowOverride Limit allows the use of a Deny statement in the - .htaccess file generated by checksetup.pl

    Users of older versions of Apache may find the above lines - in the srm.conf and access.conf files, respectively.

    -

    There are important files and directories that should not be a - served by the HTTP server - most files in the - "data" - directory and the - "localconfig" - file. You should configure your HTTP server to not serve - these files. Failure to do so will expose critical passwords and - other data. Please see - .htaccess files and security - for details on how to do this for Apache; the checksetup.pl - script should create appropriate .htaccess files for you.

    4.1.7. Bugzilla

    If you symlink the bugzilla directory into your Apache's HTML - heirarchy, you may receive + hierarchy, you may receive Forbidden

    4.1.8. Setting Up the MySQL Database

    4.1.9.

    4.1.10. Securing MySQL

    This means anyone from anywhere on the internet can not only drop +>This means anyone from anywhere on the Internet can not only drop the database with one SQL command, and they can write as root to the system.

    4.1.11. Configuring Bugzilla