Thanks for the tip with more than one db. I will take a look a that. Am 06.11.2012 um 17:17 schrieb bruno desthuilliers:
> There's no one-size-fits-all answer, depends on how the "project" is to be > sold and what it does. Given your description (per-customer settings / > installed apps / static files etc) it looks like the first solution (one > instance per customer) might be a better solution, with possibly a > per-customer database for contents and a shared database for "master data" > (django can use more than one db at once). -- 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.
