On 25/09/2010 18:32, Tim Sawyer wrote: > On 25/09/10 15:57, craphunter wrote: >> Yes, I have read it, but I don't really get it. What is the meaning of >> it? > > Consider a website that has multiple blogs, all of which are deployed to the > same database. > > Consider that you want each blog to be a separate URL: www.blog1.com, > www.blog2.com, but you only want one database for ease of backing up etc. > > So, you have one codebase, one database, but multiple sites. > > You can achieve this using SITE_ID. www.blog1.com has a settings.py with > SITE_ID = 1. www.blog2.com has a settings.py file with SITE_ID = > 2. In your database, there are two rows in the django_site database table, > with serials 1 and 2. The table that holds the blog entries has > a foreign key to Site, and so identifies which site the blog post appears on. > > At least that's how I used it...hope that helps clarify it a bit! > > Tim.
Hey Tim, the way you used it would mean that you had different settings.py per site/url and thus a project per url as 1 project can only have 1 settings file? Is this correct? Have do you config the admin then so you see both sites in the same admin? Regards, Benedict -- 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.
