No, the development server recognizes new static files on the fly. However, it
can sometimes fail; for example, if you have removed the directory and recreate
it. So restarting it is a good idea when you are trying to debug it.
Antonis Christofides
http://djangodeployment.com
On 2017-07-06 19:20
Hi Alex
> On development, I run the django-admin runserver, which AFAIK should take
> care of the static path.
Did you restart the development server. I think the static files are
collected at startup and newly added files are not recognized on the fly.
Andreas
--
Kurs 10 IT-Consulting
> Am 06.07.2017 um 11:44 schrieb Melvyn Sopacua :
>
> On development, you're running a webserver that doesn't know the `/static`
> url or failed to run `python manage.py collectstatic`.
On development, I run the django-admin runserver, which AFAIK should take care
of the static path.
I have che
[Assuming the weird opening quote comma replacement is formatting, not actual
code]
On Thursday 06 July 2017 11:03:19 Axel Rau wrote:
> Why do I get
> [06/Jul/2017 09:54:20] "GET /static/css/bootstrap.min.css HTTP/1.1"
> 404 1676 on development server, while on production server, it works.
Hi,
I can’t find the answer to this simple question:
Why do I get
[06/Jul/2017 09:54:20] "GET /static/css/bootstrap.min.css HTTP/1.1" 404
1676
on development server, while on production server, it works.
In production, I have
On development, I have tried this and this:
5 matches
Mail list logo
