|Version 9 (modified by 9 years ago) ( diff ),|
Templates allow selecting alternate configuration sets.
This allows a separation between Core Code & Settings/Custom Code.
This helps prevent merge conflicts between different deployment branches & hence reduces the risk of forking.
Configuration is done using these files:
During the 1st run,
000_config.py is copied to
- machine-specific configuration (Debug, Database, SMTP, API Keys, etc)
- a setting to define which template folder to run
- importing of settings from
- optional local overrides to the template's settings
An empty database isn't terribly useful - e.g. maps won't display at all.
Options for how to Prepopulate the database are defined in the template's
config.py (but can be overridden in the running
settings.base.prepopulate = ["default"]
If you need to tweak your menus of build completely new ones:
It is possible to develop a custom theme for the look & feel of your system:
If you wish to add a new custom page without creating a new module: