Re: Django with MySQL DB for multitenancy

You are right, you may do the routing with nginx but will you have many isntances of django this way. You are also right that you should need to create a database router yourself taking in account whatever is needed to decide which database to use. You could for example use the domain from the req

Re: Django with MySQL DB for multitenancy

Hi, I'm not the expert on that, but since no-one else is replying I'll throw my ideas anyway. One solution that does get rid of the docker containers but doesn't otherwise achieve very much is to continue routing from nginx. For one client nginx can be connecting to the :8001 backend, for another

Re: Django with MySQL DB for multitenancy

I basically want to get rid of all the docker containers for each client, and just have a single application with many client (as the tenant) and mysql databases for each tenant. Just like the way django_tenant_schemas is wor

Re: Django with MySQL DB for multitenancy

Hi, I don't understand what the problem is. You have a setup that works. What exactly do you want? You want to run many distinct instances of the application on the same server? And you want to get rid of docker? Antonis Christofides http://djangodeployment.com On 2016-12-09 17:13, Peter Edache

Django with MySQL DB for multitenancy

Hello guys, we are currently looking for a way to migrate our previous django application to a full multi-tenant application, currently the way we are handling our client is by giving each client a docker container and using nginx to do the routing, through sub-domain mapping. But after resea