This looks like it could be a good solution. Steve
On Thursday, 26 March 2015 17:02:32 UTC, Simon Charette wrote: > > This concept is called multi-tenancy. > > I suggest you have a look at the django-tenant-schema > <https://github.com/bernardopires/django-tenant-schemas> application > which isolate each tenant in it's own PostgreSQL schema. > > You could also build you own solution using a middleware and a database > router. > > Simon > > Le jeudi 26 mars 2015 12:23:38 UTC-4, Steven Nash a écrit : >> >> We are design a DJango based application to be used my multiple clients. >> Each client will have there own database but share the same code base. >> >> In the past, when I've done something like this, I have configure a >> separate virtual host for each client. >> >> This time we are thinking about using URL routing to select the clients >> database, and creating a small Django Webapp to allow an admin team to >> setup new clients etc. >> >> I'd be interested to hear how others have tackled this, I have Googled >> quite a bit on this topic. >> >> Steve >> > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/e5a35695-999c-4515-acda-82106b51709e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
