Multiple projects, one CI codebase?

[eluser]faulky[/eluser]
[quote author="theprodigy" date="1266306179"]The way I have my setup is:

application
--app1
----config
----controllers
----models
----etc, etc
--app2
----config
----controllers
----models
----etc, etc

system
--171
----codeigniter
----libraries
----database
----etc, etc
--172
----codeigniter
----libraries
----database
----etc, etc


public_html
--site1
----css
----js
----images
----index.php //<----- points to application/app1 and system/171
--site2
----css
----js
----images
----index.php //<----- points to application/app2 and system/171

I split my system folder up into whatever version of codeigniter it is running, that way, I don't have to upgrade legacy systems if I don't want to, just because a patch came out.

I split my application folder up into individual site folders

Each index.php points to it's respective application/[site_name] folder and to system/[version] folder[/quote]

Thanks theprodigy,

Seems like a lot of code duplication, and if you wanted to apply a patch, say for security reasons, you'd have to go back over a fair chunk of code?

I'm really after one CI code base. Having "RTFM"ed the documentation a little further it seems Controllers may be what I'm after.

Therefore, our site structure could look like this:

root
--&gt;system
--&gt;application
----&gt;controllers
------&gt;app1
------&gt;app2
------&gt;app3

Then, extending from your example above, for different client sites:
public_html
--site1
----css
----js
----images
----&gt;app1/index.php //<----- points to application/app1
--site2
----css
----js
----images
----&gt;app2/index.php //<----- points to application/app2

Think that would work?

Thanks again.