Hi,
Second that - don't do one database per user. However you can have one
model use different tables for each account. By way of example, I am
nearly finished a (cake-based) app that allows users to put custom
fields in their forms. Of the various approaches, I chose to set up a
new table for ea
Thanks Grant,
I appreciate your help.
I think you are right in regards to database etc... one database would
be much easier to manage etc
In terms of layout, it will function similar to a cms in that user
should be able to modify template, menu items etc so I guess that
the ability for
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 s
Hi Guys,
we are in the process of planning to develop a web app using cakephp.
I have a few questions and was hoping somebody could provide some
feedback / suggestions.
Ok basically it is intended to be a hosted application where users
will sign up for an account etc...
I guess I want to know
