Difference between revisions of "Design Specs: Application Configuration"
From WormBaseWiki
Jump to navigationJump to search (→To Do:) |
|||
| Line 11: | Line 11: | ||
* Develop a system for [[Design Specs: Application Configuration: Maintaining Links to External Resources|Maintaining Links to External Resources]] | * Develop a system for [[Design Specs: Application Configuration: Maintaining Links to External Resources|Maintaining Links to External Resources]] | ||
| + | |||
| + | |||
| + | * separate configuration from data initialization | ||
| + | ** current wormbase.conf (Config::General) file contains model info which can get complex and may be difficult to put in .ini format. | ||
| + | ** separate the config data (mostly db connections) into an .ini file. | ||
== Resources == | == Resources == | ||
Revision as of 14:17, 24 February 2010
Objectives
Maintain and document configuration of the next generation WormBase website.
- clean
- easy to maintain
- load different variables between dev and live (environment differences in configuration)
To Do:
- Document Configuration of the Web Application
- Develop a system for Maintaining Links to External Resources
- separate configuration from data initialization
- current wormbase.conf (Config::General) file contains model info which can get complex and may be difficult to put in .ini format.
- separate the config data (mostly db connections) into an .ini file.
Resources
Part 2: On Configuration (key,pdf) -- Configuration basics (and freebies)
The configuration file for the application can be found in the mercurial repository "wormbase" at the root level. It is called "wormbase.conf".
- pages are added here (as actions)
The templating system Template Toolkit also contains separate configuration related specifically to data presentation.
