Django y su forma extraña de lidiar con css, js e imágenes

Extraer de Surviving django.contrib.staticfiles (or: how to manage static files with django) :

How to override a static file

Imagine that you want to override /static_url/admin/css/base.css. The first thing you have to do is find its location:

>>> ./manage.py findstatic admin/css/base.css
Found 'admin/css/base.css' here:
  /home/jpic/env/lib/python2.7/site-packages/django/contrib/admin/static/admin/css/base.css

Then, copy it to your /srv/project/static_dir/, which you have added to settings.STATICFILES_DIRS (see previous paragraph), for example:

mkdir -p /srv/project/static_dir/admin/css/
cp /home/jpic/env/lib/python2.7/site-packages/django/contrib/admin/static/admin/css/base.css /srv/project/static_dir/admin/css

Your copy would reside in /srv/project/static_dir/admin/css/base.css. For collectstatic, /srv/project/static_dir/ tiene prioridad sobre django/contrib/admin/static, because of the default order of settings.STATICFILES_FINDERS.

¿Entonces collectstatic obtendrá /srv/project/static_url/admin/css/base.css to be a copy of your override /srv/project/static_dir/admin/css/base.css, instead of the original django/contrib/admin/static/admin/css/base.css

Dónde:

• /static_url/ is STATIC_URL
• /srv/project/static_root/ is STATIC_ROOT
• /srv/project/static_dir/ is a dir listed in STATICFILES_DIRS

Also, you will have to run collectstatic when you deploy.

Yes I wrote this article because I think it can help a lot of persons who would rather read a short article that only covers most common use cases rather than the complete documentation - ie. deadlines.

Espero que esto ayude.

In the development environment you can serve these files via Django (django.contrib.archivos estáticos). In production, you can simply serve your static files via your webserver like Apache (you could configure an Alias for your static files directory).

Yes, you can ignore all of the in-built Django machinery for static, media, etc. Although it really is convenient once you get a handle on it.

But if you do want to ignore it, and serve up the assets in your assets folder, there are two separate environments to consider: development y production.

In development, you can have the Django runserver serve static assets just by telling it where to find them. Take a look at the docs aquí to see an example of using the Django serve() función para hacer esto.

In production, you just need to configure your server to look in that directory for anything starting with /assets/ en el capítulo respecto a la URL camino.