|
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
Hôte-Avancé or
Hôte-Corporatif
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.
| 
