36955 - Want more information about MySQL setup in the docs

Status: RESOLVED WONTFIX

(Bugzilla :: Documentation, enhancement, P3)

Description

[sshah]

The bugzilla docs are actually pretty good to start with. I think Bugzilla is no
less difficult to get going than any other bug tracking system. So kudos for
what you've got.

The part that I *really* got stuck on was getting MySQL to behave. Although this
technically belongs to MySQL documentation, having it in the Bugzilla docs would
be nice too. Specifically:

o Which parts of MySQL is necessary? At mysql.com, there are many components
that are part of the whole system now. The only necessary parts is the main
package and Perl modules. 

o The current Bugzilla docs warn you in advance that MySQL perms are a pain in
the backside. Given that warning, some additional tips would be great. I spent
half a day trying to figure out why the general perl modules would fail "make
test" -- turns out I never GRANTed myself permission to the database. Since it
think it is fair to say that most first time Bugzilla installers are also first
time MySQL installers, having a more detailed step by step guide on what should
be done to make MySQL work well with Bugzilla would be nice. While the docs that
come with MySQL are complete, they are a bit volumous for folks who are only
interested in getting MySQL to work with Bugzilla.

o This is probably a RedHat 6.1 specific issue. The GD libraries that ship with
it are older and still use GIF by default. rpm -e'ing that package breaks a
bunch of dependancies and I wouldn't be surprised if installing the new GD
library in its place would probably break those packages too. =( So a tip to the
user is if they are not using Bugzilla on a public commercial site, stick with
the older perl modules that work nicely with the GIF-only version of GD that
comes with RH6.1. Yeah, it's a hack. But it's a lot easier than having to do a
bunch of upgrades just to get a new GD in place. As for the perl tools that use
GD, getting older versions of the perl tools is also important. Recommend the
versions mentioned in the docs right now and not newer versions for RedHat 6.1
folk.

If I can think of anything more, I'll add it in later.

-Steve

Comment 1

[mental]

->Bugzilla/Documentation

Comment 2

[rudman]

-->endico. Dawn, I'm lobbing this your way to close out (seems like the
documentation requested isn't obligatory for Bugzilla) or to reassign.

Comment 3

[Dave Miller [:justdave]]

-> default owners

Comment 4

[Dave Miller [:justdave]]

Barnboy changed his email address and opened a new account instead of having the
address changed on his existing one.  Reassigning all docs bugs to his new account.

Comment 5

[Gervase Markham [:gerv]]

[e-mail]: is any of this still relevant? Can you provide answers to
any of your own questions?

Gerv

Comment 6

[Matthew Barnson]

Accepting bug.  Covering the problems of each operating system's libraries &
various versions is not within the scope of the Guide.  However, a brief note to
the effect that some operating systems may run with an outdated copy of GD, and
the Bugzilla administrator should probably use CPAN and compile her own modules
in lieu of using those provided by the vendor if there is a conflict, is
appropriate.

In addition, I should make a note to myself that lengthy sentences, while
occasionally appropriate if used succinctly when there is not a more terse
method of expressing a concept, are best avoided.

<giggle>

Comment 7

[Matthew Barnson]

Just closing this one wontfix.  When we get around to reorganizing the docs,
we'll be tidying up the MySQL instructions anyway.  I want MySQL-specific
directions out of the documentation anyway, except for bare minimums to get an
up and working Bugzilla installation.  Pointers to appropriate MySQL docs for
further details.  The basic strategy should be make the grant tables and whatnot
wide-open on first install, then after one has confirmed a working Bugzilla
install, include instructions for then closing the holes.  Although this
disagrees with the security guru inside of me, it's the best strategy for
getting a first-time user up and running.  Therefore this bug is no longer
relevant...

Comment 8

[Dave Miller [:justdave]]

clearing milestone in INVALID/WONTFIX/DUPLICATE/WORKSFORME so they'll show up as
untriaged if they get reopened.