TEXT   28
Essential Post Installation Configuration
Guest on 19th March 2023 11:22:36 AM

  1. Essential Post-Installation Configuration
  2. *****************************************
  4. Bugzilla is configured in the Administration Parameters. Log in with
  5. the administrator account you defined in the last "checksetup.pl" run,
  6. then click Administration in the header, and then Parameters. You will
  7. see the different parameter sections down the left hand side of the
  8. page.
  11. Parameters
  12. ==========
  14. There are a few parameters which it is very important to define (or
  15. explicitly decide not to change).
  17. The first set of these are in the Required Settings section.
  19. * urlbase: this is the URL by which people should access Bugzilla's
  20.   front page.
  22. * sslbase: if you have configured SSL on your Bugzilla server, this
  23.   is the SSL URL by which people should access Bugzilla's front page.
  25. * ssl_redirect: Set this if you want everyone to be redirected to
  26.   use the SSL version. Recommended if you have set up SSL.
  28. * cookiepath: Bugzilla uses cookies to remember who each user is. In
  29.   order to set those cookies in the correct scope, you may need to set
  30.   a cookiepath. If your Bugzilla is at the root of your domain, you
  31.   don't need to change the default value.
  33. You may want to put your email address in the maintainer parameter in
  34. the General section. This will then let people know who to contact if
  35. they see problems or hit errors.
  37. If you don't want just anyone able to read your Bugzilla, set the
  38. requirelogin parameter in the User Authentication section, and change
  39. or clear the createemailregexp parameter.
  42. Email
  43. =====
  45. Bugzilla requires the ability to set up email. You have a number of
  46. choices here. The simplest is to get Gmail or some other email
  47. provider to do the work for you, but you can also hand the mail off to
  48. a local email server, or run one yourself on the Bugzilla machine.
  50. Bugzilla's approach to email is configured in the Email section of the
  51. Parameters.
  54. Use Another Mail Server
  55. -----------------------
  57. This section corresponds to choosing a mail_delivery_method of SMTP.
  59. This method passes the email off to an existing mail server. Your
  60. organization may well already have one running for their internal
  61. email, and may prefer to use it for confidentiality reasons. If so,
  62. you need the following information about it:
  64. * The domain name of the server (Parameter: smtpserver)
  66. * The username and password to use (Parameters: smtp_username and
  67.   smtp_password)
  69. * Whether the server uses SSL (Parameter: smtp_ssl)
  71. * The address you should be sending mail 'From' (Parameter:
  72.   mailfrom)
  74. If your organization does not run its own mail server, you can use the
  75. services of one of any number of popular email providers.
  78. Gmail
  79. ~~~~~
  81. Visit https://gmail.com and create a new Gmail account for your
  82. Bugzilla to use. Then, set the following parameter values in the
  83. "Email" section:
  85. * mail_delivery_method: SMTP
  87. * mailfrom: new_gmail_address@gmail.com
  89. * smtpserver: smtp.gmail.com:465
  91. * smtp_username: new_gmail_address@gmail.com
  93. * smtp_password: new_gmail_password
  95. * smtp_ssl: On
  98. Run Your Own Mail Server
  99. ------------------------
  101. This section corresponds to choosing a mail_delivery_method of
  102. Sendmail.
  104. Unless you know what you are doing, and can deal with the possible
  105. problems of spam, bounces and blacklists, it is probably unwise to set
  106. up your own mail server just for Bugzilla. However, if you wish to do
  107. so, some guidance follows.
  109. On Linux, any Sendmail-compatible MTA (Mail Transfer Agent) will
  110. suffice.  Sendmail, Postfix, qmail and Exim are examples of common
  111. MTAs. Sendmail is the original Unix MTA, but the others are easier to
  112. configure, and therefore many people replace Sendmail with Postfix or
  113. Exim. They are drop-in replacements, so Bugzilla will not distinguish
  114. between them.
  116. If you are using Sendmail, version 8.7 or higher is required. If you
  117. are using a Sendmail-compatible MTA, it must be compatible with at
  118. least version 8.7 of Sendmail.
  120. On Mac OS X 10.3 and later, Postfix is used as the built-in email
  121. server.  Postfix provides an executable that mimics sendmail enough to
  122. satisfy Bugzilla.
  124. On Windows, if you find yourself unable to use Bugzilla's built-in
  125. SMTP support (e.g. because the necessary Perl modules are not
  126. available), you can use Sendmail with a little application called
  127. sendmail.exe, which provides sendmail-compatible calling conventions
  128. and encapsulates the SMTP communication to another mail server. Like
  129. Bugzilla, **sendmail.exe** can be configured to log SMTP communication
  130. to a file in case of problems.
  132. Detailed information on configuring an MTA is outside the scope of
  133. this document. Consult the manual for the specific MTA you choose for
  134. detailed installation instructions. Each of these programs will have
  135. their own configuration files where you must configure certain
  136. parameters to ensure that the mail is delivered properly. They are
  137. implemented as services, and you should ensure that the MTA is in the
  138. auto-start list of services for the machine.
  140. If a simple mail sent with the command-line "mail" program succeeds,
  141. then Bugzilla should also be fine.
  144. Troubleshooting
  145. ---------------
  147. If you are having trouble, check that any configured SMTP server can
  148. be reached from your Bugzilla server and that any given authentication
  149. credentials are valid. If these things seem correct and your mails are
  150. still not sending, check if your OS uses SELinux or AppArmor. Either
  151. of these may prevent your web server from sending email. The SELinux
  152. boolean httpd_can_sendmail may need to be set to True.
  154. If all those things don't help, activate the smtp_debug parameter and
  155. check your webserver logs.
  158. Products, Components, Versions and Milestones
  159. =============================================
  161. Bugs in Bugzilla are categorised into Products and, inside those
  162. Products, Components (and, optionally, if you turn on the
  163. useclassifications parameter, Classifications as a level above
  164. Products).
  166. Bugzilla comes with a single Product, called "TestProduct", which
  167. contains a single component, imaginatively called "TestComponent". You
  168. will want to create your own Products and their Components. It's OK to
  169. have just one Component inside a Product. Products have Versions
  170. (which represents the version of the software in which a bug was
  171. found) and Target Milestones (which represent the future version of
  172. the product in which the bug is hopefully to be fixed - or, for
  173. RESOLVED bugs, was fixed. You may also want to add some of those.
  175. Once you've created your own, you will want to delete TestProduct
  176. (which will delete TestComponent automatically). Note that if you've
  177. filed a bug in TestProduct to try Bugzilla out, you'll need to move it
  178. elsewhere before it's possible to delete TestProduct.
  180. Now, you may want to do some of the Optional Post-Install
  181. Configuration.
  183. ======================================================================
  185. This documentation undoubtedly has bugs; if you find some, please file
  186. them here.

Raw Paste

Login or Register to edit or fork this paste. It's free.