All geek questions in one place

Ideal MVC structure folder structure

I would like to ask what is the ideal folder structure for an MVC structure that should 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 a framework for each site.

This is probably done in Codeigniter, but I know little about CodeIgniter, so I need your suggestions. I know that some of you may even imagine better than what CodeIgniter has done, so please share.

+3
source share
1 answer

This is a generic example of my MVC library structure. Nothing unusual, I wanted to keep it simple.

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

The advantages of this structure are that the library is not (which should not) be library dependent. This means that you can copy the library for use with other projects.

+2
source

Source: https://habr.com/ru/post/1723843/

More articles:


All Articles