Do not suggest to link static files

This can cause troubles, so stay with safer file copies.

Fixes #935
Signed-off-by: Michal Čihař <michal@cihar.com>

docs/admin/deployments.rst

@@ -308,7 +308,7 @@ The update script takes care of the following update steps as described under :r
 * manage.py setupgroups --move
 * manage.py setuplang
 * manage.py rebuild_index --all
-* manage.py collectstatic --noinput --link
+* manage.py collectstatic --noinput
 
 
 Bitnami Weblate stack

docs/admin/install.rst

@@ -720,9 +720,9 @@ Serving static files
     framework and the setup was more complex.
 
 Django needs to collect its static files to a single directory. To do so,
-execute :samp:`./manage.py collectstatic --noinput --link`. This will store
-links to static files into directory specified by ``STATIC_ROOT`` setting 
-(this default to ``static`` directory inside :setting:`DATA_DIR`).
+execute :samp:`./manage.py collectstatic --noinput`. This will copy the static
+files into directory specified by ``STATIC_ROOT`` setting (this default to
+``static`` directory inside :setting:`DATA_DIR`).
 
 It is recommended to serve static files directly by your web server, you should
 use that for following paths:

docs/admin/upgrade.rst

@@ -37,7 +37,7 @@ To collect new static files, run:
 
 .. code-block:: sh
 
-    ./manage.py collectstatic --noinput --link
+    ./manage.py collectstatic --noinput
 
 To upgrade default set of privileges definitions (optional), run: