Download the latest Stable Release from the Bugzilla website into your home directory, and extract it to some web-accessible location:

  $ wget http://ftp.mozilla.org/pub/mozilla.org/webtools/bugzilla-STABLE.tar.gz
  $ cd ~/www
  $ tar -xzf ~/bugzilla-STABLE.tar.gz
  $ ln -s bugzilla-* bugzilla
  $ rm -f ~/bugzilla-STABLE.tar.gz

Execute checksetup.pl for the first time:

  $ cd bugzilla
  $ perl checksetup.pl

Now you need to create a database. In this example we will use MySQL, but other database drivers are also available. To create a database, you can use either the shell interface or the web interface. You can choose any name for the database.

  $ csoftadm
  csoftadm> db mysql add mybugzilla
  Created database `mybugzilla'.

You also need to create a MySQL user and grant it the following rights over the database.

  csoftadm> db mysql useradd mybugzilla
  allow access from host? localhost (enter)
  password for mybugzilla? (password)
  password for mybugzilla? (again) (password)
  csoftadm> db mysql grant
  database? mybugzilla
  database user? mybugzilla
  rights to grant? (...) select,insert,update,delete,index,alter,
                         create,lock tables,create temporary tables,
			 drop,references
  Granted select,... rights to mybugzilla user.

The Bugzilla installation guide recommends specific MySQL parameters at this point. You can assume that your server's MySQL daemon is already using them.

Open up localconfig in your favorite text editor. You need to change at least the following settings:

• $webservergroup -> users
• $db_name -> (name of your database)
• $db_user -> (name of your database user)
• $db_pass -> (password of your database user)

Now execute checksetup.pl again. The script will now initialize the database and compile the templates. It will also ask you for an administrator e-mail address and password.

  $ perl checksetup.pl

As of version 3.0, the checksetup.pl script expects that you are using your own web server. If you have an Advanced-Konto or Corporate-Konto package and this is the case, you can ignore the following step. Otherwise, you need to fix permissions using:

  $ for i in docs graphs images js skins; do \
      find $i -type d -exec chmod o+rx {} \; ; \
    done
  $ for i in jpg gif css js png html rdf xul; do \
      find . -name \*.$i -exec chmod o+r {} \; ; \
    done
  $ find . -name .htaccess -exec chmod o+r {} \;
  $ chmod o+rx .

It is a good idea at this point to execute ./testserver.pl from your shell to test that Bugzilla is working as expected.

You can now browse to the Bugzilla URL and login using the e-mail address and password you previously entered in checksetup.pl. Bugzilla will guide you through the remaining configuration steps.

We recommend using an https:// URL for logging into the administrator account. If you do not own a SSL certificate, you can always generate one yourself (see the SSL guide). Don't forget to set Bugzilla's sslbase parameter accordingly.

If you want graphical statistics, you need to add a cron entry for statistics collection:

  $ crontab -e

Add the following, substituting for your actual Bugzilla installation directory:

  5 0 * * * (cd $HOME/www/your-bugzilla && ./collectstats.pl)

Bugzilla's automatic whining system is useful for periodically reminding developers about bugs left in the NEW or REOPENED state. To use this feature, add an additional entry to your crontab:

  55 0 * * * (cd $HOME/www/your-bugzilla && ./whineatnews.pl)

Users can also configure Bugzilla to execute saved searched at specific times and e-mailing back the results to them. This requires the whine.pl script:

  */15 * * * * (cd $HOME/www/your-bugzilla && ./whine.pl)

• Bugzilla home
• Bugzilla 3.0 documentation