Directory Structure

There is no mandatory directory structure in Skeleton. All directory paths are customizable. However, the framework does have default directory names. There is also a recommended directory structure.

You may set the directories for controllers and modules in the A_Controller_Mapper using:

setBaseDir() for the path to the application,
setDefaultDir() for the path to the default module, and
setClassDir() for the path to the controllers.

Typically the base dir will be an absolute path and the module and controllers paths will be relative to it.

Minimal Structure

Assuming that you are using the Front Controller, in its most basic configuration only a 'controllers' directory is set as a default.

controllers/



If you choose to base your action controller classes on one of the Skeleton Action Controllers and use the _load() functionalty, then 'models', 'views', 'templates' and 'helpers' directories are defaults. So a directory structure for a simple application might be:
 
controllers/
helpers/
models/
templates/
views/


Recommended Structures
It is recommended that you put all of the application files in a separate directory. This directory should be either outside of your public HTML directory or protected by webserver configuration. Within this application directory you can have one or multiple sets of MVC directories depending on your needs. 

Simple Single Module Application
You can specify an application directory to contain all of the MVC directories. The default application directoyr is './'.  You specify this directory using the A_Controller_Mapper call with $Mapper->setBasePath('/path/to/app');
/app 
/app/controllers
/app/models
/app/views


Complex Multi-Module Application
You can further organize your application ito module directories by adding a 'module' parameter in the Request. Specify a default module directory the mapper with $Mapper->setDefaultDir('default');
/app
/app/admin/controller
/app/admin/model
/app/admin/view
/app/blog/controller
/app/blog/model
/app/blog/view