I usually keep it like this (but note, that I've recently switched to git):
myproject.com |-myproject |--app1 |---templatetags |---templates |--app2 |--app3 |--templates |--... |-static Some people tend to keep the actual apps in some other directory (repository) and then symlink to the myproject dir (or change the sys.path to include the dir), since the whole idea behind Django is to have small reusable apps. Matic On Thu, Sep 4, 2008 at 5:10 PM, Robert Dailey <[EMAIL PROTECTED]> wrote: > > Hi, > > First, let me start by explaining what my goals are: > - Have a django project & its apps in version control > - Have all of the templates the apps will use in the same version > control > - Have all static content (images, css, etc) in the same version > control. > > So far, this is the directory structure I've come up with: > > django/ > my_project/ > app1/ > app2/ > templates/ > static/ > images/ > styles/ > > Is this a good structure? Using this structure, I can work on > everything involved in making my website through a single working copy > in Subversion. Do you guys have any better suggestions? My main > concern with the structure I presented above is how I will configure > 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 -~----------~----~----~----~------~----~------~--~---
