I will certainly look into this as it may give me a lot more control but I don't want to end up with lots of added complexity for the sake of conformity.
On Mar 23, 10:02 am, Bjunix <[email protected]> wrote: > You could also build your own "Sites framework" relying on other > things than settings files. Django's sites framework is not too > complex and if does not fit your need, I would just rebuild it > tailored to your needs. > > On Mar 23, 10:29 am, Tom Evans <[email protected]> wrote: > > > > > On Mon, Mar 22, 2010 at 5:53 PM, Tim Shaffer <[email protected]> wrote: > > > It gives you multiple sites from one codebase with multiple settings > > > files. They are using the same project module. So your project would > > > look like this: > > > > project > > > - app1 > > > - app2 > > > - settings.py > > > - settings_site1.py > > > - settings_site2.py > > > - urls.py > > > > settings.py would contain all the settings like a normal django > > > project, then settings_site1 and settings_site2 could import all those > > > default settings and overwrite just the settings they need to (like > > > SITE_ID and MEDIA_ROOT). > > > That is fascinating, but if you had 20 sites, you would need to run 20 > > instances of the project. -- 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?hl=en.
