Re: Project when using multiple sites

[Ian Holsman]

On 02/08/2006, at 10:29 PM, Jay Parlar wrote: On 8/2/06, Ian Holsman <[EMAIL PROTECTED]> wrote: and obviously not all the sites are identical (they have different hostnames and possibly different things enabled for that site) .. they go in the site_NN directory. I usually have a group of 'shared' URL roots..  url_app_X.py and of course i have a set of N settings files which are hostname specific.  setting_hostname.py so far this structure has worked for the 6-7 sites I run, and 3-4 projects I am using. Do you use the Sites framework for any of this though? That's the thing I'm having a conceptual problem with. yes. I have several 'sites' in a single DB. but at the moment i'm questioning the usefulness of it, due to it having a common 'user' table, and the cost of adding a new database is quite small. but to your question ;-) More specifically, I'm not quite sure how to configure a project to use the Sites framework. Namely, what to do with settings.py files? I know to give each site unique SITE_ID values. But then it *seems* that all the settings.py files have to have the same SECRET_KEY, or I get a "User tampered with session cookie" error. change the cookie name. for example car-chatter.com has SESSION_COOKIE_NAME ='revhead' and med-chatter.com has SESSION_COOKIE_NAME ='ithurtswhenidothis' both sites have different SECRET_KEY and SITE_ID's. Also, how are we supposed to associate sites that we add through the admin to a SITE_ID? The sites in the Admin don't actually show the SITE_ID they're associated with. look at the URL in the admin tool eg http://car-chatter.com /admin/sites/site/6/ that is the SITE_ID (6). i also have a line      r'/usr/local/src/magik/itscales/site_%d_templates' % SITE_ID, in my TEMPLATE_DIRS which makes a bit easier ;-) I just can't seem to find any guidelines for configuring settings.py properly to use the Sites framework. 4 steps. 1. copy the settings.py to new-settings.py 2. add a site_id via the admin tool 3.  configure new-settings.py, changing the cookie name, SITE_ID, and SECRET_KEY as above 4. clone your httpd.conf with so that it uses new-settings.py on your host. regards Ian Jay P. -- Ian Holsman [EMAIL PROTECTED] join http://gyspsyjobs.com the marketplace for django developers  --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---