From 4294a4f48a5949a181acb033e108a5ea897e1a3c Mon Sep 17 00:00:00 2001 From: "barnboy%trilobyte.net" <> Date: Thu, 26 Apr 2001 08:51:39 +0000 Subject: Added .htaccess files for shadow/, data/, and /. I added related information to the Bugzilla Guide, and tacked in a couple of last-minute additions. Also fixed the annoying "Tip: HINT:" thing. --- docs/html/readme.unix.html | 105 +++++++++++++++++++++++++++++++++++++-------- 1 file changed, 87 insertions(+), 18 deletions(-) (limited to 'docs/html/readme.unix.html') diff --git a/docs/html/readme.unix.html b/docs/html/readme.unix.html index faca430af..23f51096e 100644 --- a/docs/html/readme.unix.html +++ b/docs/html/readme.unix.html @@ -851,7 +851,7 @@ CLASS="TIP" >

Tip: HINT: If you symlink the bugzilla directory into your Apache's +> If you symlink the bugzilla directory into your Apache's HTML heirarchy, you may receive "Forbidden" errors unless you add the "FollowSymLinks" directive to the <Directory> entry for the HTML root. @@ -866,12 +866,45 @@ CLASS="TIP" installation.

Lastly, you'll need to set up a symbolic link from /usr/bonsaitools/bin - to the correct location of your perl executable (probably /usr/bin/perl). +> Lastly, you'll need to set up a symbolic link to /usr/bonsaitools/bin/perl + for the correct location of your perl executable (probably /usr/bin/perl). Otherwise you must hack all the .cgi files to change where they look for perl. To make future upgrades easier, you should use the symlink approach.

Example 2-1. Setting up bonsaitools symlink

Here's how you set up the Perl symlink on Linux to make Bugzilla work. + Your mileage may vary; if you are running on Solaris, you probably need to subsitute + "/usr/local/bin/perl" for "/usr/bin/perl" below; if on certain other UNIX systems, + Perl may live in weird places like "/opt/perl". As root, run these commands: + 
bash# mkdir /usr/bonsaitools
+bash# mkdir /usr/bonsaitools/bin
+bash# ln -s /usr/bin/perl /usr/bosaitools/bin/perl
+
+

+

2.1.2.14. Setting Up the MySQL Database

2.1.2.15. Tweaking "localconfig"

Note: The second time you run checksetup.pl, it is recommended you be the same - user as your web server runs under, and that you be sure you have set the +> The second time you run checksetup.pl, you should become the + user your web server runs as, and that you ensure you have set the "webservergroup" parameter in localconfig to match the web server's group - name, if any. Under some systems, otherwise, checksetup.pl will goof up - your file permissions and make them unreadable to your web server. + name, if any. I believe, for the next release of Bugzilla, this will + be fixed so that Bugzilla supports a "webserveruser" parameter in localconfig + as well. +

Example 2-2. Running checksetup.pl as the web user

Assuming your web server runs as user "apache", and Bugzilla is installed in + "/usr/local/bugzilla", here's one way to run checksetup.pl as the web server user. + As root, for the second run of checksetup.pl, do this: + 
bash# chown -R apache:apache /usr/local/bugzilla
+bash# su - apache
+bash# cd /usr/local/bugzilla
+bash# ./checksetup.pl
+
+

2.1.2.16. Setting Up Maintainers Manuall (Optional)2.1.2.16. Setting Up Maintainers Manually (Optional)

If you want to add someone else to every group by hand, you can do it @@ -1220,7 +1289,7 @@ CLASS="SECTION" >

2.1.2.17. The Whining Cron (Optional)

2.1.2.18. Bug Graphs (Optional)

2.1.2.19. Securing MySQL

2.1.2.20. Installation General Notes

2.1.2.20.1. Modifying Your Running System

2.1.2.20.2. Upgrading From Previous Versions

2.1.2.20.3. UNIX Installation Instructions History