DEBUG, which is set to True, causes storing information about queries in memory (which sometimes looks like memory leaking) and display of detailed error pages to user. So you are encouraged to set it to False on your blog, but be prepared - Django's urls configuration is set to browse static data (urls, serving CSS, JS, images and so on) only in DEBUG mode.

This is done just to make sure that you will configure your webserver to serve STATIC_URL (usually /static/), MEDIA_URL (usually /media/) and ADMIN_URL_PREFIX (usually /admin-media/) instead of passing this urls to Django (you really don't want to get them served by Django - this is static files, which do not require to fire up whole python interpreter with Django).

This is whole configuration for nginx webserver, inluding serving of static urls (Django is installed in /usr/local/lib/python2.5/site-packages/django/), where Byteflow itself is server by apache + mod_wsgi:

    upstream apache {
        server 127.0.0.1:90;
    }

    server {
        listen 80;
        server_name piranha.org.ua www.piranha.org.ua;
        root /home/piranha/web/byteflow;
        include /etc/nginx/proxy.conf;

        location / {
            proxy_pass http://apache;
        }
        location /static {
            expires 10d;
        }
        location /media {
            expires 10d;
        }
        location /admin-media {
            alias /usr/local/lib/python2.5/site-packages/django/contrib/admin/media;
            expires 10d;
        }
    }