I'll try to be brief... We're just starting to work on replacing an
existing home-grown content management system with one built with
Django. We've got lots of semi-autonomous departments (a small liberal
arts college). All of the content will be in one database. We'll be
building a bunch of apps in one core project that will handle the admin
side of things for everything and everyone. Each department that
chooses to have their pages managed through this CMS will be created as
a project, where each project will have access to whichever apps that
department needs.
My question is about the site ID in each project's settings.py file.
What does that number mean in a situation like ours? I appreciated the
explanation of the difference between an app and a project, but I
haven't been able to figure out how "site ID" ends up factoring into things.
I'm probably making a mountain out of a mole hill, but I'd feel much
better about diving into a large-ish project with a better handle on a
pretty basic concept. What would it mean (in terms of developing with
Django) for me to think of this as *one large site* with lots of
more-or-less free-standing pieces versus *a bunch of sites* that happen
to have an awful lot in common? Or does each project simply need to have
its own site ID?
Dave
X-Google-Language: ENGLISH,ASCII-7-bit
Received: by 10.54.160.18 with SMTP id i18mr156641wre;
Sat, 20 May 2006 16:59:55 -0700 (PDT)
Return-Path: <[EMAIL PROTECTED]>
Received: from carthage.edu (andre1.carthage.edu [198.150.93.70])
by mx.googlegroups.com with ESMTP id v23si510935cwb.2006.05.20.16.59.54;
Sat, 20 May 2006 16:59:55 -0700 (PDT)
Received-SPF: neutral (googlegroups.com: 198.150.93.70 is neither permitted nor
denied by best guess record for domain of [EMAIL PROTECTED])
Received: from [69.81.200.165] (account drobinson HELO [192.168.0.100])
by carthage.edu (CommuniGate Pro SMTP 4.2.10)
with ESMTP id 33339070 for django-users@googlegroups.com; Sat, 20 May 2006
18:59:53 -0500
Message-ID: <[EMAIL PROTECTED]>
Date: Sat, 20 May 2006 18:59:33 -0500
From: David Robinson <[EMAIL PROTECTED]>
User-Agent: Mozilla Thunderbird 1.0.7 (Macintosh/20050923)
X-Accept-Language: en-us, en
Mime-Version: 1.0
Content-Type: text/plain
To: django-users <django-users@googlegroups.com>
Subject: remedial django - what IS a "site" exactly?
I'll try to be brief... We're just starting to work on replacing an
existing home-grown content management system with one built with
Django. We've got lots of semi-autonomous departments (a small liberal
arts college). All of the content will be in one database. We'll be
building a bunch of apps in one core project that will handle the admin
side of things for everything and everyone. Each department that
chooses to have their pages managed through this CMS will be created as
a project, where each project will have access to whichever apps that
department needs.
My question is about the site ID in each project's settings.py file.
What does that number mean in a situation like ours? I appreciated the
explanation of the difference between an app and a project, but I
haven't been able to figure out how "site ID" ends up factoring into things.
I'm probably making a mountain out of a mole hill, but I'd feel much
better about diving into a large-ish project with a better handle on a
pretty basic concept. What would it mean (in terms of developing with
Django) for me to think of this as *one large site* with lots of
more-or-less free-standing pieces versus *a bunch of sites* that happen
to have an awful lot in common? Or does each project simply need to have
its own site ID?
Dave
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
