Hello, One approach I take with an application is: Each different "customer" (I am developping a SaaS site) o "company" in Your case, can have an specific domain ( www.company1.com, www.company2.com, ...) then based on domain the application can select an specific database.
Check following artile in the backery; http://bakery.cakephp.org/articles/view/one-core-one-app-multiple-domains That way you can select even more things, such as: "themes", "database", "AC/ACO", modules..." I hope this can help You. Regards. 2009/9/23 WebbedIT <[email protected]> > > Your query is off topic so really needs it's own topic. > > I'm sure you could probably do this, but not sure if it is the right > way to go. > > Why would you separate different companies into different databases? > I would imagine each database would have duplicate tables/models etc. > so simply having a company_id foreignKey within each model would allow > you to pull the relevant data without having to maintain multiple > databases and their connections. > > I have done this with a centrally hosted CMS which drives around 20 > completely different websites from one database, and I am currently > working on a portal/community website for the third sector where any > number of non-profit organisations can manage their own sub-sites. > > Paul. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" 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/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
