Skip to content

Latest commit

 

History

History
41 lines (31 loc) · 1.57 KB

GDO7_CONFIG.md

File metadata and controls

41 lines (31 loc) · 1.57 KB

GDOv7: Kernel Configuration

Kernel Configuration is done by including a protected/config.php, before it bootstraps by including GDO7.php.

A config.php is re-written, validated and upgraded by the following actions.

  • gdo_adm.sh configure (when using the --force or no protected/config.php exists)
  • gdo_adm.sh confgrade (always)
  • gdo_fix.sh (always)
  • gdo_update.sh (when Module_Core::GDO_REVISION changes)

The known configuration variables are documented in Module_Install: \GDO\Install\Config.php, which is used by the install/wizard.php gdo application.

The install/wizard.php is a website, using phpgdo to manage the protected/config.php. When a database connection is possible, GDO_Modules can be installed. A GDO_Module will install any GDO returned in getClasses(). @TODO Rename to maybe gdoTableNames(). A GDO is just a containered special GDT. GDT means gizmore data type, the types of which everything is plugged together. GDTs know how to behave in several situtations.

Validation - Rendering - Configuration - Testing

GDOv7: Module Configuration

Modules can define their configration variables by overriding getConfig(), returning an array of GDT.

Changes to these GDT are made by either Module_Admin, ./gdo_adm.sh config <module> <name> <var>