Perfect, that's exactly what I needed. Thanks!
Den fre 11 jan. 2019 21:53 skrev Nicolas Pinault <3...@drpi.fr>:
> Please take time to read all the content of this page. :
> https://docs.djangoproject.com/en/dev/howto/static-files/
> You'll understand the difference between DEBUG mode and
Please take time to read all the content of this page. :
https://docs.djangoproject.com/en/dev/howto/static-files/
You'll understand the difference between DEBUG mode and deployement mode
concerning static files.
Le 11/01/2019 à 20:23, Christer Enfors a écrit :
Thanks for your response. I have
Thanks for your response. I have a directory called
/home/enfors/PyVarm/static, that's the one which is served when debug ==
True, and PyVarm is obviously the name of the project. So by your
description, I take it PyVarm is the name of my Mezzanine / Django "app".
But where is the top-level
Hi Christer.
The collectstatic command is a Django concept, not something specific to
Mezzanine. Even though it requires more time, a strong foundation on Django
will make your time with Mezzanine much more productive.
When you use Django's dev server, it will look into the /static directory
I don't understand how the "collectstatic" stuff works. I have a static
directory, and inside it there are files. But if I turn off debugging in
settings.py, then the files inside static/ suddenly give me a 404, meaning
I only get a very bare-bones page with no CSS, no images, etc. But the
