From 1a6e346ca51799b197070f0f2837e5fd8d930311 Mon Sep 17 00:00:00 2001
From: "jake%bugzilla.org" <>
Date: Fri, 4 Apr 2008 11:46:20 +0000
Subject: Bug 191034, step 1 - Refactoring the installation chapter to provide
sections for OS Specific notes and configuration help on multiple web
servers. Also added some terms to the glossary.
---
docs/en/xml/administration.xml | 473 ++++++++++++-----
docs/en/xml/glossary.xml | 95 +++-
docs/en/xml/installation.xml | 1129 ++++++++++++++--------------------------
3 files changed, 814 insertions(+), 883 deletions(-)
(limited to 'docs/en')
diff --git a/docs/en/xml/administration.xml b/docs/en/xml/administration.xml
index 847527203..3cd55a616 100644
--- a/docs/en/xml/administration.xml
+++ b/docs/en/xml/administration.xml
@@ -38,27 +38,24 @@
- usebuggroups:
- This dictates whether or not to implement group-based security for
- Bugzilla. If set, Bugzilla bugs can have an associated 'group',
- defining which users are allowed to see and edit the
- bug.
-
- Set "usebuggroups" to "on"
- only
- if you may wish to restrict access to particular bugs to certain
- groups of users. I suggest leaving
- this parameter off
- while initially testing your Bugzilla.
+ makeproductgroups:
+ This dictates whether or not to automatically create groups
+ when new products are created.
+
- usebuggroupsentry:
- Bugzilla Products can have a group associated with them, so that
- certain users can only see bugs in certain products. When this parameter
- is set to on, this places all newly-created bugs in the
- group for their product immediately.
+ useentrygroupdefault:
+ Bugzilla products can have a group associated with them, so that
+ certain users can only see bugs in certain products. When this
+ parameter is set to on, this
+ causes the initial group controls on newly created products
+ to place all newly-created bugs in the group
+ having the same name as the product immediately.
+ After a product is initially created, the group controls
+ can be further adjusted without interference by
+ this mechanism.
@@ -648,44 +645,83 @@
Groups allow the administrator
to isolate bugs or products that should only be seen by certain people.
- There are two types of group - Generic Groups, and Product-Based Groups.
+ The association between products and groups is controlled from
+ the product edit page under Edit Group Controls.
+
+
+
+ If the makeproductgroups param is on, a new group will be automatically
+ created for every new product.
- Product-Based Groups are matched with products, and allow you to restrict
- access to bugs on a per-product basis. They are enabled using the
- usebuggroups Param. Turning on the usebuggroupsentry
- Param will mean bugs automatically get added to their product group when
- filed.
+ On the product edit page, there is a page to edit the
+ Group Controls
+ for a product and determine which groups are applicable, default,
+ and mandatory for each product as well as controlling entry
+ for each product and being able to set bugs in a product to be
+ totally read-only unless some group restrictions are met.
- Generic Groups have no special relationship to products;
- you create them, and put bugs in them
- as required. One example of the use of Generic Groups
- is Mozilla's "Security" group,
- into which security-sensitive bugs are placed until fixed. Only the
- Mozilla Security Team are members of this group.
+ For each group, it is possible to specify if membership in that
+ group is...
+
+
+
+ required for bug entry,
+
+
+
+
+ Not applicable to this product(NA),
+ a possible restriction for a member of the
+ group to place on a bug in this product(Shown),
+ a default restriction for a member of the
+ group to place on a bug in this product(Default),
+ or a mandatory restriction to be placed on bugs
+ in this product(Mandatory).
+
+
+
+
+ Not applicable by non-members to this product(NA),
+ a possible restriction for a non-member of the
+ group to place on a bug in this product(Shown),
+ a default restriction for a non-member of the
+ group to place on a bug in this product(Default),
+ or a mandatory restriction to be placed on bugs
+ in this product when entered by a non-member(Mandatory).
+
+
+
+
+ required in order to make any change
+ to bugs in this product including comments.
+
+
+
- To create Generic Groups:
+ To create Groups:
- Select the "groups"
+ Select the groups
link in the footer.
- Take a moment to understand the instructions on the "Edit
- Groups" screen, then select the "Add Group" link.
+ Take a moment to understand the instructions on the Edit
+ Groups screen, then select the Add Group link.
- Fill out the "Group", "Description", and
- "User RegExp" fields. "New User RegExp" allows you to automatically
+ Fill out the Group, Description,
+ and User RegExp fields.
+ User RegExp allows you to automatically
place all users who fulfill the Regular Expression into the new group.
- When you have finished, click "Add".
+ When you have finished, click Add.The User Regexp is a perl regexp and, if not anchored, will match
any part of an address. So, if you do not want to grant access
@@ -701,28 +737,15 @@
- To use Product-Based Groups:
-
-
-
- Turn on "usebuggroups" and "usebuggroupsentry" in the "Edit
- Parameters" screen.
-
-
-
-
- In future, when you create a Product, a matching group will be
- automatically created. If you need to add a Product Group to
- a Product which was created before you turned on usebuggroups,
- then simply create a new group, as outlined above, with the
- same name as the Product.
-
-
-
Note that group permissions are such that you need to be a member
of all the groups a bug is in, for whatever
- reason, to see that bug.
+ reason, to see that bug. Similarly, you must be a member
+ of all of the entry groups for a product
+ to add bugs to a product and you must be a member
+ of all of the canedit groups for a product
+ in order to make any change to bugs in that
+ product.
@@ -750,12 +773,6 @@
To secure your installation:
-
- Ensure you are running at least MysQL version 3.22.32 or newer.
- Earlier versions had notable security holes and (from a security
- point of view) poor default configuration choices.
-
-
There is no substitute for understanding the tools on your
@@ -768,9 +785,9 @@
- Lock down /etc/inetd.conf. Heck, disable inet entirely on this
- box. It should only listen to port 25 for Sendmail and port 80 for
- Apache.
+ Lock down /etc/inetd.conf. Heck, disable
+ inet entirely on this box. It should only listen to port 25 for
+ Sendmail and port 80 for Apache.
@@ -798,27 +815,45 @@
Ensure you have adequate access controls for the
- $BUGZILLA_HOME/data/ directory, as well as the
- $BUGZILLA_HOME/localconfig file.
+ $BUGZILLA_HOME/data/ directory, as well as the
+ $BUGZILLA_HOME/localconfig file.
The localconfig file stores your "bugs" database account password.
In addition, some
- files under $BUGZILLA_HOME/data/ store sensitive information.
+ files under $BUGZILLA_HOME/data/ store sensitive
+ information.
- Bugzilla provides default .htaccess files to protect the most
- common Apache installations. However, you should verify these are
- adequate according to the site-wide security policy of your web
- server, and ensure that the .htaccess files are allowed to
- "override" default permissions set in your Apache configuration
- files. Covering Apache security is beyond the scope of this Guide;
- please consult the Apache documentation for details.
+ Also, beware that some text editors create backup files in the
+ current working directory so you need to also secure files like
+ localconfig~.
+
+
+
+ Simply blocking .*localconfig.*
+ won't work because the QuickSearch feature requires the web browser
+ to be able to retrieve localconfig.js and
+ others may be introduced in the future (see
+ bug
+ 186383 for more information.
+
+
+
+ Bugzilla provides default .htaccess files
+ to protect the most common Apache installations. However, you should
+ verify these are adequate according to the site-wide security policy
+ of your web server, and ensure that the .htaccess
+ files are allowed to override default permissions set
+ in your Apache configuration files. Covering Apache security is beyond
+ the scope of this Guide; please consult the Apache documentation for
+ details.
+ If you are using a web server that does not support the
- .htaccess control method,
+ .htaccess control method,
you are at risk!
After installing, check to see if you can view the file
- "localconfig" in your web browser (e.g.:
+ localconfig in your web browser (e.g.:
http://bugzilla.mozilla.org/localconfig
@@ -827,11 +862,14 @@
problem before deploying Bugzilla. If, however, it gives you a
"Forbidden" error, then it probably respects the .htaccess
conventions and you are good to go.
+
+ When you run checksetup.pl, the script will attempt to modify
various permissions on files which Bugzilla uses. If you do not have
- a webservergroup set in the localconfig file, then Bugzilla will have
- to make certain files world readable and/or writable.
+ a webservergroup set in the localconfig file,
+ then Bugzilla will have to make certain files world readable and/or
+ writable.
THIS IS INSECURE!
. This means that anyone who can get access to your system can do
@@ -844,44 +882,44 @@
installation.
- On Apache, you can use .htaccess files to protect access to
- these directories, as outlined in
- Bug
- 57161
+ On Apache, you can use .htaccess files to
+ protect access to these directories, as outlined in Bugs
+
+ 57161 and
+
+ 186383
- for the localconfig file, and
+ for the localconfig file, and
Bug
65572
- for adequate protection in your data/ directory.
+ for adequate protection in your data/ directory.
+ Also, don't forget about the template/ and
+ Bugzilla/ directories and to allow access to the
+ data/webdot directory for the
+ 192.20.225.10 IP address if you are
+ using webdot from research.att.com. The easiest way to
+ accomplish this is to set $create_htaccess to 1
+ in localconfig. However, the information below
+ is provided for those that want to know exactly what is created.
+
- Note the instructions which follow are Apache-specific. If you
+ FIX ME BEFORE RELEASE!!!!!
+ Note the instructions which follow are Apache-specific. If you
use IIS, Netscape, or other non-Apache web servers, please consult
your system documentation for how to secure these files from being
transmitted to curious users.
- Place the following text into a file named ".htaccess",
- readable by your web server, in your $BUGZILLA_HOME/data directory.
- <Files comments> allow from all </Files>
- deny from all
-
-
- Place the following text into a file named ".htaccess",
- readable by your web server, in your $BUGZILLA_HOME/ directory.
- <Files localconfig> deny from all </Files>
- allow from all
-
-
- Template Customisation
+ Template Customization
- One of the large changes for 2.16 was the templatisation of the
+ One of the large changes for 2.16 was the templatization of the
entire user-facing UI, using the
Template Toolkit.
Administrators can now configure the look and feel of Bugzilla without
@@ -890,9 +928,9 @@
- Templatisation also makes localised versions of Bugzilla possible,
+ Templatization also makes localized versions of Bugzilla possible,
for the first time. In the future, a Bugzilla installation may
- have templates installed for multiple localisations, and select
+ have templates installed for multiple localizations, and select
which ones to use based on the user's browser language setting.
@@ -903,7 +941,7 @@
and which you use depends mainly on how you upgrade Bugzilla. The
template directory structure is that there's a top level directory,
template, which contains a directory for
- each installed localisation. The default English templates are
+ each installed localization. The default English templates are
therefore in en. Underneath that, there
is the default directory and optionally the
custom directory. The default
@@ -913,7 +951,7 @@
- The first method of making customisations is to directly edit the
+ The first method of making customizations is to directly edit the
templates in template/en/default. This is
probably the best method for small changes if you are going to use
the CVS method of upgrading, because if you then execute a
@@ -1066,7 +1104,7 @@
There are a few templates you may be particularly interested in
- customising for your installation.
+ customizing for your installation.
@@ -1087,7 +1125,7 @@
global/banner.html.tmpl:
This contains the "banner", the part of the header that appears
at the top of all Bugzilla pages. The default banner is reasonably
- barren, so you'll probably want to customise this to give your
+ barren, so you'll probably want to customize this to give your
installation a distinctive look and feel. It is recommended you
preserve the Bugzilla version number in some form so the version
you are running can be determined, and users know what docs to read.
@@ -1168,7 +1206,7 @@
- Change Permission Customisation
+ Change Permission Customization
@@ -1190,7 +1228,7 @@
- For maximum flexibility, customising this means editing Bugzilla's Perl
+ For maximum flexibility, customizing this means editing Bugzilla's Perl
code. This gives the administrator complete control over exactly who is
allowed to do what. The relevant function is called
CheckCanChangeField(),
@@ -1222,7 +1260,7 @@
- More complex customisations are not much harder. Basically, you add
+ More complex customizations are not much harder. Basically, you add
a check in the right place in the function, i.e. after all the variables
you are using have been set up. So, don't look at $ownerid before
$ownerid has been obtained from the database. You can either add a
@@ -1257,42 +1295,203 @@
For a list of possible field names, look in
data/versioncache for the list called
@::log_columns. If you need help writing custom
- rules for your organisation, ask in the newsgroup.
+ rules for your organization, ask in the newsgroup.
Upgrading to New Releases
- A plain Bugzilla is fairly easy to upgrade from one version to a
- newer one. Always read the release notes to see if there are any issues
- that you might need to take note of. It is recommended that you take a
- backup of your database and your entire Bugzilla installation before attempting an
- upgrade. You can upgrade a 'clean' installation by untarring a new
- tarball over the old installation. If you are upgrading from 2.12 or
- later, and have cvs installed, you can type cvs -z3 update,
- and resolve conflicts if there are any.
+ Upgrading Bugzilla is something we all want to do from time to time,
+ be it to get new features or pick up the latest security fix. How easy
+ it is to update depends on a few factors.
-
- However, things get a bit more complicated if you've made
- changes to Bugzilla's code. In this case, you may have to re-make or
- reapply those changes. One good method is to take a diff of your customised
- version against the original, so you can survey all that you've changed.
- Hopefully, templatisation will reduce the need for
- this in the future.
-
- From version 2.8 onwards, Bugzilla databases can be automatically
- carried forward during an upgrade. However, because the developers of
- Bugzilla are constantly adding new
- tables, columns and fields, you'll probably get SQL errors if you just
- update the code and attempt to use Bugzilla. Always run the
- checksetup.pl
- script whenever you upgrade your installation.
-
- If you are running Bugzilla version 2.8 or lower, and wish to
- upgrade to the latest version, please consult the file,
- "UPGRADING-pre-2.8" in the Bugzilla root directory after untarring the
- archive.
+
+
+
+ If the new version is a revision or a new point release
+
+
+ How many, if any, local changes have been made
+
+
+
+ There are also three different methods to upgrade your installation.
+
+
+
+
+ Using CVS ()
+
+
+ Downloading a new tarball ()
+
+
+ Applying the relevant patches ()
+
+
+
+ Which options are available to you may depend on how large a jump
+ you are making and/or your network configuration.
+
+
+ Revisions are normally released to fix security vulnerabilities
+ and are distinguished by an increase in the third number. For example,
+ when 2.16.2 was released, it was a revision to 2.16.1.
+
+
+ Point releases are normally released when the Bugzilla team feels
+ that there has been a significant amount of progress made between the
+ last point release and the current time. These are often proceeded by a
+ stabilization period and release candidates, however the use of
+ development versions or release candidates is beyond the scope of this
+ document. Point releases can be distinguished by an increase in the
+ second number, or minor version. For example, 2.16.2 is a newer point
+ release than 2.14.5.
+
+
+ The examples in this section are written as if you were updating
+ to version 2.16.2. The procedures are the same regardless if you are
+ updating to a new point release or a new revision. However, the chance
+ of running into trouble increases when upgrading to a new point release,
+ escpecially if you've made local changes.
+
+
+ These examples also assume that your Bugzilla installation is at
+ /var/www/html/bugzilla. If that is not the case,
+ simply substitute the proper paths where appropriate.
+
+
+
+ Upgrading using CVS
+
+ Every release of Bugzilla, whether it is a revision or a point
+ release, is tagged in CVS. Also, every tarball we have distributed
+ since version 2.12 has been primed for using CVS. This does, however,
+ require that you are able to access cvs-mirror.mozilla.org on port
+ 2401.
+
+
+ If you can do this, updating using CVS is probably the most
+ painless method, especially if you have a lot of local changes.
+
+
+
+
+
+bash$ cd /var/www/html/bugzilla
+bash$ cvs login
+Logging in to :pserver:anonymous@cvs-mirror.mozilla.org:2401/cvsroot
+CVS password: anonymous
+bash$ cvs -q update -r BUGZILLA-2_16_2 -dP
+P checksetup.pl
+P collectstats.pl
+P globals.pl
+P docs/rel_notes.txt
+P template/en/default/list/quips.html.tmpl
+
+
+
+
+ If a line in the output from cvs update
+ begins with a C that represents a
+ file with local changes that CVS was unable to properly merge. You
+ need to resolve these conflicts manually before Bugzilla (or at
+ least the portion using that file) will be usable.
+
+
+
+
+ You also need to run ./checksetup.pl
+ before your Bugzilla upgrade will be complete.
+
+
+
+
+
+
+ Upgrading using the tarball
+
+ If you are unable or unwilling to use CVS, another option that's
+ always available is to download the latest tarball. This is the most
+ difficult option to use, especially if you have local changes.
+
+
+
+bash$ cd /var/www/html
+bash$ wget ftp://ftp.mozilla.org/pub/webtools/bugzilla-2.16.2.tar.gz
+Output omitted
+bash$ tar xzvf bugzilla-2.16.2.tar.gz
+bugzilla-2.16.2/
+bugzilla-2.16.2/.cvsignore
+bugzilla-2.16.2/1x1.gif
+Output truncated
+bash$ cd bugzilla-2.16.2
+bash$ cp ../bugzilla/localconfig* .
+bash$ cp -r ../bugzilla/data .
+bash$ cd ..
+bash$ mv bugzilla bugzilla.old
+bash$ mv bugzilla-2.16.2 bugzilla
+bash$ cd bugzilla
+bash$ ./checksetup.pl
+Output omitted
+
+
+
+
+ The cp commands both end with periods which
+ is a very important detail, it tells the shell that the destination
+ directory is the current working directory. Also, the period at the
+ beginning of the ./checksetup.pl is important and
+ can not be omitted.
+
+
+
+
+ You will now have to reapply any changes you have made to your
+ local installation manually.
+
+
+
+
+
+
+ Upgrading using patches
+
+ The Bugzilla team will normally make a patch file available for
+ revisions to go from the most recent revision to the new one. You could
+ also read the release notes and grab the patches attached to the
+ mentioned bug, but it is safer to use the released patch file as
+ sometimes patches get changed before they get checked in (for minor
+ spelling fixes and the like). It is also theorectically possible to
+ scour the fixed bug list and pick and choose which patches to apply
+ from a point release, but this is not recommended either as what you'll
+ end up with is a hodge podge Bugzilla that isn't really any version.
+ This would also make it more difficult to upgrade in the future.
+
+
+
+bash$ cd /var/www/html/bugzilla
+bash$ wget ftp://ftp.mozilla.org/pub/webtools/bugzilla-2.16.1-to-2.16.2.diff.gz
+Output omitted
+bash$ gunzip bugzilla-2.16.1-to-2.16.2.diff.gz
+bash$ patch -p1 < bugzilla-2.16.1-to-2.16.2.diff
+patching file checksetup.pl
+patching file collectstats.pl
+patching file globals.pl
+
+
+
+
+ If you do this, beware that this doesn't change the entires in
+ your CVS directory so it may make
+ updates using CVS () more difficult in the
+ future.
+
+
+
+
+
diff --git a/docs/en/xml/glossary.xml b/docs/en/xml/glossary.xml
index cc5d4fb69..fb55363e6 100644
--- a/docs/en/xml/glossary.xml
+++ b/docs/en/xml/glossary.xml
@@ -24,23 +24,66 @@
A
-
+ ApacheIn this context, Apache is the web server most commonly used
- for serving up
- Bugzilla
-
+ for serving up Bugzilla
pages. Contrary to popular belief, the apache web server has nothing
to do with the ancient and noble Native American tribe, but instead
derived its name from the fact that it was
a patchy
-
version of the original
NCSA
-
world-wide-web server.
+
+
+ Useful Directives when configuring Bugzilla
+
+
+ AddHandler
+
+ Tell Apache that it's OK to run CGI scripts.
+
+
+
+ AllowOverride
+ Options
+
+ These directives are used to tell Apache many things about
+ the directory they apply to. For Bugzilla's purposes, we need
+ them to allow script execution and .htaccess
+ overrides.
+
+
+
+
+ DirectoryIndex
+
+ Used to tell Apache what files are indexes. If you can
+ not add index.cgi to the list of valid files,
+ you'll need to set $index_html to
+ 1 in localconfig so
+ ./checksetup.pl will create an
+ index.html that redirects to
+ index.cgi.
+
+
+
+
+ ScriptInterpreterSource
+
+ Used when running Apache on windows so the shebang line
+ doesn't have to be changed in every Bugzilla script.
+
+
+
+
+
+ For more information about how to configure Apache for Bugzilla,
+ see .
+
@@ -89,6 +132,17 @@
+
+ Common Gateway Interface
+ CGI
+
+ CGI is an acronym for Common Gateway Interface. This is
+ a standard for interfacing an external application with a web server. Bugzilla
+ is an example of a CGI application.
+
+
+
+
Component
@@ -138,10 +192,9 @@
-
-
+ G
-
+ Groups
@@ -159,6 +212,18 @@
+
+ J
+
+
+ JavaScript
+
+ JavaScript is cool, we should talk about it.
+
+
+
+
+
M
@@ -291,6 +356,18 @@
fixed, or an enhancement will be implemented.
+
+
+ Tool Command Language
+ TCL
+
+ TCL is an open source scripting language available for Windows,
+ Macintosh, and Unix based systems. Bugzilla 1.0 was written in TCL but
+ never released. The first release of Bugzilla was 2.0, which was when
+ it was ported to perl.
+
+
+
diff --git a/docs/en/xml/installation.xml b/docs/en/xml/installation.xml
index 145f39c89..0770ae4af 100644
--- a/docs/en/xml/installation.xml
+++ b/docs/en/xml/installation.xml
@@ -5,20 +5,20 @@
Step-by-step Install
-
+ IntroductionBugzilla 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
+
for further advice on getting Bugzilla to work on Microsoft
Windows.
-
+ Package List
@@ -483,7 +483,7 @@
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.
@@ -523,65 +523,22 @@
-
+ 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
- user permissions accordingly.
+ You have freedom of choice here, pretty much any web server that
+ is capable of running CGI
+ scripts will work. has more information about
+ configuring web servers to work with Bugzilla.
+
+
We strongly recommend Apache as the web server to use. The
Bugzilla Guide installation instructions, in general, assume you are
using Apache. If you have got Bugzilla working using another webserver,
please share your experiences with us.
-
-
- 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:
-
-
- 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
-
- for details on how to do this for Apache; the checksetup.pl
- script should create appropriate .htaccess files for you.
-
@@ -598,7 +555,7 @@ AllowOverride Limit
If you symlink the bugzilla directory into your Apache's HTML
- heirarchy, you may receive
+ hierarchy, you may receive
Forbidden
errors unless you add the
FollowSymLinks
@@ -829,7 +786,7 @@ perl -pi -e 's@#\!/usr/bonsaitools/bin/perl@#\!/usr/bin/perl@' *cgi *pl Bug.pm p
- 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.
@@ -1005,7 +962,7 @@ perl -pi -e 's@#\!/usr/bonsaitools/bin/perl@#\!/usr/bin/perl@' *cgi *pl Bug.pm p
Alternatively, you could set up a webdot server, or use the AT&T
public webdot server (the
default for the webdotbase param). Note that AT&T's server won't work
- if Bugzilla is only accessible using HTTPS.
+ if Bugzilla is only accessible using HARTS.
@@ -1335,762 +1292,460 @@ bash# perl -pi -e "s/Content-Type\: text\/html/Content-Type\: text\/html\; chars
-
- Win32 Installation Notes
-
- This section covers installation on Microsoft Windows.
- Bugzilla has been made to work on Win32 platforms, but the Bugzilla team
- wish to emphasise that The easiest way to install Bugzilla on
- Intel-archiecture machines
- is to install some variant of GNU/Linux, then follow the UNIX
- installation instructions in this Guide. If you have any influence in the
- platform choice for running this system, please choose GNU/Linux instead
- of Microsoft Windows.
-
-
- After that warning, here's the situation for 2.16
- and Windows. It doesn't work at all out of the box.
- You are almost certainly better off getting
- the 2.17 version from CVS (after consultation with the Bugzilla Team to
- make sure you are pulling on a stable day) because we'll be doing a load
- of work to make the Win32 experience more pleasant than it is now.
-
-
-
-
- If you still want to try this, to have any hope of getting it to work,
- you'll need to apply the
- mail patch from
- bug 124174.
- After that, you'll need to read the (outdated) installation
- instructions below, some (probably a lot better) more
- recent ones kindly provided by Toms Baugis and Jean-Sebastien
- Guay, and also check the
- Bugzilla 2.16 Win32 update page
- . If we get time,
- we'll write some better installation instructions for 2.16 and put
- them up there. But no promises.
+
+ OS Specific Installation Notes
+
+ Many aspects of the Bugzilla installation can be affected by the
+ the operating system you choose to install it on. Sometimes it can be made
+ easier and others more difficult. This section will attempt to help you
+ understand both the difficulties of running on specific operating systems
+ and the utilities available to make it easier.
-
-
- Win32 Installation: Step-by-step
-
- You should be familiar with, and cross-reference, the rest of
- the
-
+ If you have anything to add or notes for an operating system not
+ covered, please file a bug in &bzg-bugs;.
+
- section while performing your Win32 installation.
+
+ Microsoft Windows
- Making Bugzilla work on Microsoft Windows is no picnic. Support
- for Win32 has improved dramatically in the last few releases, but, if
- you choose to proceed, you should be a
- very
+ Making Bugzilla work on windows is still a very painful processes.
+ The Bugzilla Team is working to make it easier, but that goal is not
+ considered a top priority. If you wish to run Bugzilla, we still
+ recommend doing so on a Unix based system such as GNU/Linux. As of this
+ writing, all members of the Bugzilla team and all known large installations
+ run on Unix based systems.
+
- skilled Windows Systems Administrator with strong troubleshooting
- abilities, a high tolerance for pain, and moderate perl skills.
- Bugzilla on NT requires hacking source code and implementing some
- advanced utilities. What follows is the recommended installation
- procedure for Win32; additional suggestions are provided in
-
+ If after hearing all that, you have enough pain tolerance to attempt
+ installing Bugzilla on Win32, here are some pointers.
+
+
- .
-
+
+ Win32 Perl
-
-
- Install
- Apache Web Server
+ Perl for Windows can be obtained from ActiveState. You should be
+ able to find a compiled binary at http://aspn.activestate.com/ASPN/Downloads/ActivePerl/.
+
+
- for Windows, and copy the Bugzilla files somewhere Apache can serve
- them. Please follow all the instructions referenced in
-
+
+ Perl Modules on Win32
- regarding your Apache configuration, particularly instructions
- regarding the
- AddHandler
+ Bugzilla on Windows requires the same perl modules found in
+ . The main difference is that
+ windows uses ppm instead of CPAN.
+
- parameter and
- ExecCGI
+
+C:\perl> ppm <module name>
+
- .
+
+ The above syntax should work for all modules with the exception
+ of Template Toolkit. The Template Toolkit website
+ suggests using the instructions on OpenInteract's website.
+
+
-
- You may also use Internet Information Server or Personal
- Web Server for this purpose. However, setup is quite different.
- If ActivePerl doesn't seem to handle your file associations
- correctly (for .cgi and .pl files), please consult
-
+
+ A complete list of modules that can be installed using ppm can
+ be found at http://www.activestate.com/PPMPackages/5.6plus.
+
+
+
- .
+
+ Code changes required to run on win32
- If you are going to use IIS, if on Windows NT you must be
- updated to at least Service Pack 4. Windows 2000 ships with a
- sufficient version of IIS.
-
-
+ Unfortunately, Bugzilla still doesn't run "out of the box" on
+ Windows. There is work in progress to make this easier, but until that
+ happens code will have to be modified. This section is an attempt to
+ list the required changes. It is an attempt to be all inclusive, but
+ there may be other changes required. If you find something is missing,
+ please file a bug in &bzg-bugs;.
+
-
- Install
- ActivePerl
+
+ Changes to <filename>checksetup.pl</filename>
- for Windows. Check
-
- http://aspn.activestate.com/ASPN/Downloads/ActivePerl
+ In checksetup.pl, the line reading:
- for a current compiled binary.
+
+my $mysql_binaries = `which mysql`;
+
+ to
+
+my $mysql_binaries = "D:\\mysql\\bin\\mysql";
+
- Please also check the following links to fully understand the
- status of ActivePerl on Win32:
-
- Perl Porting
+ And you'll also need to change:
- , and
-
- Perl on Win32 FAQ
-
-
-
-
- Use ppm from your perl\bin directory to install the following
- packs: DBI, DBD-Mysql, TimeDate, Chart, Date-Calc, Date-Manip, GD,
- AppConfig, and Template. You may need to extract them from .zip
- format using Winzip or other unzip program first. Most of these
- additional ppm modules can be downloaded from ActiveState, but
- AppConfig and Template should be obtained from OpenInteract using
- the
- instructions on the Template Toolkit web site
-
- .
-
-
- You can find a list of modules at
-
- http://www.activestate.com/PPMPackages/zips/5xx-builds-only/
-
- or
-
- http://www.activestate.com/PPMPackages/5.6plus
-
-
+
+my $webservergid = getgrnam($my_webservergroup)
+
+ to
+
+my $webservergid = '8'
+
+
- The syntax for ppm is:
-
- C:>
+
+ Making mail work
- ppm <modulename>
-
+ The easiest way to get mail working is to use the mail patches
+ on bug
+ 124174. With any luck, this patch will receive the required
+ reviews and integrated into the main Bugzilla distribution very soon.
+ Until that happens, there's at least one report of this patch working
+ well on Windows.
-
- Installing ActivePerl ppd Modules on Microsoft
- Windows
-
-
- C:>
-
- ppm
-
-
-
+
- Watch your capitalization!
-
+
+ System Calls
- ActiveState's 5.6Plus directory also contains an AppConfig
- ppm, so you might see the following error when trying to install
- the version at OpenInteract:
+ In order to get system calls to work on win32's perl, you need
+ to tell the windows shell what interpreter to use. This is done by
+ changing the system calls. You will need to
+ search all of Bugzilla's code for system calls.
+ To tell perl your interpreter, it needs to be the first argument to
+ the system call. For example, you'll need to
+ change:
+
+
+
+system("./processmail", $id, $exporter);
+
+ with
+
+system("C:\\perl\\bin\\perl", "processmail", $id, $exporter);
+
-
- Error installing package 'AppConfig': Read a PPD
- for 'AppConfig', but it is not intended for this build of Perl
- (MSWin32-x86-multi-thread)
+ Notice that the ./ is also
+ removed.
- If so, download both
-
- the tarball
+
+ The grep command is very helpful in finding
+ these system calls, assuming you have the
+ cygwin utilities.
+
+
- and
-
- the ppd
+
- directly from OpenInteract, then run ppm from within the same
- directory to which you downloaded those files and install the
- package by referencing the ppd file explicitly via in the install
- command, f.e.:
-
- Installing OpenInteract ppd Modules manually on Microsoft
- Windows
+
-
-
- install
- C:\AppConfig.ppd
-
-
-
-
-
-
+
+ Serving the web pages
-
- Install MySQL for NT.
-
- You can download MySQL for Windows NT from
- MySQL.com
+ As is the case on Unix based systems, any web server should be
+ able to handle Bugzilla; however, the Bugzilla Team still recommends
+ Apache whenever asked. No matter what web server you choose, be sure
+ to pay attention to the security notes in .
+ More information on configuring specific web servers can be found in
+ .
+
- . Some find it helpful to use the WinMySqlAdmin utility, included
- with the download, to set up the database.
-
+
+ If using Apache on windows, you can set the ScriptInterpreterSource
+ directive in your Apache config, if you don't do this, you'll have
+ to modify the first line of every script to contain your path to
+ perl instead of /usr/bonsaitools/bin/perl.
-
-
-
- Setup MySQL
-
-
-
-
-
- C:>
-
- C:\mysql\bin\mysql -u root mysql
-
-
-
-
-
-
-
- mysql>
-
- DELETE FROM user WHERE Host='localhost' AND
- User='';
-
-
-
-
-
-
-
- mysql>
-
- UPDATE user SET Password=PASSWORD ('new_password')
- WHERE user='root';
-
-
-
-
- new_password
-
- , above, indicates whatever password you wish to use for your
- root
-
- user.
-
-
-
-
-
- mysql>
-
- GRANT SELECT, INSERT, UPDATE, DELETE, INDEX,
- ALTER, CREATE, DROP, REFERENCES ON bugs.* to bugs@localhost
- IDENTIFIED BY 'bugs_password';
-
-
-
-
- bugs_password
-
- , above, indicates whatever password you wish to use for your
- bugs
-
- user.
-
-
-
-
-
- mysql>
-
- FLUSH PRIVILEGES;
-
-
-
-
-
-
-
- mysql>
-
- create database bugs;
-
-
-
-
-
-
-
- mysql>
-
- exit;
-
-
-
-
-
-
-
- C:>
-
- C:\mysql\bin\mysqladmin -u root -p
- reload
-
-
-
-
-
-
-
- Edit
- checksetup.pl
-
- in your Bugzilla directory. Change this line:
+
-
- my $webservergid =
- getgrnam($my_webservergroup);
-
+
- to
+
-
- my $webservergid =
- $my_webservergroup;
+
+ <productname>Mac OS X</productname>
+
+
+ There are a lot of common libraries and utilities out there that
+ Apple did not include with Mac OS X, but which run perfectly well on it.
+ The GD library, which Bugzilla needs to do bug graphs, is one of
+ these.
+
+ The easiest way to get a lot of these is with a program called
+ Fink, which is similar in nature to the CPAN installer, but installs
+ common GNU utilities. Fink is available from
+ .
+
+ Follow the instructions for setting up Fink. Once it's installed,
+ you'll want to run the following as root:
+ fink install gd
+
+
+ It will prompt you for a number of dependencies, type 'y' and hit
+ enter to install all of the dependencies. Then watch it work.
+
+ To prevent creating conflicts with the software that Apple installs
+ by default, Fink creates its own directory tree at /sw where it installs
+ most of the software that it installs. This means your libraries and
+ headers for libgd will be at /sw/lib and /sw/include instead of /usr/lib
+ and /usr/local/include. Because of these changed locations for the
+ libraries, the Perl GD module will not install directly via CPAN, because it
+ looks for the specific paths instead of getting them from your
+ environment. But there's a way around that :-)
+
+ Instead of typing
+ install GD
+ at the
+ cpan>
+ prompt, type
+ look GD.
+ This should go through the motions of downloading the latest version of
+ the GD module, then it will open a shell and drop you into the build
+ directory. Apply this patch
+ to the Makefile.PL file (save the
+ patch into a file and use the command
+ patch < patchfile.)
+
+
+ Then, run these commands to finish the installation of the GD
+ module:
+
+
+ perl Makefile.PL
+
- or the name of the group you wish to own the files explicitly:
- my $webservergid =
- 'Administrators'
-
-
+
+ make
+
-
- Run
- checksetup.pl
+
+ make test
+
- from the Bugzilla directory.
-
+
+ make install
+
-
- Edit
- localconfig
+ And don't forget to run
+ exit
- to suit your requirements. Set
- $db_pass
+ to get back to CPAN.
+
+
- to your
- bugs_password
+
- from
-
+
- , and
- $webservergroup
+
+ HTTP Server Configuration
- to
- 8
+ The Bugzilla Team recommends Apache when using Bugzilla, however, any web server
+ that can be configured to run CGI scripts
+ should be able to handle Bugzilla. No matter what web server you choose, but
+ especially if you choose something other than Apache, you should be sure to read
+ .
+
- .
+ The plan for this section is to eventually document the specifics of how to lock
+ down permissions on individual web servers.
+
-
- Not sure on the
- 8
+
+ Apache <productname>httpd</productname>
+
+ As mentioned above, the Bugzilla Team recommends Apache for use
+ with Bugzilla. You will have to make sure that Apache is properly
+ configured to run the Bugzilla CGI scripts. You also need to make sure
+ that the .htaccess files created by
+ ./checksetup.pl (shown in
+ for the curious) are allowed to override Apache's normal access
+ permissions or else important password information may be exposed to the
+ Internet.
+
+
+ Many Apache installations are not configured to run scripts
+ anywhere but in the cgi-bin
+ directory; however, we recommend that Bugzilla not be installed in the
+ cgi-bin, otherwise the static
+ files such as images and
+ will not work correctly. To allow scripts to run in the normal
+ web space, the following changes should be made to your
+ httpd.conf file.
+
- for
- $webservergroup
+ To allow files with a .cgi extension to be run, make sure the
+ following line exists and is uncommented:
+
+AddHandler cgi-script .cgi
+
- above. If it's wrong, please send corrections.
-
-
+ To allow .htaccess files to override
+ permissions and .cgi files to run in the Bugzilla directory, make sure
+ the following two lines are in a Directory
+ directive that applies to the Bugzilla directory on your system
+ (either the Bugzilla directory or one of its parents).
+
+
+Options +ExecCGI
+AllowOverride Limit
+
-
- Edit
- defparams.pl
+
+ For more information on Apache and its directives, see the
+ glossary entry on .
+
+
- to suit your requirements. Particularly, set
- DefParam("maintainer")
+
+ <filename>.htaccess</filename> files for Apache
+
+ $BUGZILLA_HOME/.htaccess
+
+ deny from all
+
+
+ allow from all
+
+ ]]>
+
- and
- DefParam("urlbase") to match your install.
+ $BUGZILLA_HOME/data/.htaccess
+
+ allow from all
+
+ ]]>
-
- This is yet another step I'm not sure of, since the
- maintainer of this documentation does not maintain Bugzilla on
- NT. If you can confirm or deny that this step is required, please
- let me know.
-
-
-
-
-
- There are several alternatives to Sendmail that will work
- on Win32. The one mentioned here is a
- suggestion
-
- , not a requirement. Some other mail packages that can work
- include
- BLAT
-
- ,
- Windmail
-
- ,
- Mercury
- Sendmail
-
- , and the CPAN Net::SMTP Perl module (available in .ppm). Every
- option requires some hacking of the Perl scripts for Bugzilla to
- make it work. The option here simply requires the least.
-
-
-
-
- Download NTsendmail, available from
-
- www.ntsendmail.com
-
- . You must have a "real" mail server which allows you to relay
- off it in your $ENV{"NTsendmail"} (which you should probably
- place in globals.pl)
-
-
-
- Put ntsendmail.pm into your .\perl\lib directory.
-
-
-
- Add to globals.pl:
-
- # these settings configure the NTsendmail
- process use NTsendmail;
- $ENV{"NTsendmail"}="your.smtpserver.box";
- $ENV{"NTsendmail_debug"}=1;
- $ENV{"NTsendmail_max_tries"}=5;
-
-
- Some mention to also edit
- $db_pass
-
- in
- globals.pl
-
- to be your
- bugs_password
-
- . Although this may get you around some problem
- authenticating to your database, since globals.pl is not
- normally restricted by
- .htaccess
-
- , your database password is exposed to whoever uses your web
- server.
-
-
-
-
- Find and comment out all occurences of
-
- open(SENDMAIL
-
-
- in your Bugzilla directory. Then replace them with:
- # new sendmail functionality my $mail=new
- NTsendmail; my $from="bugzilla\@your.machine.name.tld"; my
- $to=$login; my $subject=$urlbase;
- $mail->send($from,$to,$subject,$msg);
-
-
-
- Some have found success using the commercial product,
- Windmail
-
- . You could try replacing your sendmail calls with:
- open SENDMAIL,
- "|\"C:/General/Web/tools/Windmail 4.0 Beta/windmail\" -t >
- mail.log";
-
- or something to that effect.
-
-
-
-
-
-
- Change all references in all files from
- processmail
-
- to
- processmail.pl
-
- , and rename
- processmail
-
- to
- processmail.pl
-
- .
-
-
- Many think this may be a change we want to make for
- main-tree Bugzilla. It's painless for the UNIX folks, and will
- make the Win32 people happier.
-
-
-
- Some people have suggested using the Net::SMTP Perl module
- instead of NTsendmail or the other options listed here. You can
- change processmail.pl to make this work.
-
-new(''); #connect to SMTP server
-$smtp->mail('@');# use the sender's adress here
-$smtp->to($tolist); # recipient's address
-$smtp->data(); # Start the mail
-$smtp->datasend($msg);
-$smtp->dataend(); # Finish sending the mail
-$smtp->quit; # Close the SMTP connection
-$logstr = "$logstr; mail sent to $tolist $cclist";
-}
+ $BUGZILLA_HOME/data/webdot
+
+ Allow from 192.20.225.10
+ Deny from all
+
+
+# Allow access by a local copy of 'dot' to .png, .gif, .jpg, and
+# .map files
+
+ Allow from all
+
+
+# And no directory listings, either.
+Deny from all
+ ]]>
+
-]]>
-
-
- here is a test mail program for Net::SMTP:
-
-new(' 30, Debug
-=> 1, ); # connect to SMTP server
- $smtp->auth;
- $smtp->mail('you@yourcompany.com');# use the sender's adress
-here
- $smtp->to('someotherAddress@someotherdomain.com'); #
-recipient's address
- $smtp->data(); # Start the mail
- $smtp->datasend('test');
- $smtp->dataend(); # Finish sending the mail
- $smtp->quit; # Close the SMTP connection
-exit;
-
-]]>
-
-
-
-
-
-
-
- This step is optional if you are using IIS or another web
- server which only decides on an interpreter based upon the file
- extension (.pl), rather than the
- shebang
-
- line (#/usr/bonsaitools/bin/perl)
-
-
- Modify the path to perl on the first line (#!) of all files
- to point to your Perl installation, and add
- perl
-
- to the beginning of all Perl system calls that use a perl script as
- an argument. This may take you a while. There is a
- setperl.csh
-
- utility to speed part of this procedure, available in the
-
-
- section of The Bugzilla Guide. However, it requires the Cygwin
- GNU-compatible environment for Win32 be set up in order to work.
- See
- http://www.cygwin.com/
-
- for details on obtaining Cygwin.
-
-
-
- Modify the invocation of all system() calls in all perl
- scripts in your Bugzilla directory. You should specify the full
- path to perl for each system() call. For instance, change this line
- in processmail:
+ $BUGZILLA_HOME/Bugzilla/.htaccess
- to
-
-system ("C:\\perl\\bin\\perl", "processmail", @ARGLIST);
-]]>
+# nothing in this directory is retrievable unless overriden by an .htaccess
+# in a subdirectory
+deny from all
-
-
-
-
- If you are using IIS or Personal Web Server, you must add cgi
- relationships to Properties -> Home directory (tab) ->
- Application Settings (section) -> Configuration (button), such
- as:
+ $BUGZILLA_HOME/template/.htaccess
+
+# nothing in this directory is retrievable unless overriden by an .htaccess
+# in a subdirectory
+deny from all
+
+
-
- .cgi to: <perl install directory>\perl.exe %s
- %s .pl to: <perl install directory>\perl.exe %s %s
- GET,HEAD,POST
+
- Change the path to Perl to match your install, of course.
-
-
- Additional Windows Tips
+
+ Microsoft <productname>Internet Information Services</productname>
-
- From Andrew Pearson:
-
- You can make Bugzilla work with Personal Web Server for
- Windows 98 and higher, as well as for IIS 4.0. Microsoft has
- information available at
-
- http://support.microsoft.com/support/kb/articles/Q231/9/98.ASP
-
-
- Basically you need to add two String Keys in the registry at
- the following location:
+ If you need, or for some reason even want, to use Microsoft's
+ Internet Information Services or
+ Personal Web Server you should be able
+ to. You will need to configure them to know how to run CGI scripts,
+ however. This is described in Microsoft Knowledge Base article
+ Q245225
+ for Internet Information Services and
+ Q231998
+ for Personal Web Server.
+
-
-
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\ScriptMap
-
+ Also, and this can't be stressed enough, make sure that files such as
+ localconfig and your data
+ directory are secured as described in .
+
- The keys should be called ".pl" and ".cgi", and both should
- have a value something like:
- c:/perl/bin/perl.exe "%s" "%s"
-
+
- The KB article only talks about .pl, but it goes into more
- detail and provides a perl test script.
-
-
-
+
+ AOL Server
-
- If attempting to run Bugzilla 2.12 or older, you will need to
- remove encrypt() calls from the Perl source. This is
- not necessary
+ Ben FrantzDale reported success using AOL Server with Bugzilla. He
+ reported his experience and what appears below is based on that.
+
- for Bugzilla 2.13 and later, which includes the current release,
- Bugzilla &bz-ver;.
-
- Removing encrypt() for Windows NT Bugzilla version 2.12 or
- earlier
+ AOL Server will have to be configured to run
+ CGI scripts, please consult
+ the documentation that came with your server for more information on
+ how to do this.
+
- Replace this:
- SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) .
- ", " . SQLQuote(substr($realcryptpwd, 0, 2)) . ")"); my
- $enteredcryptpwd = FetchOneColumn();
+ Because AOL Server doesn't support .htaccess
+ files, you'll have to create a TCL
+ script. You should create an aolserver/modules/tcl/filter.tcl
+ file (the filename shouldn't matter) with the following contents (change
+ /bugzilla/ to the web-based path to
+ your Bugzilla installation):
+
- with this:
- my $enteredcryptpwd = $enteredpwd
+
+ns_register_filter preauth GET /bugzilla/localconfig filter_deny
+ns_register_filter preauth GET /bugzilla/*.pl filter_deny
+ns_register_filter preauth GET /bugzilla/localconfig filter_deny
+ns_register_filter preauth GET /bugzilla/processmail filter_deny
+ns_register_filter preauth GET /bugzilla/syncshadowdb filter_deny
+ns_register_filter preauth GET /bugzilla/runtests.sh filter_deny
+
+proc filter_deny { why } {
+ ns_log Notice "filter_deny"
+ return "filter_return"
+}
+
- in cgi.pl.
-
+
+ This doesn't appear to account for everything mentioned in
+ . In particular, it doesn't block access
+ to the data or
+ template directories. It also
+ doesn't account for the editor backup files that were the topic of
+ bug
+ 186383, Bugtraq ID 6501,
+ and a partial cause for the 2.16.2 release.
-
+
-
- Mac OS X Installation Notes
-
- There are a lot of common libraries and utilities out there that
- Apple did not include with Mac OS X, but which run perfectly well on it.
- The GD library, which Bugzilla needs to do bug graphs, is one of
- these.
-
- The easiest way to get a lot of these is with a program called
- Fink, which is similar in nature to the CPAN installer, but installs
- common GNU utilities. Fink is available from
- <http://sourceforge.net/projects/fink/>.
-
- Follow the instructions for setting up Fink. Once it's installed,
- you'll want to run the following as root:
- fink install gd
-
-
- It will prompt you for a number of dependencies, type 'y' and hit
- enter to install all of the dependencies. Then watch it work.
-
- To prevent creating conflicts with the software that Apple installs
- by default, Fink creates its own directory tree at /sw where it installs
- most of the software that it installs. This means your libraries and
- headers for libgd will be at /sw/lib and /sw/include instead of /usr/lib
- and /usr/local/include. Because of these changed locations for the
- libraries, the Perl GD module will not install directly via CPAN, because it
- looks for the specific paths instead of getting them from your
- environment. But there's a way around that :-)
-
- Instead of typing
- install GD
- at the
- cpan>
- prompt, type
- look GD.
- This should go through the motions of downloading the latest version of
- the GD module, then it will open a shell and drop you into the build
- directory. Apply this patch
- to the Makefile.PL file (save the
- patch into a file and use the command
- patch < patchfile.)
-
-
- Then, run these commands to finish the installation of the GD
- module:
-
-
- perl Makefile.PL
-
-
-
- make
-
-
-
- make test
-
-
-
- make install
-
-
- And don't forget to run
- exit
-
- to get back to CPAN.
-
-
-
-
-
Troubleshooting
--
cgit v1.2.3-24-g4f1b