3.5. Installation General Notes
3.5.1. Modifying Your Running System
Bugzilla optimizes database lookups by storing all relatively static + information in the versioncache file, located in the data/ subdirectory + under your installation directory. +
If you make a change to the structural data in your database + (the versions table for example), or to the + "constants" encoded in defparams.pl, you will + need to remove the cached content from the data directory + (by doing a "rm data/versioncache"), or your + changes won't show up. +
That file gets automatically regenerated whenever it's more than an + hour old, so Bugzilla will eventually notice your changes by itself, but + generally you want it to notice right away, so that you can test things. +
3.5.2. Upgrading From Previous Versions
The developers of Bugzilla are constantly adding new tables, columns and + fields. You'll get SQL errors if you just update the code. The strategy + to update is to simply always run the checksetup.pl script whenever + you upgrade your installation of Bugzilla. If you want to see what has + changed, you can read the comments in that file, starting from the end. +
If you are running Bugzilla version 2.8 or lower, and wish to upgrade to + the latest version, please consult the file, "UPGRADING-pre-2.8" in the + Bugzilla root directory after untarring the archive. +
3.5.3. .htaccess files and security
To enhance the security of your Bugzilla installation, + Bugzilla will generate + .htaccess files + which the Apache webserver can use to restrict access to + the bugzilla data files. The checksetup script will + generate the .htaccess files. + +
If you are using an alternate provider of + webdot services for graphing + (as described when viewing + editparams.cgi in your web + browser), you will need to change the ip address in + data/webdot/.htaccess to the ip + address of the webdot server that you are using. + |
If you are using Internet Information Server or other web + server which does not observe .htaccess + conventions, you can disable their creation by editing + localconfig and setting the + $create_htaccess variable to + 0. +
3.5.4. UNIX Installation Instructions History
This document was originally adapted from the Bonsai installation + instructions by Terry Weissman <terry@mozilla.org>. +
The February 25, 1999 re-write of this page was done by Ry4an Brase + <ry4an@ry4an.org>, with some edits by Terry Weissman, Bryce Nesbitt, + Martin Pool, & Dan Mosedale (But don't send bug reports to them; + report them using bugzilla, at http://bugzilla.mozilla.org/enter_bug.cgi , + project Webtools, component Bugzilla). +
This document was heavily modified again Wednesday, March 07 2001 to + reflect changes for Bugzilla 2.12 release by Matthew P. Barnson. The + securing MySQL section should be changed to become standard procedure + for Bugzilla installations. +
Finally, the README in its entirety was marked up in SGML and included into + the Guide on April 24, 2001 by Matt Barnson. Since that time, it's undergone + extensive modification as Bugzilla grew. +
Comments from people using this Guide for the first time are particularly welcome. +