I was hoping to use Django in a web management UI for a server that I support, where new UIs are added as new applications are installed.
Due to this plugin requirement, I had planned to model that with one large Django project, where each new plugin was a Django application. Unfortunately it would appear that this would not work, as each application potentially needs its own database, and Django only permits a single one to be specified. In Rails I can specify new dbs at the model level to override the default. Is there any way to do this in Django? Surely the requirement for more than one database to drive an entire site's content is present. If not, I could use multiple Django projects, with one project per plugin, but I would still like to share some common code for inclusion tags, templates, etc., to ensure that the pages all have the same look and feel. Is there a recommended way to do this? Thank you for any help that you can offer. Mike --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
