(note: these notes will be incorporated into bugzilla documentation after some revisions)
(updated: Fri, May 13 2016 at 10:24 US/Eastern with additions from dkl)
Firstly, we need some system dependencies:
System Dependencies for Debian and Ubuntu users
$ sudo apt-get update $ sudo apt-get install git perl-modules build-essential cpanminus libssl-dev libexpat1-dev
System Dependencies for CentOS users
Bugzilla Code & CPAN Modules
A checkout of bugzilla is required, and everything we do
will be from that directory.
$ git clone https://github.com/bugzilla/bugzilla $ cd bugzilla
Next, we can run checksetup.pl with its fancy new –cpanm flag to install all our dependencies into local directory. Note that we do not need to be root for any of these commands, and nothing (from this point on) needs to be installed to the system.
$ perl checksetup.pl --cpanm
If all goes well, that should complete with a message saying you need to edit localconfig and re-run checksetup. If you’re fine just using SQLite, you do not need to edit localconfig. Just re-run checksetup.pl, as below:
$ perl checksetup.pl
The above will prompt you for an email, username, realname and password. After you provide those details, it will configure the database.
Now we can run a development server, with the following perl command below:
$ perl -Ilocal/lib/perl5 local/bin/plackup -R Bugzilla -R Bugzilla.pm -R templates app.psgi
This will start an http on http://localhost:5000.
Navigate to it, and login using the email/password you used above.
Bugzilla will direct you to set the urlbase – which you can set to to the same “http://localhost:5000” above.
Any changes made to files in Bugzilla and templates will trigger a restart. Currently changes to .cgi files might not be picked up, but that should be solved shortly.
Note that these are draft instructions, I appreciate testing and feedback on them. I will fill the todo items in as time allows, and hopefully we get this into the documentation for the Bugzilla 6.0 release.