multi-tenant

Are there common patterns people use for creating multi-tenanted applications using Django. The built in "sites" framework seems like an option. Are there other approaches people have had success with? Using the sites framework goes a long way towards providing a security guarantee to the "tenants", assuming you give each site instance a unique table. On the other hand, it'll be a big hassle if you have a small number of tenants and you'll waste a huge amount of server resources since you'll need at least one server process per customer even if they aren't using the system. If you have a large

I'm looking for working code and ideas from others who have tried to build a multi-tenant Django application using database-level isolation. Update/Solution: I ended solving this in a new opensource project: see django-db-multitenant Goal My goal is to multiplex requests as they come in to a single app server (WSGI frontend like gunicorn), based on the request hostname or request path (for instance, foo.example.com/ sets the Django connection to use database foo , and bar.example.com/ uses database bar ). Precedent I'm aware of a few existing solutions for multi tenancy in Django: django

I'm trying to get a reasonable understanding of how one can build an app on top of ruby/rack (or even more ideally, an existing framework) that manages something equivalent to WordPress. Specifically, with the ability to serve multiple sites from the same code base, each with its own features and configuration. Suppose, for instance: example.com using auth, pages, blog modules forum.example.com -> auth, forum modules api.example.com -> auth, api modules This test case seems to work, including in a production environment: # test.rb class Foo end # config.ru require 'rack' use Rack:

I have a standard DbContext with code like the following: public DbSet<Interest> Interests { get; set; } public DbSet<User> Users { get; set; } I've recently implemented multi-tenancy by creating a TenantContext that contains the following: private readonly DbContext _dbContext; private readonly Tenant _tenant; public TenantContext(Tenant tenant) : base("name=DefaultConnection") { this._tenant = tenant; this._dbContext = new DbContext(); } public IQueryable<User> Users { get { return FilterTenant(_dbContext.Users); } } public IQueryable<Interest> Interests { get { return FilterTenant(

I am building a SAAS application and we are discussing about one database per client vs shared databases. I have read a lot, incluisve some topics here at SO but I have still many doubts. Our plataform should be highly customizable by each client. (they should be able to have custom tables and add custom fields to existing tables). The multiple database aproach seems great in this case. The problem is. should my "users" table be in the master database or in each client database?. A user might have one or more organizations, so it would be present in multiple databases. Also, what about generic

I’m working on a tenant application and i was wondering how i can block tenant access other tenant data. First, let me expose some facts: The app is not free, 100% for sure the malicious user is a client. All the primary keys/identity are integers (Guid solve this problem but we can't change right now). The app use shared database and shared schema. All the tenants are business group wich own several shops. I'm use Forgery... I have some remote data chosen by dropdown and its easy change the id's and acess data from other tenants, if you have a little knowledge you can f*ck other tenants data.