unee-t / bugzilla Goto Github PK

Based on the BZ documentation, the BZ API Fields should include the information of whether a field is enabled for cases or not...

In BZ v5.0.6 this does NOT seem to be the case.

See unee-t/frontend#805 for more information on the consequences of that for Unee-T

https://github.com/bugzilla/harmony/blob/master/httpd/httpd.conf

What I did:

• Create a new fresh AWS instance (Ubuntu Server 16.04 LTS (HVM), SSD Volume Type - ami-6f198a0c)
• install dockers
  sudo apt install docker.io
• install docker compose
  sudo apt install docker-compose
• Install make:
  sudo apt-get install make
• Configure docker:
  sudo usermod -aG docker $USER
  sudo systemctl start docker
• Log out and log back in
• check that all is OK:
  docker ps
  No error there
• Clone the latest repo
  git clone https://github.com/unee-t/bugzilla.git
• Move to the bz folder
  cd ~/bugzilla
• Try to build it
  make up

This does not work as intended
Error message:

ubuntu@ip-172-31-20-119:~/bugzilla$ make up
make: *** No rule to make target 'up'. Stop.

Did I do anything wrong?
Any idea how to fix that?

The favicon is located in the folder
/images
We need to include this in the customization as this needs to be changed from a vanilla BZ installation too.

This is not strictly a bug for this repo, but it's related to how we can deploy this in AWS.
I'm putting this here so we can better follow up on this.

@kaihendry, in order for the prod environment to work it needs to be configured to be able to send emails.

We need to document how it can be done and test that before we can go live with the production envo.
As of today the prod environment throws an error each time it needs to send an email.

This is a show stopper: we can't go live if we don't understand how this can be done.

bugzilla/bugzilla@ea2b640
https://github.com/unee-t/bugzilla-customisation/blob/master/docker-compose.yml#L29
https://bugzilla.mozilla.org/show_bug.cgi?id=1467006
MariaDB/mariadb-docker#174

Since we need/want to use Aurora to benefit from AWS Lambda notification capabilities, we need to make sure that the docker uses Aurora at build time.

This is a Major update and will make Unee-T more dependent on AWS (until further releases) but this seems to be the most efficient and scalable way forward at this point.

We probably also need to update the README wherever relevant.

@kaihendry feel free to add/comment if necessary

Would appear Apache is logging twice. https://github.com/unee-t/bugzilla/blob/master/bugzilla.conf#L20

When we do an installation with dockers, the cat .env variable are the same each time.

It would be nice to be able to generate the passwords randomly.
To access the passwords we can always do
cat .env
To get the password variables for the environment we just built

For several reasons, we would like to use AWS Aurora as the DB engine for the BZFE.

See unee-t/bz-database#8,
issue #9
and unee-t/frontend#13

We need to understand how we can have the table 'bugs_fulltext' converted from MyISAM to INNODb AND make sure that the BZ checksetup.pl script is NOT reverting the changes back each time it's run