Re: Django project for multiple clients

This is what we've done successfully for multiple projects. Django makes it fairly straightforward. -- Ben On Fri, Mar 27, 2015 at 4:37 PM, Gabriel - Iulian Dumbrava < gabriel.dumbr...@gmail.com> wrote: > If your clients are using different subdomains, like client1.webapp.com, > client2.webapp

Re: Django project for multiple clients

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

Re: Django project for multiple clients

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 > application > which is

Re: Django project for multiple clients

This concept is called multi-tenancy. I suggest you have a look at the django-tenant-schema application which isolate each tenant in it's own PostgreSQL schema. You could also build you own solution using a middleware and a database rout

Django project for multiple clients

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 r