I agree. Anyway, there is a multi-tenant feature that can be enabled at any time. The issue is, is it sufficient?
On Thursday, 15 August 2013 23:18:22 UTC-5, Alex Glaros wrote: > > develop for multi-tenant from the beginning or else you will waste time > re-entering corrected designed data > > is a "group" equivalent to a "team"? > > will team membership stay permanent for each season? > > > > On Thursday, August 15, 2013 2:40:28 PM UTC-7, Carlos Zenteno wrote: >> >> Hi all, >> >> Very new to web2py and I like it so far... >> >> I am going to develop an app where a 'team' representative will sign up >> for an account >> and this will create a team environment where the team players list can >> be entered. >> Each account will have 5 groups on it and the players will be >> moved/assigned to one >> or more groups. >> >> So far I think that each team will have an account of the type: >> my_team.domain.com. >> >> I think this can be achieved with multi-tenants. Please tell me if I am >> in the right track or >> if there is a better way to do this. >> >> Some questions: >> >> - what is the best way to approach this? >> do I develop the application as if it was going to be for a single >> account and then transform it to multi-tenants? >> or do I develop it for multi-tenants from the beginning? >> >> - I want to use postgresql. Do I start with sqlite and then migrate to >> postgresql >> or is it better to start with postgresql from the beginning? >> >> - Is there a place where I can read what are the best practices on >> developing with >> web2py or what are the best ways to do it? >> >> Thanks in advance for your advice >> > -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
