In regards to that, don't forget that settings.py is a code file. I have boilerplate code that goes in my settings.py using the os library to figure out where the settings.py file is located. Since my project structures are always identical relative to their root path, I can use the value of "os.path.dirname(os.path.abspath(__file__))" to dynamically create all of my necessary absolute paths (for templates, media, etc.) regardless of environment. It's still flexible though since I can override any value in settings_local.py if I do need to hardcode a one-off location.
On Sep 4, 9:10 am, Robert Dailey <[EMAIL PROTECTED]> wrote: > Apache2 to handle serving static content. Also, the fact that Django > requires an absolute path for the templates directory makes this more > of a management nightmare. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
