From: Stephen Finucane Date: Thu, 18 May 2017 13:42:19 +0000 (+0100) Subject: docs: Don't mention 'default_project' in deployment guide X-Git-Tag: v2.0.0-rc2~22 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=1b47510ae8e3f43aa7bf3b80fbbb29aea9b88afa;p=thirdparty%2Fpatchwork.git 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 --- diff --git a/docs/deployment/installation.rst b/docs/deployment/installation.rst index 6993f26e..16cb41fb 100644 --- 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