FreeBSD6.1 quick installation and configuration Bugzilla2.22

Author：Eve Cole Update Time：2009-06-04 16:45:05

Friends who have developed large-scale projects must have come into contact with these types of tools: requirements management, code and version control, and bug tracking tools. The more common requirements management tool is ClearQuest. The most commonly used code and version control tools are VSS and CVS. The most famous bug tracking tool must be bugzilla.

Bugzilla is a free and excellent bug tracking tool provided by the Mozilla team. It is completely web-based, easy to install, easy to run, and can be stored using a MySQL database or Ldap. The system is very flexible and has strong configurability. , and can automatically send emails for notifications and reminders, produce flexible and convenient various reports and graphics, and also support standard XML import and export.

As a product defect recording and tracking tool, it can establish a complete bug tracking system for you. At the same time, because there are many similarities in processes and features between requirements management and bug tracking, Bugzilla can also be used to implement entry-level Requirements management, a requirement is like a bug. The entire process from proposal to reception, processing, feedback, and verification can be reflected and processed in bugzilla, and can be mapped to products and related personnel just like bugs. Michael used to work at Yahoo At that time, the company used bugzilla as a platform for requirements and bug management, which felt very convenient and practical.

I won’t go into more details about the features of Bugzilla here. Michael mainly talks about how to quickly install and configure Bugzilla in the FreeBSD6.1 environment to provide requirements and bug management support for your project.

The installation mentioned by Michael here has a premise, that is, it is assumed that FreeBSD6.1 has been successfully installed and ports configured on your system, and the installation and configuration of Apache, Perl, and MySQL have been completed through ports. Regarding the installation of FreeBSD6.1 , the configuration of ports and the installation and configuration of Apache, Perl and MySQL will not be discussed here. There is quite a lot of related information.

Below is Michael's Bugzilla installation process.

#cd /usr/ports/devel/bugzilla
#more ./distinfo (Look at the version information, you can see something similar to the following)

MD5 (bugzilla-2.22.tar.gz) = bbf2f1ec5607978d39855df104231973
SHA256 (bugzilla-2.22.tar.gz) = 9d7e2144cd8499430c802ef5267dd2237aaec401546e5b9476db4f9ca19ebd4d
SIZE (bugzilla-2.22.tar.gz) = 1956898
Indicates that the current version of bugzilla in ports is version 2.22. This version is basically the latest version of the currently officially released stable version.

#make config (configure initial configuration options, the following are my choices)
[X] MYSQL MySQL database support
[ ] PGSQL PostgreSQL database support
[X] CHARTING_MODULES Bug charting support
[ ] GRAPHVIZ Use GraphViz
[X] EMAIL_GATEWAY Use email gateway
[X] EXPORT_IMPORT Import/export bugs (via XML)
[ ] CONTRIB Install user-contributed scripts
[ ] LDAP Enable LDAP support
Select support for MySQL database, graphical reports, email, XML import and export

#make install clean

The above completes the basic installation. Next, you need to make some settings before you can finally use it.

SetupMySQL

We need to set up the MySQL database to store Bugzilla data. You can set it up through the command line or a web management tool like phpmyadmin. Below we use the MySQL command line to complete the setting.

#mysql -hlocalhost -uroot -p
Enter password:xxxxxx
mysql> create database <dbname>;
mysql> GRANT SELECT, INSERT,
UPDATE, DELETE, INDEX, ALTER, CREATE, LOCK TABLES,
CREATE TEMPORARY TABLES, DROP, REFERENCES ON <dbname>.*
TO <dbuser>@localhost IDENTIFIED BY '<dbpass>';
mysql> FLUSH PRIVILEGES;
mysql> exit;

The above completes the creation of a database for bugzilla to use on the local MySQL (Here’s Replace with the database name you want to use) and add the user and password , the user is interested in Has all permissions.
Here, Michael uses is bugzilla, and Both are bugzilla
In addition, in order for MySQL to support bugzilla's larger attachment storage, the default settings of MySQL need to be modified. The attachments supported by bugzilla by default are up to 1M. The modification method is as follows:

#vi /etc/my.cnf
Add the following line to the [mysqld] section
max_allowed_packet=1M

Then restart MySQL.

SetupApache

If your system is FreeBSD6.1 and the ports have been updated to the latest version, then the Apache installed through ports should be Apache2.2.3 version, and its ServerRoot directory should be in /usr/local/www/apache22, but Bugzilla passes through ports After installation, the bugzilla web directory will be installed under /usr/local/www/data/bugzilla. You can adjust it according to your own preferences. You can move the bugzilla directory to /usr/local/www/apache22/data/bugzilla. Next, you can also re-modify Apache's httpd.conf file, change the ServerRoot to /usr/local/www, and update other settings related to /usr/local/www/apache22 in httpd.conf. I used the latter method because many other apache-related web applications installed through ports will default to /usr/local/www. For example, cvsweb defaults to the /usr/local/www/cgi-bin directory. For the convenience of installing other applications in the future, I chose to modify the configuration of apache, and it is very simple to modify. The general related settings are as follows:

#cp -r /usr/local/www/apache22/* /usr/local/www/
#vi /usr/local/etc/apache22/httpd.conf
Modify the part related to /usr/local/www/apache22 in the file to /usr/local/www. There are about three or four places.

Then add the following content to the httpd.conf file
<Directory /usr/local/www/data/bugzilla>
AddHandler cgi-script .cgi
Options +Indexes +ExecCGI
DirectoryIndex index.cgi
AllowOverride Limit
</Directory>
This content sets the bugzilla directory to execute cgi files, because bugzilla is written in perl.

This completes the configuration of Apache and restarts the apache service.

Bugzilla final settings

Completing the settings of MySQL and Apache is basically 99% complete. The last step is bugzilla's own configuration part. The configuration process is also very simple. The steps are as follows:

#cd /usr/local/www/data/bugzilla
#./checksetup.pl
This is the first time you execute this script and the configuration file localconfig will be automatically created for you.
#vi ./localconfig
Modify the database name, user name, and password inside to the values you set when you created it before, save and exit.
#./checksetup.pl
This command will allow bugzilla to complete the creation and setting of various tables in the database. At the same time, you will be asked to enter the email address and password of the bugzilla administrator. Just follow the prompts and enter it. The process is very simple.

At this point, the entire installation of bugzilla is over. Enter http://yourserverip/bugzilla/index.cgi in the browser. Haha, did you see the cute bugs? Of course, you can also configure apache's VirtualHost to use an independent domain name to access your bugzilla. For example, the bugzilla I configured can access http://bugzilla.toplee.com through the following domain name. You can test it!

Since the Chinese localization of bugzilla currently only supports version 2.20, the version 2.22 we installed has not yet had the Chinese version, so we cannot enjoy the Chinese interface for the time being. Please wait. For more details, please follow http://www.bugzilla.org for the latest news. !