I would not recommend each account having their own database, unless sheer size is a problem (ie each account's data is gigabytes) - it is certainly simpler, and I would imagine more efficient, to use a single database.
Logging in via a subdomain / main domain is really an apache issue - it shouldn't really affect your app (other than perhaps a skin change when accessed from a subdomain). As for customisation per account, I guess this depends on what needs to be done. I would hope that simply a unique CSS file per account would be enough, which should be fairly simple (just a check in your layout file to include a custom CSS). If you really need to change functionality and output per account... I would still hope that you could have account attribute fields, and your controllers / views check these attributes as to how exactly to operate. But if you expect quite different functionality for an account, making a new app sounds like a good idea. In our app the login is an Operator, and all data types have an operator_id field. In our AppController beforeFilter we check that an operator is logged in to access any action, and in the AppModel beforeFind all query conditions are modified to limit only to the current operator. This way it's fairly automatic that the logged in operator can only see / interact with their own data (occasionally need some additional checks in each action - ie delete). --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" 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 -~----------~----~----~----~------~----~------~--~---
