Skip to content

Commit e2dd34c

Browse files
committed
[#2131] Furthering the excellent permissions changes made by @sprain
1 parent 455670f commit e2dd34c

File tree

1 file changed

+12
-14
lines changed

1 file changed

+12
-14
lines changed

book/installation.rst

Lines changed: 12 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -118,30 +118,28 @@ If there are any issues, correct them now before moving on.
118118
a UNIX system, if your web server user is different from your command
119119
line user, you can run the following commands just once in your project
120120
to ensure that permissions will be setup properly.
121-
122-
Note that not all web servers run as the user ``www-data`` as in the examples
123-
below. You have to check which user the web server is being run as and put it
124-
in for ``www-data``. This can be done by checking your process list to see
125-
which user is running your web server processes.
126-
127-
Depending on your system this may easily be accomplished with one of the
128-
follwing commands:
129-
121+
122+
**Note that not all web servers run as the user** ``www-data`` as in the examples
123+
below. Instead, check which user *your* web server is being run as and
124+
use it place of ``www-data``.
125+
126+
On a UNIX system, this can be done with one of the following commands:
127+
130128
.. code-block:: bash
131129
132130
$ ps aux | grep httpd
133-
131+
134132
or
135-
133+
136134
.. code-block:: bash
137-
135+
138136
$ ps aux | grep apache
139-
140137
141138
**1. Using ACL on a system that supports chmod +a**
142139

143140
Many systems allow you to use the ``chmod +a`` command. Try this first,
144-
and if you get an error - try the next method:
141+
and if you get an error - try the next method. Be sure to replace ``www-data``
142+
with your web server user on the first ``chmod`` command:
145143

146144
.. code-block:: bash
147145

0 commit comments

Comments
 (0)