3.4. Mac OS X¶
The Bugzilla team has very little Mac expertise and we've not been able to do a successful install of the latest version. We got close, though. If you've managed it, tell us how and we can update these docs!
3.4.1. Install Packages¶
OS X 10.7 provides Perl 5.12 and Apache 2.2. Install the following additional packages:
The best way to get Bugzilla is to check it out from git:
git clone --branch release-X.X-stable https://github.com/bugzilla/bugzilla
Run the above command in your home directory, replacing "X.X" with the 2-digit
version number of the stable release of Bugzilla that you want - e.g. "4.4".
This will place Bugzilla in the directory
If that's not possible, you can download a tarball of Bugzilla.
3.4.3. Additional System Libraries¶
Apple does not include the GD library with Mac OS X. Bugzilla needs this if you want to display bug graphs, and you need to install it before you try installing the GD Perl module.
If you don't have one of the above installed already, pick one and follow the
instructions for setting it up. Then, use it to install the
(MacPorts/Fink) or the
gd package (Brew).
The package manager may prompt you to install a number of dependencies; you will need to agree to this.
To prevent creating conflicts with the software that Apple
installs by default, Fink creates its own directory tree at
where it installs most of
the software that it installs. This means your libraries and headers
will be at
/usr/include. When the
Perl module config script for the GD module asks where your
is, be sure to tell it
3.4.4. Perl Modules¶
Bugzilla requires a number of Perl modules. Generally, the best way to install these is with the cpanm command.
Generally, the best way to install these is with
cpanm --installdeps -l local .
If you want a more full-featured Bugzilla:
cpanm --installdeps -l local --with-all-features --without-feature oracle --without-feature mysql --without-feature pg
If you don't have
cpanm installed, you can
download it from cpanmin.us.
3.4.5. Web Server¶
Any web server that is capable of running CGI scripts can be made to work. We have specific configuration instructions for the following:
You'll need to create a symbolic link so the webserver can see Bugzilla:
sudo ln -s $HOME/bugzilla bugzilla
In System Preferences --> Sharing, enable the Web Sharing checkbox to start Apache.
3.4.6. Database Engine¶
Bugzilla supports MySQL, PostgreSQL, Oracle and SQLite as database servers. You only require one of these systems to make use of Bugzilla. MySQL is most commonly used on Mac OS X. (In fact, we have no reports of anyone using anything else.) Configure your server according to the instructions below:
You should now change into the Bugzilla directory and run
checksetup.pl, without any parameters:
checksetup.pl will write out a file called
This file contains the default settings for a number of
Bugzilla parameters, the most important of which are the group your web
server runs as, and information on how to connect to your database.
Load this file in your editor. You will need to check/change
$db_pass, which are respectively the type of the database you are
using and the password for the
bugs database user you have created.
$db_driver can be either
Sqlite. All values are case sensitive.
Set the value of
$webservergroup to the group your web server runs as.
- Fedora/Red Hat:
- Mac OS X:
- Windows: ignore this setting; it does nothing
The other options in the
localconfig file are documented by their
accompanying comments. If you have a non-standard database setup, you may
need to change one or more of the other
If you are using Oracle,
$db_name should be set to
the SID name of your database (e.g.
XE if you are using Oracle XE).
checksetup.pl an additional time:
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
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.
Your Bugzilla should now be working. Check by running:
perl testserver.pl http://<your-bugzilla-server>/
If that passes, access
http://<your-bugzilla-server>/ in your browser -
you should see the Bugzilla front page. Of course, if you installed Bugzilla
in a subdirectory, make sure that's in the URL.
Next, do the Essential Post-Installation Configuration.