If your clients are using different subdomains, like client1.webapp.com, client2.webapp.com then you can have separate settings file per subdomain and completely isolate the client data, but still use the same virtualenv and codebase. You must also take care of the file upload/access because you also need to isolate it.
joi, 26 martie 2015, 18:23:38 UTC+2, Steven Nash a scris: > > 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/0db98454-b9f4-4ed0-9924-e528d0b11174%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
