Michael, Yes true multi-tenancy would be slightly more complex than multi-user, but I think it could be accomplished by having a tenant model which owns an administrator model (in case each tenant may have multiple admins) which then owns users.
Again I'll refer to the Agility tutorial where you have tasks which belong to stories which belong to projects, with top down permissions starting at the projects layer. Think of a similar situation where you have tasks which belong to users, users who belong to tenant, and admins who are superusers who belong to tenants with certain additional permissions. On Oct 20, 11:52 am, Michael Q <[email protected]> wrote: > Thanks Jeremy. > > Please forgive me if I'm misunderstanding you, but I'm talking about where a > "tenant" is a company, who has several users. So the users must be managed > according to the tenant they belong to. Each Tenant gets its own > administrator so they can manage their own users etc etc. > > Then there is the issue of isolating each Tenant's data. There are a range > of solutions to this with various pros & cons. A good compromise is to use > Postgres and do schema partitioning. This can be done in plain vanilla > Rails, but I was wondering whether anyone has gone this route with Hobo. I'm > a beginner and this all seems very daunting. I'd probably have to > subcontract this out. > > M -- You received this message because you are subscribed to the Google Groups "Hobo Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/hobousers?hl=en.
