summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorbugreport%peshkin.net <>2004-03-22 07:41:17 +0100
committerbugreport%peshkin.net <>2004-03-22 07:41:17 +0100
commit5ed084cc7d9d77cf96c8f49d93e021d74774c4bb (patch)
treecb7146b0e804bd77ab17de4284bb4ee44f575217
parentd1619a459e23394ebf8d72503fd01a8df5c28517 (diff)
downloadbugzilla-5ed084cc7d9d77cf96c8f49d93e021d74774c4bb.tar.gz
bugzilla-5ed084cc7d9d77cf96c8f49d93e021d74774c4bb.tar.xz
Bug 207039: Add documentation explaining how to install bugzilla under regular user privileges (re-checkin)
r=vlad, a=justdave
-rw-r--r--docs/xml/installation.xml8
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/xml/installation.xml b/docs/xml/installation.xml
index 0c709e029..33c26b201 100644
--- a/docs/xml/installation.xml
+++ b/docs/xml/installation.xml
@@ -1,5 +1,5 @@
<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"> -->
-<!-- $Id: installation.xml,v 1.66 2004/03/21 22:09:31 bugreport%peshkin.net Exp $ -->
+<!-- $Id: installation.xml,v 1.67 2004/03/21 22:41:17 bugreport%peshkin.net Exp $ -->
<chapter id="installing-bugzilla">
<title>Installing Bugzilla</title>
@@ -1595,7 +1595,7 @@ $smtp->quit;
<section>
<title>Introduction</title>
- <para>If you are running an *NIX OS as non-root, either due
+ <para>If you are running a *NIX OS as non-root, either due
to lack of access (web hosts, for example) or for security
reasons, this will detail how to install Bugzilla on such
a setup. It is recommended that you read through the
@@ -1862,7 +1862,7 @@ pid-file=/home/foo/mymysql/the.pid
<title>HTTP Server</title>
<para>Ideally, this also needs to be installed as root and
- running under a special webserver account. As long as
+ run under a special webserver account. As long as
the web server will allow the running of *.cgi files outside of a
cgi-bin, and a way of denying web access to certain files (such as a
.htaccess file), you should be good in this department.</para>
@@ -1943,7 +1943,7 @@ pid-file=/home/foo/mymysql/the.pid
<warning>
<para>The one option in <filename>localconfig</filename> you
might have problems with is the web server group. If you can't
- successful browse to the <filename>index.cgi</filename> (like
+ successfully browse to the <filename>index.cgi</filename> (like
a Forbidden error), you may have to relax your permissions,
and blank out the web server group. Of course, this may pose
as a security risk. Having a properly jailed shell and/or