Defined constants

Constant definitions will be done at the very beginning of an entry script on separated file index.consist.php inside skeleton application. constants are separated for specific cases that you want extend Poirot beside other frameworks and scripts so by include this file whole constant, environment and directory structure could be revealed to other systems.

What Are These Constants?

Constant Name	Description	Could Overrides?
DS	Current system directory separator	No
TIME_REQUEST_MICRO	Micro time script started up	No
PT_DIR_SKELETON	Path address point to skeleton package directory.	No
PT_DIR_CONFIG_INITIAL	Path Address to initial system configurations directory. configuration files inside this directory can be overrides by config load mechanism.	No
PT_DIR_ROOT	Path address meant to be a directory root of projects where we have .env files html public directory and vendor by default.	Yes
PT_DIR_CONFIG	Path Address to where we store additional configuration files to override application or modules default. Default Value: PT_DIR_SKELETON/config/	Yes
PT_DIR_DATA	Path Address to where we meant to store run-time application data. Default Value: PT_DIR_SKELETON/data/	Yes
PT_DIR_TMP	Path Address to where we meant to store application temporary data. based on the environment and OS you could replace the default value for exp. to /tmp on linux systems. Default Value: PT_DIR_DATA/tmp/	Yes
PT_DIR_CORE	Path Address to Core modules, basically it's a directory where we put core modules of skeleton application. Default Value: PT_DIR_SKELETON/src/core	Yes
PT_DIR_VENDOR	Directory path to vendors Default Value: PT_DIR_ROOT/vendors/	Yes

You could also read about Directory Structure and use cases that why it's needed on this page.

Directory structure

Continue reading to next section