It is now possible to run the Bugzilla software under mod_perl on Apache.   mod_perl has some additional requirements to that of running Bugzilla under   mod_cgi (the standard and previous way).   Bugzilla requires mod_perl to be installed, which can be obtained from   http://perl.apache.org - Bugzilla requires version 1.999022 (AKA 2.0.0-RC5)   to be installed.   Bugzilla also requires a more up-to-date version of the CGI perl module to   be installed, version 3.11 as opposed to 2.93     _________________________________________________________________2.2. Configuration   Warning   Poorly-configured MySQL and Bugzilla installations have given attackers full   access to systems in the past. Please take the security parts of these   guidelines seriously, even for Bugzilla machines hidden away behind your   firewall. Be certain to read Chapter 4 for some important security tips.     _________________________________________________________________2.2.1. localconfig   You should now run checksetup.pl again, this time without the   --check-modules switch.   bash# ./checksetup.pl   This time, checksetup.pl should tell you that all the correct modules are   installed and will display a message about, and write out a file called,   localconfig. This file contains the default settings for a number of   Bugzilla parameters.   Load this file in your editor. The only value you need to change is   $db_pass, the password for the user you will create for your database. Pick   a strong password (for simplicity, it should not contain single quote   characters) and put it here.   You may need to change the value of webservergroup if your web server does   not run in the "apache" group. On Debian, for example, Apache runs in the   "www-data" group. If you are going to run Bugzilla on a machine where you do   not have root access (such as on a shared web hosting account), you will   need to leave webservergroup empty, ignoring the warnings that checksetup.pl   will subsequently display every time it is run.   Caution   If you are using suexec, you should use your own primary group for   webservergroup rather than leaving it empty, and see the additional   directions in the suexec section Section 2.6.6.1.   The other options in the localconfig file are documented by their   accompanying comments. If you have a slightly non-standard MySQL setup, you   may wish to change one or more of the other "$db_*" parameters.   You may also wish to change the names of the priorities, severities,   operating systems and platforms for your installation. However, you can   always change these after installation has finished; if you then re-run   checksetup.pl, the changes will get picked up.     _________________________________________________________________2.2.2. Database Server   This section deals with configuring your database server for use with   Bugzilla. Currently, MySQL (Section 2.2.2.2) and PostgreSQL (Section   2.2.2.3) are available.     _________________________________________________________________2.2.2.1. Bugzilla Database Schema   The Bugzilla database schema is available at Ravenbrook. This very valuable   tool can generate a written description of the Bugzilla database schema for   any version of Bugzilla. It can also generate a diff between two versions to   help someone see what has changed.     _________________________________________________________________2.2.2.2. MySQL   Caution   MySQL's default configuration is very insecure. Section 4.2 has some good   information for improving your installation's security.     _________________________________________________________________2.2.2.2.1. Allow large attachments   By default, MySQL will only accept packets up to 64Kb in size. If you want   to have attachments larger than this, you will need to modify your   /etc/my.cnf as below.  [mysqld]  # Allow packets up to 1M  max_allowed_packet=1M   There is also a parameter in Bugzilla called 'maxattachmentsize' (default =   1000 Kb) that controls the maximum allowable attachment size. Attachments   larger than either the 'max_allowed_packet' or 'maxattachmentsize' value   will not be accepted by Bugzilla.   Note   This does not affect Big Files, attachments that are stored directly on disk   instead of in the database. Their maximum size is controlled using the   'maxlocalattachment' parameter.     _________________________________________________________________2.2.2.2.2. Allow small words in full-text indexes   By default, words must be at least four characters in length in order to be   indexed by MySQL's full-text indexes. This causes a lot of Bugzilla specific   words to be missed, including "cc", "ftp" and "uri".   MySQL can be configured to index those words by setting the ft_min_word_len   param to the minimum size of the words to index. This can be done by   modifying the /etc/my.cnf according to the example below:  [mysqld]  # Allow small words in full-text indexes  ft_min_word_len=2   Rebuilding the indexes can be done based on documentation found at   http://www.mysql.com/doc/en/Fulltext_Fine-tuning.html.     _________________________________________________________________2.2.2.2.3. Add a user to MySQL   You need to add a new MySQL user for Bugzilla to use. (It's not safe to have   Bugzilla use the MySQL root account.) The following instructions assume the   defaults in localconfig; if you changed those, you need to modify the SQL   command appropriately. You will need the $db_pass password you set in   localconfig in Section 2.2.1.   We use an SQL GRANT command to create a "bugs" user. This also restricts the   "bugs"user to operations within a database called "bugs", and only allows   the account to connect from "localhost". Modify it to reflect your setup if   you will be connecting from another machine or as a different user.   Run the mysql command-line client and enter:  mysql> GRANT SELECT, INSERT,           UPDATE, DELETE, INDEX, ALTER, CREATE, LOCK TABLES,           CREATE TEMPORARY TABLES, DROP, REFERENCES ON bugs.*           TO bugs@localhost IDENTIFIED BY '$db_pass';           mysql> FLUSH PRIVILEGES;     _________________________________________________________________2.2.2.2.4. Permit attachments table to grow beyond 4GB   By default, MySQL will limit the size of a table to 4GB. This limit is   present even if the underlying filesystem has no such limit. To set a higher   limit, follow these instructions.   After you have completed the rest of the installation (or at least the   database setup parts), you should run the MySQL command-line client and   enter the following, replacing $bugs_db with your Bugzilla database name   (bugs by default):            mysql> use $bugs_db            mysql> ALTER TABLE attachments            AVG_ROW_LENGTH=1000000, MAX_ROWS=20000;   The above command will change the limit to 20GB. Mysql will have to make a   temporary copy of your entire table to do this. Ideally, you should do this   when your attachments table is still small.   Note   This does not affect Big Files, attachments that are stored directly on disk   instead of in the database.     _________________________________________________________________2.2.2.3. PostgreSQL2.2.2.3.1. Add a User to PostgreSQL   You need to add a new user to PostgreSQL for the Bugzilla application to use   when accessing the database. The following instructions assume the defaults   in localconfig; if you changed those, you need to modify the commands   appropriately. You will need the $db_pass password you set in localconfig in   Section 2.2.1.   On most systems, to create the user in PostgreSQL, you will need to login as   the root user, and then    bash# su - postgres   As the postgres user, you then need to create a new user:    bash$ createuser -U postgres -dAP bugs   When asked for a password, provide the password which will be set as   $db_pass in localconfig. The created user will have the ability to create   databases and will not be able to create new users.     _________________________________________________________________2.2.2.3.2. Configure PostgreSQL   Now, you will need to edit pg_hba.conf which is usually located in   /var/lib/pgsql/data/. In this file, you will need to add a new line to it as   follows:   host all bugs 127.0.0.1 255.255.255.255 md5   This means that for TCP/IP (host) connections, allow connections from   '127.0.0.1' to 'all' databases on this server from the 'bugs' user, and use   password authentication (md5) for that user.   Now, you will need to restart PostgreSQL, but you will need to fully stop   and start the server rather than just restarting due to the possibility of a   change to postgresql.conf. After the server has restarted, you will need to   edit localconfig, finding the $db_driver variable and setting it to Pg and   changing the password in $db_pass to the one you picked previously, while   setting up the account.     _________________________________________________________________2.2.3. checksetup.pl   Next, rerun checksetup.pl. It reconfirms that all the modules are present,   and notices the altered localconfig file, which it assumes you have edited   to your satisfaction. It compiles the UI templates, connects to the database   using the 'bugs' user you created and the password you defined, and creates   the 'bugs' database and the tables therein.   After that, it asks for details of an administrator account. Bugzilla can   have multiple administrators - you can create more later - but it needs one   to start off with. Enter the email address of an administrator, his or her   full name, and a suitable Bugzilla password.   checksetup.pl will then finish. You may rerun checksetup.pl at any time if   you wish.     _________________________________________________________________2.2.4. Web server   Configure your web server according to the instructions in the appropriate   section. (If it makes a difference in your choice, the Bugzilla Team   recommends Apache.) To check whether your web server is correctly   configured, try to access testagent.cgi from your web server. If "OK" is   displayed, then your configuration is successful. Regardless of which web   server you are using, however, ensure that sensitive information is not   remotely available by properly applying the access controls in Section   4.3.1. You can run testserver.pl to check if your web server serves Bugzilla   files as expected.     _________________________________________________________________2.2.4.1. Bugzilla using Apache   You have two options for running Bugzilla under Apache - mod_cgi (the   default) and mod_perl (new in Bugzilla 2.23)     _________________________________________________________________2.2.4.1.1. Apache httpd with mod_cgi   To configure your Apache web server to work with Bugzilla while using   mod_cgi, do the following:    1. Load httpd.conf in your editor. In Fedora and Red Hat Linux, this file       is found in /etc/httpd/conf.    2. Apache uses <Directory> directives to permit fine-grained permission       setting. Add the following lines to a directive that applies to the       location of your Bugzilla installation. (If such a section does not       exist, you'll want to add one.) In this example, Bugzilla has been       installed at /var/www/html/bugzilla.    <Directory /var/www/html/bugzilla>    AddHandler cgi-script .cgi    Options +Indexes +ExecCGI    DirectoryIndex index.cgi    AllowOverride Limit    </Directory>       These instructions: allow apache to run .cgi files found within the       bugzilla directory; instructs the server to look for a file called       index.cgi if someone only types the directory name into the browser; and       allows Bugzilla's .htaccess files to override global permissions.   Note   It is possible to make these changes globally, or to the directive   controlling Bugzilla's parent directory (e.g. <Directory /var/www/html/>).   Such changes would also apply to the Bugzilla directory... but they would   also apply to many other places where they may or may not be appropriate. In   most cases, including this one, it is better to be as restrictive as   possible when granting extra access.    3. checksetup.pl can set tighter permissions on Bugzilla's files and       directories if it knows what group the web server runs as. Find the       Group line in httpd.conf, place the value found there in the       $webservergroup variable in localconfig, then rerun checksetup.pl.    4. Optional: If Bugzilla does not actually reside in the webspace       directory, but instead has been symbolically linked there, you will need       to add the following to the Options line of the Bugzilla <Directory>       directive (the same one as in the step above):    +FollowSymLinks       Without this directive, Apache will not follow symbolic links to places       outside its own directory structure, and you will be unable to run       Bugzilla.     _________________________________________________________________2.2.4.1.2. Apache httpd with mod_perl   Some configuration is required to make Bugzilla work with Apache and   mod_perl    1. Load httpd.conf in your editor. In Fedora and Red Hat Linux, this file       is found in /etc/httpd/conf.    2. Add the following information to your httpd.conf file, substituting       where appropriate with your own local paths.   Note   This should be used instead of the <Directory> block shown above. This   should also be above any other mod_perl directives within the httpd.conf and   must be specified in the order as below.