On Mar 24, 12:53 pm, Tim Shaffer <timster...@gmail.com> wrote: > No, it would just be one instance of the project with 20 different > configuration files.
There is the single instance of the code files on disk, but there would be multiple instances of the loaded application in memory where each instance in memory is configured differently based on which settings file was used for that Python interpreter occurence. You are using 'instance' to mean different things and why the likely confusion. Graham > On Mar 23, 5:29 am, Tom Evans <tevans...@googlemail.com> wrote: > > > > > On Mon, Mar 22, 2010 at 5:53 PM, Tim Shaffer <timster...@gmail.com> 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 django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
