if i have a site under example.com domain with structure: www.example.com - public site - django project "portal" admin.example.com - administration site - django project "admin" shop.example.com - satchmo integration attempt - django project "shop" ... services, rss, and anything else you can think of
1. should i use one project for entire site or break it into projects like in example above? 2. sharing secret key in project - http://www.djangoproject.com/documentation/settings/#secret-key - when i break example.com in more projects, i share database, media settings for all projects but i don't know if i should share secret key? - any advice on what to share between projects and what not? 3. sessions - what would you recommend, any special setup related to sessions that can be applied to this kind of site structure? 4. satchmo comes with admin app configured, so should i leave it under shop.example.com or should i integrate in admin.example.com 5. have anything related to project theory to share? Aljosa --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
