Bugzilla:Win32Install: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
mNo edit summary
(Redirect to new docs.)
 
(34 intermediate revisions by 12 users not shown)
Line 1: Line 1:
==Installing Bugzilla on Microsoft Windows==
See http://bugzilla.readthedocs.org/en/latest/installing/windows.html .
 
<b>Original author: [http://bugzilla.glob.com.au/ Byron Jones]</b>
 
Bugzilla version 2.18 was the first release that runs unmodified on Windows. The current stable version of Bugzilla is 2.20. This document guides you step by step through the installation process.
 
Note that there are a few things that don't work on Windows. The most important one of these would be the inbound email interface ([http://lxr.mozilla.org/mozilla/source/webtools/bugzilla/contrib/README.Mailif contrib/README.Mailif]).
 
===Bugzilla===
 
There's two main methods to getting the Bugzilla source - from CVS or in a tarball.  The best method for fetching Bugzilla is to grab it directly from CVS, as this will allow for simple upgrades, even if you have customised Bugzilla.
 
Read the [http://bugzilla.org/releases/2.20/release-notes.html Release Notes] before you do anything.
 
====Installing Bugzilla From CVS====
 
Download the CVSNT client from [http://www.cvsnt.org/] (2.15 Meg).
 
Run the installation, you'll only need to install the <b>Command line client</b> and the <b>Password Server (:pserver:) Protocol</b>.  Once the install has completed, log out and log in again to pick up the changes to the PATH.
 
Note: this document assumes you want to install Bugzilla into <b>C:\Bugzilla</b>.
 
Open the command line, and cd to the <b>parent</b> of the directory you want to install Bugzilla into.  As we'll be installing Bugzilla into <b>C:\Bugzilla</b>, the current directory must be <b>C:\</b>.
 
C:\&gt;<b>set CVSROOT=:pserver:anonymous@cvs-mirror.mozilla.org:/cvsroot</b>
C:\&gt;<b>cvs login</b>
Logging in to :pserver:anonymous@cvs-mirror.mozilla.org:2401:/cvsroot
CVS password: <b>anonymous</b>
C:\&gt;<b>cvs checkout -d Bugzilla -rBUGZILLA-2_20-STABLE Bugzilla</b>
cvs checkout: cwd=C:\ ,current=C:\
cvs checkout: Updating Bugzilla
U Bugzilla/.cvsignore
U Bugzilla/1x1.gif
U Bugzilla/Bugzilla.pm
U Bugzilla/CGI.pl
...
U Bugzilla/template/en/default/whine/multipart-mime.txt.tmpl
U Bugzilla/template/en/default/whine/schedule.html.tmpl
cvs checkout: Updating Bugzilla/template/en/extension
U Bugzilla/template/en/extension/filterexceptions.pl
cvs checkout: Updating Bugzilla/template/en/extension/hook
C:\&gt;
 
====Upgrading From CVS====
 
If you've already installed an earlier version of Bugzilla from CVS or from a TarBall, updating is easy. Even if you've made customisations, CVS is smart enough to merge. If CVS needs help merging, it displays a C in the first column of its report. You need to resolve such conflicts manually.
 
C:\Bugzilla&gt;<b>cvs update -R -d -rBUGZILLA-2_20-STABLE</b>
cvs update: Updating .
P editusers.cgi
cvs update: Updating Bugzilla
P Bugzilla/Bug.pm
P Bugzilla/BugMail.pm
P Bugzilla/Chart.pm
P Bugzilla/Flag.pm
P Bugzilla/User.pm
P Bugzilla/Util.pm
cvs update: Updating Bugzilla/Auth
U Bugzilla/Auth/CGI.pm
cvs update: Updating Bugzilla/Template
cvs update: Updating Bugzilla/Template/Plugin
...
cvs update: Updating template/en/default/search
cvs update: Updating template/en/default/whine
cvs update: Updating template/en/extension
C:\Bugzilla&gt;
 
====Installing Bugzilla From the TarBall====
 
Download the Bugzilla 2.20 from [http://bugzilla.org/download.html] (1.2 Meg).
 
Bugzilla ships as a Tarball, which has the extension .tar.gz.  Any decent Windows archive tool should be able to extract tarballs.
 
Extract the archive to the directory of your choice. For the remainder of this document I will assume that you have extracted Bugzilla into <b>C:\Bugzilla</b>.
 
====Upgrading From TarBall====
 
If you installed Bugzilla from the TarBall, the simplest way to upgrade is to follow the <b>CVS Upgrading</b> instructions.
 
===MySQL===
 
====Download MySQL 4.1.x====
 
Download the MySQL "Windows Essentials" installer from [http://dev.mysql.com/downloads/mysql/4.1.html#Windows http://dev.mysql.com/downloads/mysql/4.1.html] (14.1 Meg).
 
MySQL 5.x is still under development and is <b>not</b> recommended.
 
====Install====
 
MySQL has a standard Windows installer.  It's ok to select a Typical MySQL install (the default).  For the remainder of this document I will assume you have installed MySQL into <b>C:\mysql</b>.
 
====Create Bugs Database and User====
 
Use the <b>mysql</b> command line utility to create the Bugzilla database and a MySQL account for Bugzilla.
 
Note in the following example 'sockmonkey' is my password for the bugs account:
 
C:\mysql\bin&gt;<b>mysql --user=root -p mysql</b>
Enter password: <b>********</b>
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 15 to server version: 4.0.20a-debug
Type 'help;' or '\h' for help. Type '\c' to clear the buffer.
mysql&gt; <b>create database bugs;</b>
Query OK, 1 row affected (0.11 sec)
mysql&gt; <b>grant all privileges on bugs.* to 'bugs'@'localhost' identified by 'sockmonkey';</b>
Query OK, 0 rows affected (0.03 sec)
mysql&gt; <b>flush privileges;</b>
Query OK, 0 rows affected (0.00 sec)
mysql&gt; <b>quit</b>
Bye
C:\mysql\bin&gt;
 
If you are running MySQL 4.1, you may encounter the <b>Client does not support authentication protocol requested by server</b> error message.  To fix this, once the user has been created you will have to reset the password using OLD_PASSWORD:
 
C:\mysql\bin&gt;<b>mysql --user=root -p mysql</b>
Enter password: <b>********</b>
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 15 to server version: 4.1.11-nt
Type 'help;' or '\h' for help. Type '\c' to clear the buffer.
mysql&gt; <b>set password for 'bugs'@'localhost' = OLD_PASSWORD('sockmonkey');</b>
Query OK, 0 rows affected (0.00 sec)
mysql&gt; <b>quit</b>
Bye
C:\mysql\bin&gt;
 
===ActiveState Perl===
 
====Download ActiveState Perl 5.8.1 or Higher====
 
Download the ActiveState Perl 5.8.1 or Higher MSI from: http://activestate.com/Products/Download/Download.plex?id=ActivePerl (12.5 Meg).
 
Note that Bugzilla requires ActiveState Perl 5.8.1 as it needs CGI.pm version 2.93 or higher.  5.8.0 ships with CGI.pm version 2.81, 5.8.1 ships with CGI.pm version 3.00.
 
There is [https://bugzilla.mozilla.org/show_bug.cgi?id=281920 a bug in Time::Local 1.10], which is shipped with ActiveState Perl 5.8.6, that will cause warnings to be generated at the top of every buglist.  It's a good idea to avoid version 5.8.6 (version 5.8.4 works without issue).
 
====Install====
 
ActiveState Perl uses a standard Windows Installer.  Install, sticking with the defaults, which will install Perl into <b>C:\Perl</b>.
 
Note:  Installing Perl into a directory that contains a space (eg "C:\Program Files") will break the Template-Toolkit installer.
 
Once the install has completed, log out and log in again to pick up the changes to the PATH.
 
====Upgrading Existing Installs====
 
If you already have ActiveState Perl installed, now's a good time to ensure you're running the latest version of ActiveState Perl, along with the latest versions of the modules.
 
To upgrade ActiveState Perl, follow the directions at: [http://aspn.activestate.com/ASPN/docs/ActivePerl/install.html#upgrade_56 http://aspn.activestate.com/ASPN/docs/ActivePerl/install.html]
 
To upgrade your modules, simply run <b>ppm upgrade</b>
 
====Create Temp Directory====
 
On Windows, Perl has a hard time of locating the correct directory to write its temporary files (CGI.pm, File::Spec).  Basically it has a list of paths hard coded to use, instead of querying Windows for the correct path.
 
To avoid problems, create the <b>C:\Temp</b> directory (it has to be on drive C) and ensure SYSTEM has write and modify access.
 
====Install Modules====
 
Bugzilla requires a number of perl modules to be installed. They are either available in the ActiveState repository, or at <b>http://theoryx5.uwinnipeg.ca/ppms/</b> (Perl 5.8.x) or <b>http://cpan.uwinnipeg.ca/PPMPackages/10xx/</b> (Perl 5.10.x).
 
If you use a proxy server or a firewall you may have trouble running PPM.  This is covered in the [http://aspn.activestate.com/ASPN/docs/ActivePerl/faq/ActivePerl-faq2.html#ppm_and_proxies ActivePerl FAQ].
 
The <b>Net::LDAP</b> module is only required if you want to [http://www.bugzilla.org/docs/tip/html/extraconfig.html#bzldap use Active Directory for authentication].
 
C:\&gt;<b>ppm</b>
PPM - Programmer's Package Manager version 3.1.
Copyright (c) 2001 ActiveState Corp. All Rights Reserved.
ActiveState is a devision of Sophos.
Entering interactive shell. Using Term::ReadLine::Stub as readline library.
Type 'help' to get started.
ppm&gt; <b>rep add Bugzilla http://...uwinnipeg.ca/...</b>
Repositories:
[1] ActiveState PPM2 Repository
[2] ActiveState Package Repository
[3] Bugzilla
ppm&gt; <b>install AppConfig</b>
====================
Install 'AppConfig' version 1.52 in ActivePerl 5.8.7.813.
====================
Downloaded 50508 bytes.
...
Successfully installed AppConfig version 1.52 in ActivePerl 5.8.7.813.
ppm&gt; <b>install TimeDate</b>
====================
Install 'TimeDate' version 1.16 in ActivePerl 5.8.7.813.
====================
Downloaded 19235 bytes.
...
Successfully installed TimeDate version 1.16 in ActivePerl 5.8.7.813.
ppm&gt; <b>install DBI</b>
====================
Install 'DBI' version 1.43 in ActivePerl 5.8.7.813.
====================
Downloaded 508164 bytes.
...
Successfully installed DBI version 1.43 in ActivePerl 5.8.7.813.
ppm&gt; <b>install DBD-mysql</b>
====================
Install 'DBD-mysql' version 2.9002 in ActivePerl 5.8.7.813.
====================
Downloaded 178803 bytes.
...
Successfully installed DBD-mysql version 2.9002 in ActivePerl 5.8.7.813.
ppm&gt; <b>install Template-Toolkit</b>
====================
Install 'Template-Toolkit' version 2.13 in ActivePerl 5.8.7.813.
====================
Downloaded 530770 bytes.
...
Successfully installed Template-Toolkit version 2.13 in ActivePerl 5.8.7.813.
ppm&gt; <b>install MailTools</b>
====================
Install 'MailTools' version 1.67 in ActivePerl 5.8.7.813.
====================
Downloaded 46881 bytes.
...
Successfully installed MailTools version 1.67 in ActivePerl 5.8.7.813.
ppm&gt; <b>install GD</b>
====================
Install 'GD' version 2.07 in ActivePerl 5.8.7.813.
====================
Downloaded 363039 bytes.
...
Successfully installed GD version 2.07 in ActivePerl 5.8.7.813.
ppm&gt; <b>install Chart</b>
====================
Install 'Chart' version 2.3 in ActivePerl 5.8.7.813.
====================
Downloaded 58641 bytes.
...
Successfully installed Chart version 2.3 in ActivePerl 5.8.7.813.
ppm&gt; <b>install GDGraph</b>
====================
Install 'GDTextUtil' version 0.86 in ActivePerl 5.8.7.813.
====================
Downloaded 19178 bytes.
...
Successfully installed GDTextUtil version 0.86 in ActivePerl 5.8.7.813.
====================
Install 'GDGraph' version 1.43 in ActivePerl 5.8.7.813.
====================
Downloaded 71764 bytes.
...
Successfully installed GDGraph version 1.43 in ActivePerl 5.8.7.813.
ppm&gt; <b>install PatchReader</b>
====================
Install 'PatchReader' version 0.9.4 in ActivePerl 5.8.7.813.
====================
Downloaded 9558 bytes.
...
Successfully installed PatchReader version 0.9.4 in ActivePerl 5.8.7.813.
ppm&gt; <b>install Net::LDAP</b>
====================
Install 'Convert-ASN1' version 0.19 in ActivePerl 5.8.7.813.
====================
Downloaded 26326 bytes.
...
Successfully installed Convert-ASN1 version 0.19 in ActivePerl 5.8.7.813.
====================
Install 'perl-ldap' version 0.33 in ActivePerl 5.8.7.813.
====================
Downloaded 188548 bytes.
...
Successfully installed perl-ldap version 0.33 in ActivePerl 5.8.7.813.
====================
Install 'Net-LDAP-Express' version 0.11 in ActivePerl 5.8.7.813.
====================
Downloaded 7693 bytes.
...
Successfully installed Net-LDAP-Express version 0.11 in ActivePerl 5.8.7.813.
ppm&gt;
 
===Apache===
 
It is recommended that you run Bugzilla with the Apache web server.  If you want to use IIS to run Bugzilla, there are [http://www.bugzilla.org/docs/2.20/html/configuration.html#http-iis configuration instructions] in the Bugzilla documentation.
 
====Download Apache 2.x====
 
Download the Apache HTTP Server version 2.x or high from: http://httpd.apache.org/download.cgi (5.8 Meg).
 
====Install====
 
Yet another standard Windows Installer.  Just follow the prompts, making sure you Install for All Users.  Be aware the Apache will always install itself into an <b>Apache2</b> directory under what ever path you specify.  The default install path will be displayed as <b>C:\Program Files\Apache Group</b> which will result in Apache being installed to <b>C:\Program Files\Apache Group\Apache2</b>.  This gets me every time.
 
For the remainder of this document I will assume you installed Apache into the default location, <b>C:\Program Files\Apache Group\Apache2</b>.
 
If you are already running IIS, you must configure apache to run on a port other than 80, however you aren't asked the port to listen on at install time.  Choose <b>All Users</b> (which says port 80), and we'll change the port later.
 
By default Apache installs itself to run as the SYSTEM account.  For security reasons it's better the reconfigure the service to run as an Apache user.  Create a user that is a member of <b>no</b> groups, and reconfigure the Apache2 service to run as that account.
 
====Grant write access for Apache account====
 
By default Apache will run as the SYSTEM account.  This account needs write and modify access to the following directorys, and all their subdirectories.  Depending on your version of Windows, this access may already be granted.
 
*C:\Bugzilla\data
*C:\Program Files\Apache Group\Apache2\logs
*C:\Temp
 
Note that <b>C:\Bugzilla\data</b> is created the first time you run <b>checksetup.pl</b>.
 
====Configure Port and DocumentRoot====
 
Edit <b>C:\Program Files\Apache Group\Apache2\conf\httpd.conf</b> with your [http://www.vim.org/ favourite text editor].
 
To change the port that Apache runs on (listens on, or binds to), edit the <b>Listen</b> option.
 
#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the &lt;VirtualHost&gt;
# directive.
#
# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses (0.0.0.0)
#
#Listen 12.34.56.78:80
<b>Listen 80</b>
Change the <b>DocumentRoot</b> setting to point to <b>C:\Bugzilla</b>.  Note there are two locations in <b>httpd.conf</b> that need to be updated.  Note you need to use / instead of \ as a path separator.
 
#
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
#
<b>DocumentRoot "C:/Bugzilla"</b>
#
# Each directory to which Apache has access can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories).
#
# First, we configure the "default" to be a very restrictive set of
# features. 
#
&lt;Directory /&gt;
    Options FollowSymLinks
    AllowOverride None
&lt;/Directory&gt;
#
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
#
#
# This should be changed to whatever you set DocumentRoot to.
#
<b>&lt;Directory "C:/Bugzilla"&gt;</b>
 
====Configure CGI====
 
To enable CGI support in Apache, you need to enable the CGI handler, by uncommenting the <b>AddHandler cgi-script .cgi</b> line.
 
#
# AddHandler allows you to map certain file extensions to "handlers":
# actions unrelated to filetype. These can be either built into the server
# or added with the Action directive (see below)
#
# To use CGI scripts outside of ScriptAliased directories:
# (You will also need to add "ExecCGI" to the "Options" directive.)
#
<b>AddHandler cgi-script .cgi</b>
 
And allow .cgi scripts in the Bugzilla directory by adding the <b>ExecCGI</b> option.  We also need to allow Bugzilla's .htaccess file to restrict access to sensitive documents by allowing it to override the defaults.  This involves changing <b>AllowOverride None</b> to <b>AllowOverride All</b>.
 
Apache also needs to know to use Perl to execute .cgi files, via the <b>ScriptInterpreterSource</b> directive.
 
#
# This should be changed to whatever you set DocumentRoot to.
#
&lt;Directory "C:/Bugzilla"&gt;
#
# Possible values for the Options directive are "None", "All",
# or any combination of:
#  Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
#
# Note that "MultiViews" must be named *explicitly* --- "Options All"
# doesn't give it to you.
#
# The Options directive is both complicated and important.  Please see
# http://httpd.apache.org/docs-2.0/mod/core.html#options
# for more information.
#
<b>    Options Indexes FollowSymLinks ExecCGI</b>
#
# AllowOverride controls what directives may be placed in .htaccess files.
# It can be "All", "None", or any combination of the keywords:
#  Options FileInfo AuthConfig Limit
#
<b>    AllowOverride All</b>
#
# Controls who can get stuff from this server.
#
    Order allow,deny
    Allow from all
<b>#
# Tell Apache to use Perl to execute .cgi
#
    ScriptInterpreterSource Registry-Strict</b>
&lt;/Directory&gt;
 
You also should add <b>index.cgi</b> to the <b>DirectoryIndex</b> list.
 
#
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
#
# The index.html.var file (a type-map) is used to deliver content-
# negotiated documents.  The MultiViews Option can be used for the
# same purpose, but it is much slower.
#
<b>DirectoryIndex index.html index.html.var index.cgi</b>
 
In order for <b>ScriptInterpreterSource Registry-Strict</b> to work, you also need to add an entry to the Registry so Apache will use Perl to execute .cgi files.
 
Create a key <b>HKEY_CLASSES_ROOT\.cgi\Shell\ExecCGI\Command</b> with the default value of the full path of perl.exe with a -T parameter.  For example <b>C:\Perl\bin\perl.exe -T</b>
 
[[Image:Bugzilla-Regedit.png|100px|Regedit]]
 
====Disable Logging====
 
Unless you want to keep statistics on how many hits your Bugzilla install is getting, it's a good idea to disable logging by commenting out the <b>CustomLog</b> directive.
 
#
# The location and format of the access logfile (Common Logfile Format).
# If you do not define any access logfiles within a &lt;VirtualHost&gt;
# container, they will be logged here.  Contrariwise, if you *do*
# define per-&lt;VirtualHost&gt; access logfiles, transactions will be
# logged therein and *not* in this file.
#
<b>#CustomLog logs/access.log common</b>
 
====Restart Apache====
 
Finally, restart Apache to get it pick up the changes.
 
C:\&gt;<b>net stop apache2</b>
The Apache2 service is stopping..
The Apache2 service was stopped successfully.
C:\&gt;<b>net start apache2</b>
The Apache2 service is starting.
The Apache2 service was started successfully.
C:\&gt;
 
===Extras===
 
While Bugzilla 2.20 has built in support for SMTP servers, it doesn't (yet) support SMTP authentication or debugging of SMTP errors.
 
If you require SMTP authentiation (including POP before SMTP), you can use [http://www.glob.com.au/sendmail/ Glob's sendmail wrapper].  Download and install as per the instructions on that site.
 
If you enable logging in Sendmail, you need to ensure that your Apache account has write access to <b>C:\usr\lib</b>.
 
===Configure Bugzilla===
 
====checksetup.pl====
 
Run <b>checksetup.pl</b>.  This will check your Perl modules and create <b>localconfig</b>.
 
C:\&gt;<b>cd bugzilla</b>
C:\bugzilla&gt;<b>perl checksetup.pl</b>
Checking perl modules ...
Checking for      AppConfig (v1.52)  ok: found v1.55
Checking for            CGI (v2.93)  ok: found v3.10
Checking for    Data::Dumper (any)    ok: found v2.121_04
Checking for    Date::Format (v2.21)  ok: found v2.22
Checking for            DBI (v1.38)  ok: found v1.48
Checking for      File::Spec (v0.84)  ok: found v3.05
Checking for      File::Temp (any)    ok: found v0.16
Checking for        Template (v2.08)  ok: found v2.13
Checking for      Text::Wrap (v2001.0131) ok: found v2001.09293
Checking for    Mail::Mailer (v1.65)  ok: found v1.67
Checking for        Storable (any)    ok: found v2.13
The following Perl modules are optional:
Checking for              GD (v1.20)  ok: found v2.16
Checking for    Chart::Base (v1.0)    ok: found v2.3
Checking for    XML::Parser (any)    ok: found v2.34
Checking for      GD::Graph (any)    ok: found v1.43
Checking for GD::Text::Align (any)    ok: found v1.18
Checking for    PatchReader (v0.9.4)  ok: found v0.9.5
Most ActivePerl modules are available at Apache's ppm repository.
A list of mirrors is available at
    http://www.apache.org/dyn/closer.cgi/perl/win32-bin/ppms/
You can add the repository with the following command:
    ppm rep add apache http://www.apache.org/dist/perl/win32-bin/ppms/
Checking user setup ...
This version of Bugzilla contains some variables that you may want
to change and adapt to your local settings. Please edit the file
'./localconfig' and rerun checksetup.pl
The following variables are new to localconfig since you last ran
checksetup.pl:  index_html cvsbin interdiffbin diffpath create_htaccess
webservergroup db_driver db_host db_pass db_sock db_check
C:\bugzilla&gt;
 
====Edit localconfig====
 
Open <b>C:\Bugzilla\localconfig</b> in your favourite text editor to configure Bugzilla.
 
You have to tell Bugzilla how to access your database.  If you used bugs/bugs, you'll only have to set <b>db_pass</b>.
 
#
# How to access the SQL database:
#
$db_host = "localhost";        # where is the database?
$db_port = 3306;                # which port to use
$db_name = "bugs";              # name of the MySQL database
$db_user = "bugs";              # user to attach to the MySQL database
#
# Enter your database password here. It's normally advisable to specify
# a password for your bugzilla database user.
# If you use apostrophe (') or a backslash (\) in your password, you'll
# need to escape it by preceding it with a \ character. (\') or (\\)
#
<b>$db_pass = 'sockmonkey';</b>
 
====checksetup.pl====
 
Run <b>checksetup.pl</b> again.  This time it will build your database tables and initialise Bugzilla.
 
C:\bugzilla&gt;perl checksetup.pl
Checking perl modules ...
Checking for      AppConfig (v1.52)  ok: found v1.55
Checking for            CGI (v2.93)  ok: found v3.10
Checking for    Data::Dumper (any)    ok: found v2.121_04
Checking for    Date::Format (v2.21)  ok: found v2.22
Checking for            DBI (v1.38)  ok: found v1.48
Checking for      File::Spec (v0.84)  ok: found v3.05
Checking for      File::Temp (any)    ok: found v0.16
Checking for        Template (v2.08)  ok: found v2.13
Checking for      Text::Wrap (v2001.0131) ok: found v2001.09293
Checking for    Mail::Mailer (v1.65)  ok: found v1.67
Checking for        Storable (any)    ok: found v2.13
The following Perl modules are optional:
Checking for              GD (v1.20)  ok: found v2.16
Checking for    Chart::Base (v1.0)    ok: found v2.3
Checking for    XML::Parser (any)    ok: found v2.34
Checking for      GD::Graph (any)    ok: found v1.43
Checking for GD::Text::Align (any)    ok: found v1.18
Checking for    PatchReader (v0.9.4)  ok: found v0.9.5
Most ActivePerl modules are available at Apache's ppm repository.
A list of mirrors is available at
    http://www.apache.org/dyn/closer.cgi/perl/win32-bin/ppms/
You can add the repository with the following command:
    ppm rep add apache http://www.apache.org/dist/perl/win32-bin/ppms/
Checking user setup ...
Creating data directory (./data) ...
Creating graphs directory...
Creating .htaccess...
Creating Bugzilla/.htaccess...
Creating ./data/.htaccess...
Creating ./template/.htaccess...
Creating ./data/webdot/.htaccess...
Precompiling templates ...
Checking for    MySQL Server (v3.23.41) ok: found v4.0.20a-debug
Creating table user_group_map ...
Creating table series_data ...
Creating table longdescs ...
Creating table dependencies ...
Creating table components ...
Creating table keywords ...
Creating table cc ...
Creating table duplicates ...
Creating table groups ...
Creating table flagtypes ...
Creating table profiles ...
Creating table products ...
Creating table bugs_activity ...
Creating table series_categories ...
Creating table keyworddefs ...
Creating table fielddefs ...
Creating table group_control_map ...
Creating table profiles_activity ...
Creating table group_group_map ...
Creating table user_series_map ...
Creating table bugs ...
Creating table series ...
Creating table versions ...
Creating table flagexclusions ...
Creating table logincookies ...
Creating table watch ...
Creating table bug_group_map ...
Creating table votes ...
Creating table attachments ...
Creating table flags ...
Creating table milestones ...
Creating table tokens ...
Creating table flaginclusions ...
Creating table quips ...
Creating table namedqueries ...
Creating initial dummy product 'TestProduct' ...
Populating duplicates table...
Creating duplicates directory...
Migrating old chart data into database ...
Adding group tweakparams ...
Adding group editusers ...
Adding group creategroups ...
Adding group editcomponents ...
Adding group editkeywords ...
Adding group admin ...
Adding group editbugs ...
Adding group canconfirm ...
Looks like we don't have an administrator set up yet.  Either this is your
first time using Bugzilla, or your administrator's privileges might have
accidently been deleted.
Enter the e-mail address of the administrator: <b>byron@example.com</b>
You entered 'byron@example.com'.  Is this correct? [Y/n] <b>y</b>
Enter the real name of the administrator: <b>Byron Jones</b>
Enter a password for the administrator account: <b>beef</b>
Please retype the password to verify: <b>beef</b>
'byron@example.com' is now set up as an administrator account.
C:\bugzilla&gt;
 
====Parameters====
 
You should now be able to log into to Bugzilla using the account <b>checksetup.pl</b> just created.  Point your web browser to >http://localhost/, choose <b>Log in to an existing account</b>, and login.
 
In the page footer, choose <b>Parameters</b>.
 
Put in your email address as the <b>maintainer</b>.
 
maintainer:
<b>byron@example.com</b>
 
Put in the URL to Bugzilla in the <b>urlbase</b> field.  This URL will be used in emails, so don't use localhost.
 
urlbase:
<b>http://bugzilla.example.com/</b>
 
Download and install WebDot from http://www.graphviz.org/Download_windows.php.  Put the complete path to dot.exe in <b>webdotbase</b>.
 
webdotbase:
<b>C:/Program Files/ATT/Graphviz/bin/dot.exe</b>
 
===Scheduled Tasks===
 
====collectstats.pl====
 
Add a Scheduled Task to run <b>collectstats.pl</b> nightly.
 
'''Step-by-step for Windows XP:
 
#Control Panel --&gt; Scheduled Tasks --&gt; Add Scheduled Task
#Next
#Browse
#Find <b>perl.exe</b> (normally <b>C:\Perl\bin\perl.exe</b>)
#Give it a name, such as "Bugzilla Collect Stats"
#Perfom the task daily at your desired time
#If you're running Apache as a user, not as SYSTEM, enter that user here.  Otherwise you're best off creating an account that has write access to the Bugzilla directory and using that
#Tick "Open Advanced Properties.." and click Finish
#Append "-T" and the script name to the end of the "Run" field.  eg <b>C:\Perl\bin\perl.exe -T C:\Bugzilla\collectstats.pl</b>
#Change "start in" to the Bugzilla directory
 
====whineatnews.pl====
 
Add a Scheduled Task to run <b>whineatnews.pl</b> nightly.
 
The steps for setting up <b>whineatnews.pl</b> are as per <b>collectstats.pl</b>
 
====Backing up Bugzilla====
 
You may want to backup the entire Bugzilla directory.  It's small and you'll get all your settings and customisations on your backup media.
 
The most important component of Bugzilla to backup is the Bugzilla Database.  It contains all your Bugs, Users, Attachments, pretty well everything.  Like most databases, backups with MySql are performed by generating a dump of the database and backing up the dump.
 
Schedule the <b>mysqldump</b> utility to create the dump, and add the resulting file to your backup media.  You'll find MySql's <b>mysqldump</b> documentation at http://dev.mysql.com/doc/mysql/en/mysqldump.html.
 
====Congratulations, the Bugzilla installation process is complete!====

Latest revision as of 15:43, 17 February 2015

See http://bugzilla.readthedocs.org/en/latest/installing/windows.html .

Retrieved from "https://wiki.allizom.org/index.php?title=Bugzilla:Win32Install&oldid=1056473"