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. 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. 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. I just can't seem to find any guidelines for configuring settings.py properly to use the Sites framework. Jay P. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
