Ideal Folder Structure of MVC framework [closed]

Question

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.

Closed 7 years ago.

I would like to ask what is the ideal folder structure for a MVC framework that should be able to support multiple installations. For example, I install xyz framework and i run two or more sites based on this single installation of xyz framework rather than installing the framework for each site.

This is probably done in Codeigniter too but i don't know much about CodeIgniter, so i need your suggestions. I know some of you might even have better idea than what is done by CodeIgniter, so please share.

Answer 1

This is, a generalized example, of my MVC library structure. Nothing fancy, i wanted to keep it simple.

Library
    - Configuration
    - Modules (Database adapters etc)
    - Core (Abstract controllers, routing functionality etc)
Application
    - Model
    - View
    - Controllers
    - Helpers

The benefits with this structure is that the library is not (which it shouldnt) dependent of the library. That means that you can copy the library for use with other projects.