[eluser]Kumar Chetan sharma[/eluser]
Well, I have been trying to build up a CMS solution on top of CI. I once had studied and more or less worked on a multi-tenant or a hosted solution. The idea was to
a) maintain configs for each site/instance - this will take care of site specific db connections and or licenses keys, languages etc
b) maintain assets for each site separately - this will avoid mapping assets to db and then some unnecessary db calls to load those assets
c) maintain a main repo for code that will hold all the modules/features
d) create a base template config that loads a base set of features
e) create a control panel that allows the super admin to alter the configs for each site, this basically meant modifying base template config created in d)
Later on I got to work on an enterprise level project for a large telecom product company, they opted for CI coz its fast. They didn't tinker with base CI installation but some how and cleverly tweaked configs and wrote some libs to achieve a hosted solution. My bad, I lost the code and moreover it was unethical and illegal too to use their code.
Do let me know what are your ideas. :-)