> So to sum it up, 1 admin area, 1 member database (under 1 domain) [snip] > Would something like this be possible in Django? The problem is I'm > not sure what should be a separate App or Project... the goal is to be > able to deploy new "front-end" quickly...so perhaps this could be a > separate project?
Yes, it's certainly doable. I don't usually bother making them separate projects. But they could be done as somewhat separate apps. I do use permissions to control access to views (wrapping in decorators) and show/hide links to the admin tools. So if you're logged in as a user with admin'ish permissions, you can see links to the admin area. If you're not logged in with admin'ish permissions, you can't see the links to the admin area, and even if you try to type in the admin-area URLs, the permission-required decorators will prevent access. -tim --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
