docs: Don't mention 'default_project' in deployment guide

The deployment guide currently suggests using the 'default_project'
fixture when deploying a production installation of Patchwork. While one
_could_ use this, it's generally unnecessary given that most people care
about their own projects and not Patchwork.

Resolve this by simply removing any references. The references are
retained for the development installation guide, as they're likely
useful here.

Signed-off-by: Stephen Finucane <stephen@that.guru>

diff --git a/docs/deployment/installation.rst b/docs/deployment/installation.rst
index 6993f26e57c6caa790552291ca606521179d2ca6..16cb41fb7fadfa1f222e651275797c6196257db7 100644 (file)
--- a/docs/deployment/installation.rst
+++ b/docs/deployment/installation.rst
@@ -317,13 +317,13 @@ files:
 .. code-block:: shell
 
    $ python3 manage.py migrate
-   $ python3 manage.py loaddata default_tags default_states default_projects
    $ sudo python3 manage.py collectstatic
+   $ python3 manage.py loaddata default_tags default_states
 
 .. note::
 
-   The above ``default_tags``,``default_states``, and ``default_projects`` are
-   just that: defaults. You can modify these to fit your own requirements.
+   The above ``default_tags`` and ``default_states`` fixtures above are just
+   that: defaults. You can modify these to fit your own requirements.
 
 Finally, it may be helpful to start the development server quickly to ensure
 you can see *something*. For this to function, you will need to add the