On Mon, Apr 14, 2008 at 11:40 AM, James Bennett <[EMAIL PROTECTED]> wrote: > I very rarely have a "project folder". All it is is a place to stick a > settings file and a root URLConf module, both of which are just plain > old Python files which can live anywhere you can import from.
Besides settings and urlconf I often find that I need a few site specific context processors and perhaps connect a signal or two from some stand-alone application, e.g. sending an email when something happens. So my solution is normally to put settings, urlconf and site-specific stuff like this in its own "application", usually named after the site it's running on. This application lives in PYTHONPATH like every other application. I usually organize it like this, 'mysite-trunk' is my top-level "project", 'mysite/python/' is added to the pythonpath: $ ls mysite-trunk/ media/ python/ templates/ environment.sh $ ls mysite-trunk/python/ poll/ registration/ tagging/ mysite/ $ ls mysite-trunk/python/mysite/ __init__.py context_processors.py settings_dev.py settings_prod.py urls.py I have written a few words about it in http://prettyprinted.net/blog/2008/mar/25/developing-django-sites-multiple-branches-part-1/ and http://prettyprinted.net/blog/2008/mar/29/developing-django-sites-multiple-branches-part-2/ -- Steingrim Dovland. Oslo, Norway. This behaviour is by design. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
