Skip to content

Commit

Permalink
Update settings.py location and do not reference DATABASE_NAME, which…
Browse files Browse the repository at this point in the history
… is not in settings.py anymore.
  • Loading branch information
mpdaugherty committed Oct 25, 2012
1 parent 3dfa18e commit 679db00
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions chapter03.rst
Expand Up @@ -360,9 +360,9 @@ does Django do behind the scenes?

It all starts with the *settings file*. When you run
``python manage.py runserver``, the script looks for a file called
``settings.py`` in the same directory as ``manage.py``. This file contains all
``settings.py`` in the inner ``mysite`` directory. This file contains all
sorts of configuration for this particular Django project, all in uppercase:
``TEMPLATE_DIRS``, ``DATABASE_NAME``, etc. The most important setting is called
``TEMPLATE_DIRS``, ``DATABASES``, etc. The most important setting is called
``ROOT_URLCONF``. ``ROOT_URLCONF`` tells Django which Python module should be
used as the URLconf for this Web site.

Expand Down

1 comment on commit 679db00

@peeter3
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For django 1.3.1, settings,py and manage.py are in the same directory. Has it changed since?

Please sign in to comment.