Difference between revisions of "Design Specs: Application Configuration"

From WormBaseWiki
Jump to navigationJump to search
(New page: == Objectives == Develop a system for maintaining links to external resources and other configuration data for the web application.)
 
 
(11 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
== Objectives ==
 
== Objectives ==
  
Develop a system for maintaining links to external resources and other configuration data for the web application.
+
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 [[Design Specs: Application Configuration: Configuration of the Web Application|Configuration of the Web Application]]
 +
* 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 ==
 +
 
 +
Part 2: On Configuration ([http://www.wormbase.org/wiki/images/2008.02.13-on_configuration.key.tgz key],[http://www.wormbase.org/wiki/images/2008.02.13-on_configuration.pdf 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.
 +
 
 +
 
 +
[[Category:Developer documentation]]

Latest revision as of 18:47, 11 August 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:


  • 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.