TEXT   32

Mac OS X

Guest on 3rd August 2022 01:46:08 AM

  1. Mac OS X
  2. ********
  3.  
  4. Note: The Bugzilla team has very little Mac expertise and we've not
  5.   been able to do a successful install of the latest version. We got
  6.   close, though. If you've managed it, tell us how and we can update
  7.   these docs!
  8.  
  9.  
  10. Install Packages
  11. ================
  12.  
  13. OS X 10.7 provides Perl 5.12 and Apache 2.2. Install the following
  14. additional packages:
  15.  
  16. * git: Download an installer from the git website.
  17.  
  18. * MySQL: Download an installer from the MySQL website.
  19.  
  20.  
  21. Bugzilla
  22. ========
  23.  
  24. The best way to get Bugzilla is to check it out from git:
  25.  
  26. **git clone --branch release-X.X-stable
  27. https://github.com/bugzilla/bugzilla**
  28.  
  29. Run the above command in your home directory, replacing "X.X" with the
  30. 2-digit version number of the stable release of Bugzilla that you want
  31. - e.g. "4.4". This will place Bugzilla in the directory
  32. "$HOME/bugzilla".
  33.  
  34. If that's not possible, you can download a tarball of Bugzilla.
  35.  
  36.  
  37. Additional System Libraries
  38. ===========================
  39.  
  40. Apple does not include the GD library with Mac OS X. Bugzilla needs
  41. this if you want to display bug graphs, and you need to install it
  42. before you try installing the GD Perl module.
  43.  
  44. You can use MacPorts, Homebrew or Fink, all of which can install
  45. common Unix programs on Mac OS X.
  46.  
  47. If you don't have one of the above installed already, pick one and
  48. follow the instructions for setting it up. Then, use it to install the
  49. "gd2" package (MacPorts/Fink) or the "gd" package (Brew).
  50.  
  51. The package manager may prompt you to install a number of
  52. dependencies; you will need to agree to this.
  53.  
  54. Note: To prevent creating conflicts with the software that Apple
  55.   installs by default, Fink creates its own directory tree at "/sw"
  56.   where it installs most of the software that it installs. This means
  57.   your libraries and headers will be at "/sw/lib" and "/sw/include"
  58.   instead of "/usr/lib" and "/usr/include". When the Perl module
  59.   config script for the GD module asks where your "libgd" is, be sure
  60.   to tell it "/sw/lib".
  61.  
  62.  
  63. Perl Modules
  64. ============
  65.  
  66. Bugzilla requires a number of Perl modules. On Mac OS X, the easiest
  67. thing to do is to install local copies (rather than system-wide
  68. copies) of any ones that you don't already have. However, if you do
  69. want to install them system-wide, run the below commands as root with
  70. the **--global** option.
  71.  
  72. To check whether you have all the required modules and what is still
  73. missing, run:
  74.  
  75. **perl checksetup.pl --check-modules**
  76.  
  77. You can run this command as many times as necessary.
  78.  
  79. Install all missing modules locally like this:
  80.  
  81. **perl install-module.pl --all**
  82.  
  83.  
  84. Web Server
  85. ==========
  86.  
  87. Any web server that is capable of running CGI scripts can be made to
  88. work. We have specific configuration instructions for the following:
  89.  
  90. * Apache
  91.  
  92. You'll need to create a symbolic link so the webserver can see
  93. Bugzilla:
  94.  
  95. **cd /Library/WebServer/Documents**
  96.  
  97. **sudo ln -s $HOME/bugzilla bugzilla**
  98.  
  99. In System Preferences --> Sharing, enable the Web Sharing checkbox to
  100. start Apache.
  101.  
  102.  
  103. Database Engine
  104. ===============
  105.  
  106. Bugzilla supports MySQL, PostgreSQL, Oracle and SQLite as database
  107. servers. You only require one of these systems to make use of
  108. Bugzilla. MySQL is most commonly used on Mac OS X. (In fact, we have
  109. no reports of anyone using anything else.) Configure your server
  110. according to the instructions below:
  111.  
  112. * MySQL
  113.  
  114. * PostgreSQL
  115.  
  116. * Oracle
  117.  
  118. * SQLite
  119.  
  120.  
  121. localconfig
  122. ===========
  123.  
  124. You should now change into the Bugzilla directory and run
  125. "checksetup.pl", without any parameters:
  126.  
  127. **perl checksetup.pl**
  128.  
  129. "checksetup.pl" will write out a file called "localconfig". This file
  130. contains the default settings for a number of Bugzilla parameters, the
  131. most important of which are the group your web server runs as, and
  132. information on how to connect to your database.
  133.  
  134. Load this file in your editor. You will need to check/change
  135. "$db_driver" and "$db_pass", which are respectively the type of the
  136. database you are using and the password for the "bugs" database user
  137. you have created. "$db_driver" can be either "mysql", "Pg"
  138. (PostgreSQL), "Oracle" or "Sqlite". All values are case sensitive.
  139.  
  140. Set the value of "$webservergroup" to the group your web server runs
  141. as.
  142.  
  143. * Fedora/Red Hat: "apache"
  144.  
  145. * Debian/Ubuntu: "www-data"
  146.  
  147. * Mac OS X: "_www"
  148.  
  149. * Windows: ignore this setting; it does nothing
  150.  
  151. The other options in the "localconfig" file are documented by their
  152. accompanying comments. If you have a non-standard database setup, you
  153. may need to change one or more of the other "$db_*" parameters.
  154.  
  155. Note: If you are using Oracle, "$db_name" should be set to the SID
  156.   name of your database (e.g. "XE" if you are using Oracle XE).
  157.  
  158.  
  159. checksetup.pl
  160. =============
  161.  
  162. Next, run "checksetup.pl" an additional time:
  163.  
  164. **perl checksetup.pl**
  165.  
  166. It reconfirms that all the modules are present, and notices the
  167. altered localconfig file, which it assumes you have edited to your
  168. satisfaction. It compiles the UI templates, connects to the database
  169. using the "bugs" user you created and the password you defined, and
  170. creates the "bugs" database and the tables therein.
  171.  
  172. After that, it asks for details of an administrator account. Bugzilla
  173. can have multiple administrators - you can create more later - but it
  174. needs one to start off with. Enter the email address of an
  175. administrator, his or her full name, and a suitable Bugzilla password.
  176.  
  177. "checksetup.pl" will then finish. You may rerun "checksetup.pl" at any
  178. time if you wish.
  179.  
  180.  
  181. Success
  182. =======
  183.  
  184. Your Bugzilla should now be working. Check by running:
  185.  
  186. **perl testserver.pl http://<your-bugzilla-server>/**
  187.  
  188. If that passes, access "http://<your-bugzilla-server>/" in your
  189. browser - you should see the Bugzilla front page. Of course, if you
  190. installed Bugzilla in a subdirectory, make sure that's in the URL.
  191.  
  192. Next, do the Essential Post-Installation Configuration.
  193.  
  194. ======================================================================
  195.  
  196. This documentation undoubtedly has bugs; if you find some, please file
  197. them here.

Raw Paste


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