Savy kirjoitti: > > > Hi Djangonauts, > > I am developing a Django project (with a few pluggable apps). > > I want to offer this project as a SaaS (something like 37signals.com). > > i.e: customer1.product1.com , customer2.product2.com etc > > product1 could be the basecamp product2 could be highrise and so on. > > I want to know how the project should be structured for these > products. > > Should there be a single project under which all products will be an > application. ---- OR ---- Should I be making different projects for > all the products. > > Also interms of database.. should all the products look into a single > database or we should have seperate databases for each product. > > I am looking out for the most efficient and scalable way to do this.
I'm not saying this is best and most scalable way but we're doing SaaS Django projects and it's project per customer. And each project will have it's own database (Oracle schema usually) so we can scale up pretty much. -- Jani Tiainen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
