Added 'Where should this code live?' section to tutorial01

git-svn-id: http://code.djangoproject.com/svn/django/trunk@1676 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Adrian Holovaty 2005-12-15 23:44:33 +00:00
parent 6c6feb482a
commit 0c6653cf03
1 changed files with 12 additions and 0 deletions

View File

@ -32,6 +32,18 @@ its setup.py utility. If it's not on your path, you can find it in
``site-packages/django/bin``; consider symlinking to it from some place ``site-packages/django/bin``; consider symlinking to it from some place
on your path, such as /usr/local/bin.) on your path, such as /usr/local/bin.)
.. admonition:: Where should this code live?
If your background is in PHP, you're probably used to putting code under the
Web server's document root (in a place such as ``/var/www``). With Django,
you don't do that. It's not a good idea to put any of this Python code within
your Web server's document root, because it risks the possibility that
people may be able to view your code over the Web. That's not good for
security.
Put your code in some directory **outside** of the document root, such as
``/home/mycode``.
A project is a collection of settings for an instance of Django -- including A project is a collection of settings for an instance of Django -- including
database configuration, Django-specific options and application-specific database configuration, Django-specific options and application-specific
settings. Let's look at what ``startproject`` created:: settings. Let's look at what ``startproject`` created::