From f44bd7dc873d6122d32f4d8619f82429096750cf Mon Sep 17 00:00:00 2001 From: Christopher Allan Webber Date: Thu, 20 Nov 2014 11:36:29 -0600 Subject: [PATCH] Patch by Sturm: explain permissions on media directories in deployment docs This should hopefully reduce the amount that users are confused by their media files not being available. --- docs/source/siteadmin/deploying.rst | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/docs/source/siteadmin/deploying.rst b/docs/source/siteadmin/deploying.rst index d049f8fb..8356f4ba 100644 --- a/docs/source/siteadmin/deploying.rst +++ b/docs/source/siteadmin/deploying.rst @@ -388,6 +388,18 @@ this ``nginx.conf`` file should be modeled on the following:: } } +The first four ``location`` directives instruct Nginx to serve the +static and uploaded files directly rather than through the MediaGoblin +process. This approach is faster and requires less memory. + +.. note:: + + The user who owns the Nginx process, normally ``www-data``, + requires execute permission on the directories ``static``, + ``public``, ``theme_static`` and ``plugin_static`` plus all their + parent directories. This user also requires read permission on all + the files within these directories. This is normally the default. + Now, nginx instance is configured to serve the MediaGoblin application. Perform a quick test to ensure that this configuration works. Restart nginx so it picks up your changes, with a command that @@ -433,3 +445,7 @@ Security Considerations and restart the server, so that it creates a new secret key. All previous sessions will be invalidated. +.. + Local variables: + fill-column: 70 + End: -- 2.25.1