On 24 mar, 19:33, Dave A <hikingd...@hotmail.com> wrote: > Hi, > > I'm new to Django -- I'm evaluating open source frameworks in an > attempt to port an existing application to a non-proprietary > platform. > I like Django, but am not sure about how to approach an application > templating function from the current system... > > In short, each registered user of the system has their own copy of one > or more applications. Their copies holds their data, their > configurations, etc. The main web site lets them add/remove > applications, and provides links into each personal application to > view/manage their data. > Each night, a process runs to deploy any code changes to each users > application. > > I'd love to build a similar system in Django, where a user can > register, select applications to use, and have their own personal > data, navigation, and views of their data, while providing my team > with an easy way to create and deploy new applications to the site. > I'm just not sure quite how to approach this... > > If anyone can provide guidance to an appropriate architecture for this > type of function withing a Django platform, it would be greatly > appreciated..
The simplest solution IMHO (assuming *n*x on the server) would be to keep all code (django itself and django apps) in the same place (which saves place and make sure you don't have any outdated code). Then it's just a matter of updating per-user configuration files and db when adding an application, which should be easy to script using Python. Remember that the configuration file is just plain Python code, so you don't necessarily have to hard-code INSTALLED_APPS and the like. So you could have one django instance for managing your users, which applications they use and per-user application settings (the per-user configuration file getting it's data from this instance's database), then one django instance per user. Using mod_wsgi or mod_fcgi, it should be possible to restart one given django instance (when one user adds an app or changes it's settings) without stopping Apache itself. My 2 cents. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
