Scalable architecture

[eluser]eoinmcg[/eluser]
hi txomin,

rather than write a controller for each school i would:
1. have a single code base so when you make changes, fix bugs and add features it is available to all sites
2. symlink each site back to the master codebase
(the above assumes you're hosting them all on the same server and something like virtual hosts)

as for databases, i'd say keeping them separate will probably save headaches in the future.

of course, there are other approaches. i used something like what i describe above recently with a bash script to create each new site 'instance' and database and it saved alot of headaches.

good luck!