I've recently been looking at the docs, trying to grok the Sites framework.
What is the recommended way of laying out the filesystem when doing
multiple sites? Let's say I have two sites, "foo" and "bar", with URLs
foo.com and bar.com.
Would you put all the files for both sites into one Django project, or
would you give each its own project?
When I say "both sites into one Django project", I mean something like this:
myproject/
foo/
settings.py
urls.py
app1/
app2/
templates/
bar/
settings.py
urls.py
app3/
app4/
templates/
Then the vhost configurations for each site can point to the
individual settings files, the sites can potentially share
applications, and they can easily share models.
I suppose the same could be done by having each site in its own
project (after all, these are just Python packages and modules), but
it seems like I wouldn't want shared models crossing project domains
like that. That's just a purely conceptual idea though.
And that's the other thing, models. Say I have a model "Baz", that is
used by app1 in "foo", and by app3 in "bar". Where would I define it?
I would guess I can arbitrarily choose to define it in either
foo.models or bar.models. Or would it make any sense to define it
somewhere else entirely, so it's not directly coupled to only one app?
Thanks,
Jay P.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
