Re: On django multi tenancy

Hello, Il 06/08/2014 16:34, Robert Grant ha scritto: Does Ikari do what you want? I'm not saying it should or shouldn't be in Django contrib itself, but at least worth taking a look and seeing if that has any useful ideas. Thanks for sharing, the

Re: On django multi tenancy

Does Ikari do what you want? I'm not saying it should or shouldn't be in Django contrib itself, but at least worth taking a look and seeing if that has any useful ideas. On Wednesday, 30 April 2014 09:37:13 UTC+2, riccardo.magliocchetti wrote: > > Hi

Re: On django multi tenancy

Hi Eduardo, [adding Stephen McDonald to CC] Il 29/04/2014 21:43, Eduardo Rivas ha scritto: Mezzanine, a Django based CMS, has true multi tenancy. I've used it and works great. However, it's clear it's not something that should be in Django's core, for the reasons other have stated. I'm just

Re: On django multi tenancy

Mezzanine, a Django based CMS, has true multi tenancy. I've used it and works great. However, it's clear it's not something that should be in Django's core, for the reasons other have stated. I'm just bringing it up in case OP is still looking for something like this for his projects; not

Re: On django multi tenancy

It's so easy to build an Account or Tenant or Site model of your own, do a little leg work, and you've got a multitenant app with all the custom functionality you need. Getting caught up in trying to use contrib apps and hacking things together turned out to be more work once you pass the

Re: On django multi tenancy

Hello, Il 03/04/2014 09:46, Riccardo Magliocchetti ha scritto: Hello, Il 03/04/2014 00:15, Russell Keith-Magee ha scritto: On Thu, Apr 3, 2014 at 2:20 AM, Riccardo Magliocchetti > wrote: First we already have an

Re: On django multi tenancy

Hello, Il 03/04/2014 00:15, Russell Keith-Magee ha scritto: On Thu, Apr 3, 2014 at 2:20 AM, Riccardo Magliocchetti > wrote: Hi everyone, i'd like to start a discussion about multi tenancy on this list.

Re: On django multi tenancy

On Thu, Apr 3, 2014 at 7:42 AM, wrote: > > Short version - it doesn't matter what pretty name you put on it, a thread >> local is a global variable. We teach first year programmers not to use >> globals, so why would we introduce them to Django as a core framework idea?

Re: On django multi tenancy

On Wed, Apr 2, 2014 at 7:42 PM, wrote: > > Short version - it doesn't matter what pretty name you put on it, a thread >> local is a global variable. We teach first year programmers not to use >> globals, so why would we introduce them to Django as a core framework idea?

Re: On django multi tenancy

> Short version - it doesn't matter what pretty name you put on it, a thread > local is a global variable. We teach first year programmers not to use > globals, so why would we introduce them to Django as a core framework idea? > Aren't database connections thread local in Django? -- You

Re: On django multi tenancy

i tenancy of the type that you're describing. However, it's also a contrib app -- so it's entirely optional, and also replaceable. If you have a specific set of requirements for multi tenancy, then write your own third-party app to implement those changes, and use it. > So to summarize

On django multi tenancy

to the site framework and a dozen lines middleware one could build a basic django multi tenancy site. How can I help to have this in 1.7? thanks in advance, riccardo -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubs