Thanks. But afterwards, with the second model, how can you integrate it for a webpage to work?
Imagine a webpage that uses several distinct applications, each one with different templates, media,... In the webserver you will still have only one template subdirectory and one media subdirectory. How will you integrate all this? Thanks, G On 7/31/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > Guillermo Fernandez Castellanos wrote: > > Hi, > > > of course ,the second model is better,the first one is too much > confused > > I've seen this subject several times in the mailing lists without > > being able to find a definite/useful answer in the mailing list. > > > > I'm going to have a server with several domain names serve a few > > applications (blog, photo gallery,...). But I'm a bit at a loss when > > dealing with how to organize the different files. > > > > In Django there's a separation between templates, media, applications, > > the sites urls.py,... The question is, what is the > > suggested/official/best practices way of managing a server with > > several sites? Same for keeping an svn tree. > > > > Do you organize it like: > > /templates/site1 > > /site2 > > /media/site1 > > /site2 > > /urls/site1 > > /site2 > > /apps/app1 > > /app2 > > /app3 > > > > Or more like: > > /site1/templates > > /media > > /urls.py > > /site2/templates > > /media > > /urls.py > > > > Or maybe another way? > > > > Same for svn (maybe for svn it makes more sense the second model...). > > > > Thanks a lot, > > > > G > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
