Simplifying the local_settings.py seems to have resolved this problem; I'm
using the defaults for STATIC_ROOT and STATIC_URL that are already in
settings.py, with the configuration for nginx as listed above.
Of course, now I'm getting a different error, but the problem with the
permission
I made some progress on understanding this, but haven't quite gotten past
the problem. One thing I learned was that I mixed up the use of the
STATIC_ROOT and STATIC_URL, but fixing it didn't seem to do much.
Here are what appear to be the relevant configs.
local_settings.py:
STATIC_URL =
I wonder if STATIC_ROOT is the source of your problem. Have you tried
different settings for that, including STATIC_ROOT = /static/ ? I don't
use nginx (I use Apache), but looking at your config, I wonder if the
webserver is looking for static files in a folder that Django appends with
another
I think you're probably right, Ross. I noticed that when we did some
updates to the theme locally and some static files were accidentally
missing, internally the dev server produced a 404 error as evidenced by the
server output. However, on the browser it showed up as a 500 error. I
suspect
Good thought, I had been running collectstatic as part of the fabric
deploy. This time I ran the command by itself.
It correctly copied everything into the location specified by the static
root, so it's putting them where I expected. I'm still not seeing any new
error messages in the ngnix
What happens when you run collectstatic?
If I recall correctly, one of the differences between DEBUG = False and
DEBUG = True is that the former will use static files from Mezzanine's
codebase and the latter will search for static files in your project
folders. The collectstatic command will
