I like this explanation very much, thank You. I didn't know, that
STATICFILES_DIRS is the source for the DEV-server serving static files.
That is a big help. Now, as a consequence, in my project I've renamed the
empty static folder (where the collects go into) to "static_collected",
that means:
I'm running manage.py runserver (on the dev environment) the only
reason I'm asking this is because I'm quite certain on my previous
installs (Django 1.3) it worked fine
On Apr 23, 12:54 pm, Philip Mountifield
wrote:
> It depends how you are running. When using "manage.py runserver" it
> serves t
It depends how you are running. When using "manage.py runserver" it
serves the static files for you, without even needing to collect them
IIRC. But when deploying, you have to run "manage.py collectstatic" and
Django collects all the files from the other locations for you and puts
them in STATI
But then shouldn't I expect the files to be served from the
STATIC_ROOT as well ?
On Apr 23, 12:38 pm, Philip Mountifield
wrote:
> There is a slight difference:
>
> * STATIC_ROOT is where you would like the files to be collected to
> when you run "manage.py collectstatic" and should be emp
There is a slight difference:
* STATIC_ROOT is where you would like the files to be collected to
when you run "manage.py collectstatic" and should be empty to begin
with.
* STATICFILES_DIRS is where the actual files are located and they will
be automagically servered under the developm
5 matches
Mail list logo
