Serving of static and media files

---------------------------------

Out of the box, project templates will configure ``/static/`` as base URL for

static files, and ``/media/`` as base URL for media.

Root directories for locating static and media files are set-up to point to

parent directory of project (so, one level up from ``manage.py``), in

directories ``assets/static/`` and ``assets/media/``.

As an example, in case you create project in ``~/tmp/``, you would have

structure similar to:

- ``~/tmp/myproject/``

- ``~/tmp/myproject/manage.py``

- Many other files and directories under ``~/tmp/myproject/``

- ``~/tmp/assets/static/``

- ``~/tmp/assets/media/``

This way you can keep the assets (static and media files) outside of the project

code tree.

Working with the project

------------------------

When running ``manage.py`` commands for a project, Django by default expects all

settings to be found within the project's settings module. Specifically, it

expects them all to be present in the ``settings.py`` file.

As mentioned before, when using *Majic Django Templates*, this file is

split-up. When Django attempts to load all settings from the project's

``settings`` module, it will fail (since it will effectively be loading settings

from an empty ``__init__.py`` file).

Therefore, settings file must be explicitly specified for all Django commands,

as well as for running the project. There are two ways to do this.

One way is to pass the ``--settings`` option to every invocation of

``manage.py`` command. For example, in order to run the migrate command for

development environment, you would run::

  ./manage.py migrate --settings myproject.settings.development

The second way, is to make sure that the ``DJANGO_SETTINGS_MODULE`` environment

variable is set-up. Following the previous example, you could do something along