How to run the Bugzilla package?

[rokejulianlockhart (Mr. Beedell, Roke Julian Lockhart (RJLB))]

I’d like to answer serverfault.com/q/125241, so how does one run the bugzilla package? I ask because it doesn’t appear to be as automated as askubuntu.com/posts/62078/timeline#comment_2751486 describes, because:

#!/usr/bin/env sh
run0 dnf5 install --refresh -y bugzilla

…doesn’t appear to be sufficient.

My Environment

• Bugzilla

  Its version is what I’ve cited at bugzilla.redhat.com/show_bug.cgi?id=2436486#c0.

• My OS

  NAME: Fedora Linux
  VARIANT: KDE Plasma Desktop Edition
  VERSION_ID: 43
  

[augenauf (Flo)]

3.2. Linux — Bugzilla 5.2+ documentation

However, the packaged version in Fedora repo is 5.0.6, see bugzilla - Fedora Packages

[barryascott]

Bugzilla used to be difficult to setup and keep going, alternatives where often recomended. Maybe things changed since I last looked, that was a long time ago.

[eseyman (Emmanuel Seyman)]

As Flo said, reading the bugzilla instructions should help you answer your own question.

One prerequisite is to have a empty database setup with a dedicated user and password. You can use a postgresql, mariadb/mysql or sqlite database. For postgresql and mariadb/mysql, these can be on the machine you are running bugzilla on or a remote one.

Going from memory, the steps are:

• dnf install bugzilla httpd “perl(DBD::XXX)” (where XXX is the driver for your database)
• edit /etc/bugzilla/localconfig (you probably only need to edit the database info)
• run /usr/share/bugzilla/checksetup.pl

This should create the tables in your database and populate them with the initial content. The checksetup.pl script will also prompt you for an admin account that it will then create. It will also list the dnf commands you need to install optional Bugzilla features. Review these and install whatever you need.

Once that is done, start httpd (“systemctl start httpd”) and you should be able to visit your bugzilla instance.

[rokejulianlockhart (Mr. Beedell, Roke Julian Lockhart (RJLB))]

Thanks, all. Before I try these steps, does anyone recommend a specific Fedora edition for this? I ask because I want to try this in a VM, first, and something like the lack of packages available via the Server installer, and/or the “immutable” filesystem of Kinoite, appear useful for keeping such a server stable.

[barryascott]

Server is the obvious edition to use for bugzilla as it is a server style app.

[gnwiii (George N. White III)]

@barryascott

Server is the obvious edition to use for bugzilla

Which means many other bugzilla systems will be server, so better chances that any problems you encounter is seen by many other server admins and the likelihood that one of them knows a solution.

[rokejulianlockhart (Mr. Beedell, Roke Julian Lockhart (RJLB))]

@gnwiii

many other bugzilla systems will be server, so better chances that any problems you encounter is seen by many other server admins

Although well-documented, I forgot that Server’s default 15-GiB layout can be painful. Consequently, instead of fighting with default partitioning, I’ll try a normal Edition:

@theprogram

may I ask if you really need ‘server’ It may be easier to learn on Fedora Workstation (Gnome) or a minimal install. You can still bring in any server like functions you require. Server is great for remote deployments as it comes with a nice web-based console.

Especially, because I can always install Cockpit there:

Instructions for installing Cockpit on Silverblue

this is for my homeserver. I already figured it out, I did not install the cockpit-ws package… Correct way of doing it: rpm-ostree install cockpit-system cockpit-ws cockpit-files cockpit-networkmanager cockpit-ostree cockpit-podman cockpit-selinux cockpit-storaged sudo systemctl enable --now cockpit.socket sudo firewall-cmd --add-service=cockpit sudo firewall-cmd --add-service=cockpit --permanent Now it works at localhost:9090 I should not have followed instructions for Core…

[barryascott]

@rokejulianlockhart

Although well-documented, I forgot that Server’s default 15-GiB layout can be painful.

It was easy to override the sizes for my lasty f43 server install.
I would also strongly recommend that you add a specific partition for /var.
It will be into /var that all the data for your services will be going.

On my latest server with a 500GiB SSD I choose 25GiB for / and 150 GiB for /var.
The rest of the space is unallocated in LVM so that I can grow or add partitions as future requirements demand.

So far / is only using 5.7GiB.
I have nfs, samba, home assistant, grafana, prometheus, dovecot installed and running.