PageRenderTime 48ms CodeModel.GetById 23ms RepoModel.GetById 0ms app.codeStats 0ms

/docs/faq/usage.txt

https://code.google.com/p/mango-py/
Plain Text | 77 lines | 56 code | 21 blank | 0 comment | 0 complexity | fcdc1e458f4f13c6db5dc4f07616780c MD5 | raw file
Possible License(s): BSD-3-Clause
  1. FAQ: Using Django
  2. =================
  3. Why do I get an error about importing DJANGO_SETTINGS_MODULE?
  4. -------------------------------------------------------------
  5. Make sure that:
  6. * The environment variable DJANGO_SETTINGS_MODULE is set to a
  7. fully-qualified Python module (i.e. "mysite.settings").
  8. * Said module is on ``sys.path`` (``import mysite.settings`` should work).
  9. * The module doesn't contain syntax errors (of course).
  10. * If you're using mod_python but *not* using Django's request handler,
  11. you'll need to work around a mod_python bug related to the use of
  12. ``SetEnv``; before you import anything from Django you'll need to do
  13. the following::
  14. os.environ.update(req.subprocess_env)
  15. (where ``req`` is the mod_python request object).
  16. I can't stand your template language. Do I have to use it?
  17. ----------------------------------------------------------
  18. We happen to think our template engine is the best thing since chunky bacon,
  19. but we recognize that choosing a template language runs close to religion.
  20. There's nothing about Django that requires using the template language, so
  21. if you're attached to ZPT, Cheetah, or whatever, feel free to use those.
  22. Do I have to use your model/database layer?
  23. -------------------------------------------
  24. Nope. Just like the template system, the model/database layer is decoupled from
  25. the rest of the framework.
  26. The one exception is: If you use a different database library, you won't get to
  27. use Django's automatically-generated admin site. That app is coupled to the
  28. Django database layer.
  29. How do I use image and file fields?
  30. -----------------------------------
  31. Using a :class:`~django.db.models.FileField` or an
  32. :class:`~django.db.models.ImageField` in a model takes a few steps:
  33. #. In your settings file, you'll need to define :setting:`MEDIA_ROOT` as
  34. the full path to a directory where you'd like Django to store uploaded
  35. files. (For performance, these files are not stored in the database.)
  36. Define :setting:`MEDIA_URL` as the base public URL of that directory.
  37. Make sure that this directory is writable by the Web server's user
  38. account.
  39. #. Add the :class:`~django.db.models.FileField` or
  40. :class:`~django.db.models.ImageField` to your model, making sure to
  41. define the :attr:`~django.db.models.FileField.upload_to` option to tell
  42. Django to which subdirectory of :setting:`MEDIA_ROOT` it should upload
  43. files.
  44. #. All that will be stored in your database is a path to the file
  45. (relative to :setting:`MEDIA_ROOT`). You'll most likely want to use the
  46. convenience :attr:`~django.core.files.File.url` attribute provided by
  47. Django. For example, if your :class:`~django.db.models.ImageField` is
  48. called ``mug_shot``, you can get the absolute path to your image in a
  49. template with ``{{ object.mug_shot.url }}``.
  50. How do I make a variable available to all my templates?
  51. -------------------------------------------------------
  52. Sometimes your templates just all need the same thing. A common example would
  53. be dynamically-generated menus. At first glance, it seems logical to simply
  54. add a common dictionary to the template context.
  55. The correct solution is to use a ``RequestContext``. Details on how to do this
  56. are here: :ref:`subclassing-context-requestcontext`.